Frequently Asked

GRAVE is an all-in-one Discord bot built to handle everything your server needs — moderation, economy, server setup, info commands, and fun. The idea is you shouldn't need five different bots cluttering your server when one does it all cleanly.

Yes, completely. Every feature listed on this site is available with no paywalls, no premium tiers, no subscription. Just add the bot and use it.

Over 200 commands across moderation, economy, setup, info, utility, and fun categories. You can browse the full list on the Commands page.

99.9%. GRAVE runs 24/7 and is monitored continuously. If something goes down you'll usually know about it in the support server before you even notice it yourself.

Hit the Add to Discord button, pick your server, and authorize. Takes about 10 seconds. No setup wizard, no configuration required to get started.

The invite link requests Administrator by default, which covers everything. If you prefer granular control, the minimum GRAVE needs to function properly is: Manage Roles, Kick Members, Ban Members, Manage Channels, Read Messages, Send Messages, Embed Links, and Manage Messages.

Run /welcome set in the channel you want messages sent to, then use /welcome message to customize the text. You can disable it anytime with /welcome disable. Same flow applies for leave messages using /leave.

Yes. Use /prefix set [prefix] to change it server-wide. Keep it short — single characters like !, ?, or . work best and avoid conflicts with other bots.

Run /autorole set @role. From then on every new member who joins gets that role automatically. Make sure GRAVE's role is higher than the target role in the role hierarchy or Discord will block the assignment.

Anti-Nuke monitors your server for destructive actions — mass channel deletes, mass bans, mass role deletions — and automatically punishes the responsible account. Enable it with /antinuke and configure thresholds with /antinuke config. You can whitelist trusted admins with /whitelist add so they don't trigger it.

Yes, warnings are stored and persist until manually cleared. Use /warnings @user to view their history and /clearwarn @user to wipe it. Only members with moderation permissions can issue or clear warnings.

/lockdown removes the Send Messages permission from @everyone across all channels instantly. Use it when things go sideways fast. /unlockdown restores everything back to how it was.

Yes. Use /modrole set @role and that role gains access to moderation commands without needing full administrator. Same goes for admins via /adminrole set @role.

Members earn currency through /daily, /work, and gambling commands. There's a wallet and a bank — your wallet can be robbed, your bank can't. Use /deposit and /withdraw to move money between them. Spend it in the shop or flex on the /leaderboard.

No. Each server has its own completely separate economy. Balances, leaderboards, and shops are all local to the server they were earned in.

Only from your wallet, and only if /rob succeeds — it's not guaranteed and comes with a failure penalty if they get caught. Anything stored in your bank with /deposit is untouchable.

Once every 24 hours. The cooldown resets from the time you last claimed, not at midnight. GRAVE will tell you exactly how long you have left if you try too early.

Check these in order: make sure GRAVE has permission to read and send messages in that channel; confirm you're using the right prefix (default is !); check the command isn't disabled with /commands; and verify GRAVE is actually online in the member list. If none of that works, hop in the support server.

Almost always a role hierarchy issue. GRAVE's role needs to be above the role of the member you're trying to moderate in Server Settings → Roles. Discord prevents any bot or user from actioning someone with an equal or higher role.

The command might have been disabled by a server admin. Check if it shows as inactive in /commands. If you have admin access, you can re-enable it. Otherwise contact your server admin.

Open an issue on the GitHub repo for bugs — include what command you ran, what you expected, and what actually happened. Feature requests go in the support server in the suggestions channel.

The support server is the fastest way to get a response. Drop your question in the help channel and someone will get back to you.