Get started
Getting started
To set up Rage, add it to your server, move its role to the top of the role list, then turn on antinuke and logging - every other module is set up the same way, with one command and a menu.
Steps
- Add Rage to Discord and pick your server. Keep the Administrator permission ticked - antinuke and recovery need it.
- Server Settings > Roles: drag the **Rage** role above every role it should manage. A bot can only act on members below its own role.
?antinuke config
Turn on server protection first.?log setup
Pick which events are logged and where.?help
Browse every module from Discord. Each command shows its arguments, permissions and an example.
The prefix
The default prefix is ? - ?help, ?ban, ?tickets panels. Change it per server with ?prefix.
Reading command syntax
Every command on these pages is written the same way:
(argument)- required.[argument]- optional.a or b- pick one.- Commands with spaces (
tickets panels,levels add) are subcommands of a group - run the group alone to see them all.
Who can use what
Each command lists the permissions it needs. Staff without Administrator can still be given single commands through Fake Permissions, and commands or modules can be turned off per channel with ?disablecommand.
Next steps
Most servers set up these next:
- Antinuke and Antiraid - security.
- Automod and Moderation.
- Tickets, Levels and Welcome messages.
- Embed code and Variables - for every custom message.
Questions
Why can't Rage ban or edit someone?
Their highest role is above Rage's role, they're the server owner, or the bot is missing that permission. Move the bot's role higher.
Does Rage use slash commands?
Some - most commands are prefix commands (?command), because Discord limits a bot to 100 slash commands.