Skip to content

Conversation

@Kevinking500
Copy link

This is a small update to the current Ping Protection module.
This update includes the following changes:

  • [QOL] Updated some locales and improved some of their names
  • [Bug] Fixed the automod default block message from being over the 150 characters limit
  • [Bug] Fixed that the whitelisted users didn't show

I apologize for not catching these bugs in the initial release
No AI has been used this time.

Kevinking500 and others added 30 commits December 11, 2025 19:46
… advanced configuration in moderation.json and made the choices inside depend on it because I forgot to :/ Added the options to enable/disable pings/modlogs/logs kept after leave and made the choices depend on it + made those choices with numbers select instead of integers for almost 0 user-error issues.
…ded into the message editor for the warning message
…o debug code, has been tested and is currently ongoing extensive testing to ensure absolutely everythig works as supposed to
…lish while remaining the same functions. Removed a few locales that are unused and updated some locales for better understanding. Fully tested extensively. Not verified by GitHub because I code in VSCode.
Listed the warnings for all commands except the panel command as the bot already checks for administrator perms.
…efault with the message content and allows to configure both options
…ge to the automod message block. Also the bot now deletes the rule it created if automod enabled = false
…imit reached with reply pings even when it's allowed in config
Added from my ping protection branch
…for days instead of weeks in the now renamed "useCustomTimeframe" instead of "advancedConfiguration"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant