sahneedev / sahnee-bot Goto Github PK

As specified by @JakobHeubl :

• Kick and Ban actions at given amounts of warnings
• make this feature optionally
• what to do after a user reached the given amount of warnings and got punished (reset warnings?, higher tiers? @JakobHeubl )
• only admins and serveradmins can configure the behaviour

If a warned user leaves the Discord server they cannot be unwarned or otherwise removed from the DB.

needs further investigation

a command /randomhistory <optional: amount, default = 1> <optinal: username> that returns a random warning/unwarn from a user. if no user is given, it will return a random warn/unwarn from anyone on the guild.

NOOO I NEED JS

The warnleaderboard should optionally exclude users with 0 warns.

if a user does not enable all permissions for the bot on the guild, send him a message and tell what's the problem

As of right now it only shows who warned/unwarned whom and with which reason. I'd also like to be able to see the date of the warning and the warning number.

do not send a broadcast message with the latest changes if there is no file available.
currently an empty embed will be generated and sent to every guild, the bot is in.

currently the text gets written down without looking if there is a new version.
maybe just use a new embed if there is a new version.

/unwarn @ROLE <optional: reason>

same as /warn @ROLE

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dotnet monorepo to v7 (major) (Microsoft.EntityFrameworkCore, Microsoft.EntityFrameworkCore.Design, Microsoft.Extensions.Configuration.UserSecrets, Microsoft.Extensions.Hosting, Microsoft.Extensions.Logging.Console)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update actions/download-artifact action to v3.0.2
• Update dependency Npgsql.EntityFrameworkCore.PostgreSQL to v6.0.8
• Update dotnet monorepo to v6.0.16 (Microsoft.EntityFrameworkCore, Microsoft.EntityFrameworkCore.Design)
• Update actions/upload-artifact action to v3.1.2
• Update dependency ColorHelper to v1.8.1
• Update dependency Discord.Net to v3.10.0
• Update haythem/public-ip action to v1.3
• Update actions/checkout action to v3
• Update actions/setup-dotnet action to v3
• Update dependency Npgsql.EntityFrameworkCore.PostgreSQL to v7
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

startup tutorial will not be displayed if the bot joins a guild that does not have a channel bot-commands.
If the channel then gets created via CreateBotCommandsChannelAsync(IGuild) the startup tutorial cannot fetch a channel with this name via query.

-> Resulting in the startup tutorial not getting displayed

make the channel the bot listens to configurable per guild.
and listen to every channel by default

Does this bot run fine on multiple servers

/wlb = warnleaderboard
etc...

if a users gets warned for the first time, the bot will introduce himself.

A user can then opt-out for any message that the bot would send him
(Make the user clear, that he can still be warned, but won't get notified if they are about to get kicked or banned)

/warn @ROLE

Should warn all users in a specific role.

After a new release too many timeouts are sent out at once. This triggers the discord rate limit.

Therefore changelogs should be sent out slower (e.g. only 5 per minute)

currently some wip things are not documented. This needs to improve

command /warnerhistory @UserName <optional: amount> or something like that.
Will show the specified amount of warnings/unwarns the user issued. Sorted by the latest to the oldest.

something like /vote or /botlists to show where you are able to vote for the bot

Hey. I actually found some time to test the bot today and even with the newest version of the bot I encountered the same error with a custom prefix as last time:

Newtonsoft.Json.JsonSerializationException: Error converting value "c!" to type 'System.Char'. Path 'General.CommandPrefix', line 6, position 33.
---> System.FormatException: String must be exactly one character long.

This was tested on windows. I didnt have the time to check if it might just be a windows-only error as you stated before that longer prefixes would now work. Might have some time to try it on my raspberry tomorrow, cant promise anything tho.

Currently we rely on a config.json file and some settings in the database.
This mix ain't goot.

Either config file only or database only.
Default config needs to be available if database only.

Maybe something like /config <something> <something>

reverse the order of shown entries