• add a config value AllowBanAppeals with commands for setting this value
• add a DM-only command $appeal [serverid]
• add the following text to the ban DM: appealing this ban is possible by running $appeal [serverid]. when appealing is indeed possible
• always check whether member is actually banned when appealing

ModCore has a nice and useful setup wizard by @uwx, iirc this wan't done yet. Opening this issue to remind myself to finish it.

Idea: adding a delay so welcome messages get deleted after x minutes. Option to only do so if the member left within this time

Some events aren't properly handling null guild configs. This for example seems to happen in the Member Updated event and the User Updated event.

When this happens, the events simply throw and get ignored. For the end user this is no big issue, it won't be noticed. However, for the sake of clean code and a proper program this has to get fixed.

As of right now, purging a chat also gets rid of messages like polls etc. It would be better to just keep these messages, to prevent accidental deletion of polls.

The following methods will never be called without a cast:

https://github.com/NaamloosDT/ModCore/blob/8f47918d6273b2b9c4efa8dea360e2ba2a7369ed/ModCore/Logic/Extensions/Sanitization.cs#L29-L39

This is due to an intricacy in how overload resolution works in the C# compiler, it will always prefer the string overload over the FormattableString one.

The only fix is to rename these overloads and use them wherever appropriate. They should probably not be removed, as they enforce invariant culture and sanitization within interpolated string parameters, which is pretty important.

As all builds are done on my end by now and the bot is not intended to be a "pull and run your own instance delele" kinda bot I suppose removing anything auto-update and CI related is fine.

A way for ModCore users to directly contact the bot developers.

Might want to fix that

Have all commands with arguments have interactive counterparts that collect arguments with interactivity (and no arguments themselves)

example: screenshare command

The idea is to add a command that will scan through a server to find possible issues with ModCore's functionality, e.g. missing permissions, channels it can't access, etc etc

fun fun leaderboard

• poll support
• set up to give role on reaction
• set up to give role on join
• #113
• avatar change log (and possibly other types of changes)
• nickname change request system
• #114
• #115
• Slowmode
• #116
• Todo lists
• Additional strawpoll creator next to the reaction poll system
• #117
• Snipe command
• #118
• #119
• #120
• #121
• #122
• Mass mention filter (with exempt of course)
• #123
• Feedback system (DM Naamloos(?))
• Temporary channel locks
• Starboard leaderboards
• #124
• #125
• #127
• #126

(UPDATED OP)
Instead of a rewrite, ModCore is getting a refactor. Here a list of new stuff I still want to add:

Mega mega todo

• Use buttons instead of reactions for polls
• Image based welcomer
• Updated link filters and invite filters
• Improve Giveaway feature
• Verification system (give role on special phrase?)
• Mass mention filter (with exempt of course)
• Ticket system
• Feedback system (DM Naamloos(?))
• Temporary channel locks
• Starboard leaderboards
• Ban appeals
• Delete welcome messages if a member leaves within specified time
• Prevent purging polls etc
• Highlighter (DM on phrase highlight)

Title says all.

Discord does not support slowmode for specific users

Idea: use the mute role

user sends message -> gets mute role for x minutes -> timespan ends -> remove mute role -> repeat

I am not 100% sure whether I want to use GPLv3, and considering I am rewriting I'd fine with picking a different license..

Might be nice for server owners that want to reserve commands like $snipe/$snipeedit for moderators. Might just add an exempt thingy for the commanddisable though.

Not shitty human beings exploiting the bot to mention here and everyone. Needs fixes.

Known occurences:

• tag names

This would allow for implementing command-specific fail cases, telling the user what went wrong and how they can fix it + expected behaviour.

example:

[Command("test")]
public async Task TestAsync(CommandContext ctx)
{
    // let's pretend this has code that might fail
}

[CommandFail("test")]
public async Task TestFailAsync(CommandContext ctx, CommandErrorEventArgs error)
{
    // handle command-specific errors here
}

Basically a command that says "I wanna get reminded about that too!" to copy someone elses reminder.

i like the attribute API more. i believe @Emzi0767 likes the fluent API more. i wanna wait for consensus before migrating anything.

Gotta add some more of dem action logging aight

some commands are missing them

Exception from console

I want to make mee6 completely obsolete on a server I'm in.

Starboard now only decreases and increases on a star. This should just recalculate the full count based on what reactions exist.

fix that, baka naam

Giveaway is not persistent across bot sessions.

it's here boys

might do it myself, if you're lucky you might be faster

ModCore has a lot of broken / incomplete commands/features. These need to either be fixed or removed. Next to that code has to be cleaned up a bit as well. Refactor might be nice.

More details coming soon, eg features that are broken / incomplete.

Might be nice to make it a separate command too

Title says all.

We need way more commands for moderation. Creating a single command is good enough for a PR to be accepted ;)

refactor it all!!!1

plez add appveyor hooks

eg.

await ctx.WithSettings(async cfg => {
    // do stuff with cfg
    cfg.Linkfilter.BlockBooters = true;
    cfg.Linkfilter.BlockInviteLinks = true;
    cfg.Linkfilter.BlockIpLoggers = true;
    cfg.Linkfilter.BlockShockSites = true;
    cfg.Linkfilter.BlockUrlShorteners = true;
    // implicit
    // await ctx.SetGuildSettingsAsync(cfg);
});

I've taken a look at some more popular moderation bots and hand picked a couple of functions that would be nice for modcore. (and thought up a couple)

• Temporary bans
• Global warnings (moderators from other guilds can see whether users have done more bad things)
• Temporary mutes (mutes are at the moment permanent untill you unmute)
• Leave server (for those who want to make the bot leave on its own)
• Temporary pins (unpin after specific date/time)
• Reminders (remind me to ban this guy after 2 hours :^) )
• Clean bot's own commands (basically a shortcut to purge, or perhaps with user commands included)
• Automated Kicks/Bans (after certain amount of warnings/strikes)
• Scheduled Pins
• Server warnings (these trigger the auto-kick/ban)
• Tag system
• Prune by regex

These are just proposals. Feel free to add anything c:

For example, give a member the "regulars" role after 1000 messages. Maybe even make it a message average or something? dunno.

Sometimes timers break, and keep resetting themselves. This is to be investigated ;^)

Cause:
unknown

What happens:
When setting a reminder, you won't get a confirmation message, yet the timer will be saved to the database. Once the timer is hit, it will just reset itself. This issue would just pop up randomly for (seemingly) no reason.

Currently it seems like a rebbot or cleaning the database table fixes it, yet we need a permanent full-on fix for this

I want to add something to allow users to build their own commands. When in beta I want to allow people to build their own JSON that gets validated and parsed to a command. Later on I want to build a graphical command builder which might be similar to scratch, I'm not sure yet.

Example ModCoreCommand format:

{
    "parameters":[
        {"name" : "user", "type" : "member"},
        {"name" : "nickname", "type" : "string"},
    ],
    "actions":[
        {"action" : "setnickname", "parameters" : [ "param:user", "param:nickname" ] }
    ]
}

I'll still have to think of notations for stuff like if-statements, but I think this might work out fine.

Commands will be:
$[command name] args for calling custom commands
$customcommands for listing custom commands

to not spam the board.

ask velvet about how silk did it