Getting Started
Setup
Commands
Recommendations & Help
GamerSafer
Setup - Anti-Nuke
Easily configure Anti-Nuke settings through our dashboard to protect your server from attacks and ensure its integrity. Use our documentation to understand every feature and set it up properly.
IMPORTANT: Ensure that the bot's role is positioned above all roles it can manage and above any member's role in the server hierarchy to avoid issues with assigning and removing roles.
1. Quarantine
Use the Quarantine feature to isolate users who perform suspicious activities and prevent them from causing further damage.
Regularly review and update your allow-list and quarantine settings to ensure optimal protection for your server.
1.1. Quarantine Role
- Select the role that will be assigned to quarantined users. This role should have restricted permissions to limit the actions of quarantined users.
- Users will lose all their previous roles and be assigned this selected quarantine role.
1.2 Punish Admins
- Enable options to punish administrators who try to perform harmful actions.
- Changing the server link. (Owner itās notified)
- Granting dangerous permissions in commonly used roles (Administrator, Manage Server, Manage Channels, Manage Messages, Manage Roles, Manage Webhooks)
- Giving dangerous permissions to channels or members (Manage Channel, Manage Permissions, Manage Webhooks)
- Attempting to give dangerous and staff roles to unverified or non-staff members.
1.3 Punish Bots/Apps
- Enable punishment for bots that are not on the allow-list and attempt to perform dangerous actions.
- Optionally, you can exempt Discord-verified bots from punishment.
- ATTENTION: The app/bot verification process on Discord has changed. A verified application is not necessarily safe. Be careful when turning on this option.
- Add bots to the immune list if they are trusted and should not be punished.
1.4. Advanced Settings
- Advanced Settings allow you to customize editing permissions for various server components such as channels, roles, emojis, stickers, sounds, webhooks, and bots/apps. You can enable or disable editing permissions for these components based on your server's security needs.
- It's important to note that the bot does not grant permissions to roles; you must apply the permissions to the roles yourself. The bot only monitors the actions taken. For example, if you allow members with the "Manage Channels" permission to edit/add/remove channels, the GS Defender bot will not prevent the action but will react if an unauthorized action is taken based on your settings.
- Example: If a member has the "Manage Channels" or āAdministratorā permission and you don't allow removing channels, and they remove a channel, they will be placed in quarantine. This is due to the limitations of Discord; the bot can only react to actions, not prevent them.
1.4.1. Permissions
- Channels: Customize the editing permissions for the server's channels. If a member attempts to perform an action (such as removing a channel) and the permission is not allowed in this section, they will be placed in quarantine, even if they have high-level permissions like "Administrator" or "Manage Channels."
- Roles: Control the editing permissions for server roles. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- Emojis and Stickers: Manage permissions for editing emojis and stickers. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- Sounds: Customize the permissions for editing sound settings. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- Webhooks: Specify permissions for managing webhooks. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- Bots/Apps: Control the permissions for managing bots and apps. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- General Permissions (Beta): Customize general settings editing permissions for the server. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
Remember: The bot does not grant permissions to roles; you must apply the permissions yourself. The bot only monitors actions and reacts to unauthorized changes based on your settings.
1.4.2. Applying and Monitoring Permissions
- It's essential to correctly apply permissions to roles within Discord settings to ensure the bot can effectively monitor and react to unauthorized actions.
a. Apply Permissions:
- Go to your Discord server settings and navigate to the roles section.
- Assign the necessary permissions to each role according to your server's requirements.
b. Monitoring Actions:
- The GS Defender bot will monitor actions taken by any members with the specified permissions.
- If an unauthorized action is detected, the bot will react according to your settings (Example: If a member has the "Manage Channels" or āAdministratorā permission and removes a channel without authorization, they will be placed in quarantine. The bot cannot prevent the action but will react to it.).
2. Exceptions to Anti-Nuke and Quarantine
Configure exceptions for trusted roles and users who can bypass certain Anti-Nuke restrictions.
2.1. Editor Mode
- Enable Editor Mode to grant special permissions to trusted users.
- Select the role for Editor Mode and set an expiration time for these permissions.
- Editors can remove users from quarantine and manage certain settings without triggering Anti-Nuke actions.
2.2. Editors and Quarantine
- Editors can remove people from Quarantine: Other editors can remove members from quarantine and restore all their previous roles. If the quarantined member performed an unauthorized action in editor mode, only the server owner can restore their role.
- Editors without the Editor Mode role can remove themselves from quarantine if they verify themselves: If the quarantined member performed an unauthorized action in editor mode, only the server owner can restore their role. Therefore, they can only exit quarantine using the
/editor
command if the unauthorized action was due to forgetting to activate "Editor Mode." After verifying their identity with facial biometrics, they can proceed with their actions.
2.3. Advanced Settings
- The difference between Advanced Settings in Editor Mode and Quarantine is that Editor Mode acts as an exception. It is an excellent configuration for allowing certain temporarily verified roles to perform actions that regular members cannot. Therefore, be very careful when selecting users permitted to access Editor Mode.
- Advanced Settings allow you to customize editing permissions for various server components such as channels, roles, emojis, stickers, sounds, webhooks, and bots/apps. You can enable or disable editing permissions for these components based on your server's security needs.
- It's important to note that the bot does not grant permissions to roles; you must apply the permissions to the roles yourself. The bot only monitors the actions taken. For example, if you allow members with the "Manage Channels" permission to edit/add/remove channels, the GS Defender bot will not prevent the action but will react if an unauthorized action is taken based on your settings.
- Example: If a member has the "Manage Channels" or āAdministratorā permission and you don't allow removing channels, and they remove a channel, they will be placed in quarantine. This is due to the limitations of Discord; the bot can only react to actions, not prevent them.
2.3.1. Permissions
- Channels: Customize the editing permissions for the server's channels. If a member attempts to perform an action (such as removing a channel) and the permission is not allowed in this section, they will be placed in quarantine, even if they have high-level permissions like "Administrator" or "Manage Channels."
- Roles: Control the editing permissions for server roles. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- Emojis and Stickers: Manage permissions for editing emojis and stickers. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- Sounds: Customize the permissions for editing sound settings. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- Webhooks: Specify permissions for managing webhooks. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- Bots/Apps: Control the permissions for managing bots and apps. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
- General Permissions (Beta): Customize general settings editing permissions for the server. Unauthorized changes, even by members with high-level permissions, will result in quarantine.
Remember: The bot does not grant permissions to roles; you must apply the permissions yourself. The bot only monitors actions and reacts to unauthorized changes based on your settings.
2.3.2. Applying and Monitoring Permissions
- It's essential to correctly apply permissions to roles within Discord settings to ensure the bot can effectively monitor and react to unauthorized actions.
a. Apply Permissions:
- Go to your Discord server settings and navigate to the roles section.
- Assign the necessary permissions to each role according to your server's requirements.
b. Monitoring Actions:
- The GS Defender bot will monitor actions taken by any members with the specified permissions.
- If an unauthorized action is detected, the bot will react according to your settings (Example: If a member has the "Manage Channels" or āAdministratorā permission and removes a channel without authorization, they will be placed in quarantine. The bot cannot prevent the action but will react to it.).
ā Previous
Next ā
On this page
- Setup - Anti-Nuke
- 1. Quarantine
- 1.1. Quarantine Role
- 1.2 Punish Admins
- 1.3 Punish Bots/Apps
- 1.4. Advanced Settings
- 1.4.1. Permissions
- 1.4.2. Applying and Monitoring Permissions
- 2. Exceptions to Anti-Nuke and Quarantine
- 2.1. Editor Mode
- 2.2. Editors and Quarantine
- 2.3. Advanced Settings
- 2.3.1. Permissions
- 2.3.2. Applying and Monitoring Permissions