Removing example config, updating to .NET Core 2.0.0

This commit is contained in:
Noikoio 2017-09-05 11:26:57 -07:00
parent c344db0c92
commit a91b432557
3 changed files with 3 additions and 77 deletions

View file

@ -1,13 +1,13 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
This file is used by the publish/package process of your Web project. You can customize the behavior of this process
This file is used by the publish/package process of your project. You can customize the behavior of this process
by editing this MSBuild file. In order to learn more about this please visit https://go.microsoft.com/fwlink/?LinkID=208121.
-->
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<PublishProtocol>FileSystem</PublishProtocol>
<Configuration>Release</Configuration>
<TargetFramework>netcoreapp1.1</TargetFramework>
<TargetFramework>netcoreapp2.0</TargetFramework>
<PublishDir>bin\Release\PublishOutput</PublishDir>
</PropertyGroup>
</Project>

View file

@ -2,7 +2,7 @@
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>netcoreapp1.1</TargetFramework>
<TargetFramework>netcoreapp2.0</TargetFramework>
<RootNamespace>Noikoio.RegexBot</RootNamespace>
<AssemblyVersion>1.1.3.0</AssemblyVersion>
<Description>Highly configurable Discord moderation bot</Description>
@ -20,10 +20,4 @@
<PackageReference Include="System.ValueTuple" Version="4.4.0" />
</ItemGroup>
<ItemGroup>
<None Update="settings.example.json">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</None>
</ItemGroup>
</Project>

View file

@ -1,68 +0,0 @@
// (this is now really outdated. I'll update it eventually)
{
"bot-token": "your bot token goes here", // this value is required
"playing": "add some extra flair here", // optional
// Server values are defined in the "servers" array. Multiple servers are supported.
// Unless stated otherwise, all given values are not case sensitive.
"servers": [
{
"name": "RegexBot testing area", // Server name, as exists on Discord.
"ignore": {
// Server-wide ignore list. This entire section and its subsections are optional.
// For the moment, only names are checked and it is assumed they will never change.
// The user ignore list in particular should be considered highly unreliable. This will be fixed later.
"users": [],
"roles": [ "Bots" ],
"channels": []
},
"rules": [
// Response rules are defined within this array. See the examples below.
{
"name": "Greeter", // Name of the rule, for logging purposes. Required.
"regex": "^hello", // Regex string that will trigger this rule's response. Required.
"response": [ // Array of responses. Required.
"say #_ Hi @_."
// "say" sends a message to a channel.
// The first parameter (#_) is a reference to the channel where the response
// is being triggered. The rest of the parameters are the text to use. The text
// "@_" is replaced by the name of the user that triggered the response.
]
},
{
"name": "fishfish spam remover",
"regex": "(fish)+",
// Regex rules are not case sensitive by default, but can be overridden with this setting.
"ignorecase": "false",
// The next two statements ensure that the rule won't be enforced unless the message
// is between 10 and 20 characters (inclusive) in length.
"min": 10,
"max": 20,
"response": [
"delete", // Deletes the message that triggered the response.
"report #modlog" // Quotes the message to the given channel.
]
},
{
"name": "Fun script thing",
"regex": "^!fun",
"ignore": {
// Individual rules may define their own ignore lists.
// It works in exactly the same way as the server-wide ignore list.
"roles": [ "Anti-Fun Brigade" ]
},
"response": [
// Executes an external script and sends output to the source channel.
"exec #_ python ../fun.py"
]
}
]
}
//, {
// Another server may be defined here with its own set of rules.
//}
]
}