You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users could subscribe to OptiFine updates by being granted a new role (something called "Notifications" or "Updates"). This would work via an OptiBot command, such as !sub. Users may also unsubscribe at any time with the opposite command: !unsub
When a new update is posted, another command (could be !notify) may be used by mods/admins to ping everyone with that role. To prevent mass pings, this role CAN NOT be pinged by default. To make this work, the bot must have the "Manage Roles" permission. With this permission in place, the bot can now perform this set of actions:
modify the notification role to allow pings
ping the role with a message posted in the channel where the command is used.
modify the notification role once again to disallow pings
Given a stable connection to Discord's API, this would all occur within less than a second, making it effectively impossible to abuse the mass ping.
This is great and all, but why not just enable notifications for the #updates channel manually?
I've asked this same question when 5 people suggested it to me. They all gave me pretty much the same response: Discord's notifications don't work. With this system, it basically acts like an opt-in @everyone.
The text was updated successfully, but these errors were encountered:
Users could subscribe to OptiFine updates by being granted a new role (something called "Notifications" or "Updates"). This would work via an OptiBot command, such as
!sub
. Users may also unsubscribe at any time with the opposite command:!unsub
When a new update is posted, another command (could be
!notify
) may be used by mods/admins to ping everyone with that role. To prevent mass pings, this role CAN NOT be pinged by default. To make this work, the bot must have the "Manage Roles" permission. With this permission in place, the bot can now perform this set of actions:Given a stable connection to Discord's API, this would all occur within less than a second, making it effectively impossible to abuse the mass ping.
I've asked this same question when 5 people suggested it to me. They all gave me pretty much the same response: Discord's notifications don't work. With this system, it basically acts like an opt-in @everyone.
The text was updated successfully, but these errors were encountered: