Role Groups: The Answer to Mod @Pinging Permissions

Role Groups. You can have ~200 roles, currently. Of those, large servers have all roles @pingability turned OFF.

Why? Trolls, simply. They will come in and @ping all the groups with spam/junk and upset people (folks don't like being pinged without a solid reason).

What do mods do now? All pings for all groups are turned off. When you have news, you may need to ping multiple groups. So you need to turn on 3 groups to be pinged >> hope trolls don't notice >> @ping the 3 roles >> hope trolls aren't fast enough to @ping themselves >> find and turn off those 3, again. It's tedious.

What do BOTs do? It's even tedious for BOTs! You need to turn ON the role ping >> @ping >> turn OFF the role ping. If you run into a bug, it may crash with the role ping still turned on.

Solution! Role Groups -- They don't show, they don't do anything except help moderators and bots. You can stuff roles into a single, @pingable group, that only mods have permission to change and ping. Users CANNOT ping groups. Boom, bam -- solution to both multi-ping roles AND bot/mod @pings without users troll @pinging.

Afterthoughts. I run a verified game server with 14k users in it - it can get wild, even with high security settings. This would revolutionize our server.

Also, no one likes pings, so we modulate them -- @news, @community-news, @game-news,@dev-blog .... well, sometimes you get @pings that apply to MULTIPLE groups, where we'd then need to tweak the @ping settings on/off (super tedious) for all of these groups.

And hope you even remember to turn those groups @ping back off! You're usually bombarded with questions right after major announcements in large servers.

Stop the tediousness and please help mods mod!

Comments