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"
@Fridolin012
Copy link

I noticed a few things I’d like to share regarding the module:

  • Redundant Settings: In the "Moderation Actions" config, there’s a setting for "Pings to trigger moderation," but there’s also a custom function for it. It feels a bit messy to have both. I’d suggest just keeping the custom function ("custom timeframe") to make it cleaner.
  • Log Retention: Why is the mod-log capped at 12 months? The moderation module doesn't have this limit, and I’m wondering if this can be changed to stay consistent with the rest of the tools.

@Kevinking500
Copy link
Author

Hi Fridolin,
That is indeed a bit messy, I will change that.
For the log retention though, as this is a module for "only" pings and not otherwise a broad (multiple) rule breaking that can include a big variety of punishments like warnings, mutes, kicks, bans and things that it feels like having it more than 1 year for "only" pinging is a lot, but I can extend it if you feel like it would need to be more, or even do no limit.

@Fridolin012
Copy link

Hi,

thank you for your quick response. I think we should ask @SCDerox for the second question^^

@SCDerox
Copy link
Member

SCDerox commented Feb 1, 2026

Thanks for your valuable feedback, Fridolin. I, personally, have no issues with the limit. But based on your feedback, there's no technical reason that requires a limit. So making it adjustable and allowing users to disable it might be a compromise that both sides could agree on.

@Kevinking500
Copy link
Author

I think I might just increase the limit to 2 years (48 months) and if we get any feedback from users for it to be longer then ig I can make it unlimited. But I agree with both 😅

@Kevinking500
Copy link
Author

Alrighty, I have now set the pings history limit to 2 years (I actually relaized it was only 6 months max, that was indeed short). Additionally, I removed the pings count thing for the custom timeframe as that's basically useless, it now uses the standard one, which is now also renamed to pingsCount without the Basic.

@Kevinking500
Copy link
Author

Sorry, I forgot you were talking about moderation log

@Kevinking500
Copy link
Author

Hi, I quickly added the category feature in the configuration.json and storage.json config files to make it look more sleek ^^

@Kevinking500
Copy link
Author

Thanks to Simon who provided me the list of emoji's that actually work in the dashboard, I adjusted it to use supported ones ^^

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.

3 participants