Questions people actually ask

Click Add to Discord in the nav or on the homepage, pick your server, and approve the requested permissions. Then run the ,setup command (see the prefix question for which prefix your server uses) or /setup, to walk through first-run provisioning.

It depends on which features you use: moderation commands need the matching Discord permission (Ban Members, Kick Members, etc.), and Anti-Nuke specifically needs View Audit Log to detect anything at all (see the Anti-Nuke question). The bot requests a broad set on invite so most features work immediately, but you can trim per-channel overwrites afterward; a command will tell you what it’s missing if it can’t act.

The most common cause is that your server isn’t currently whitelisted/entitled: Righteous gates guild access behind an entitlement system, and an un-entitled guild goes quiet rather than posting an error to every channel. Ask an admin, or ask in the support server (opens in a new tab), to check your server’s status. The second most common cause is a missing bot permission in the channel you’re testing in: check that Righteous can view and send messages there.

Global slash-command deploys take about an hour to propagate to every server after they’re pushed. If a command was added or changed recently, wait before assuming something’s broken. If it’s been longer than an hour, try restarting Discord; the client caches command lists.

No. A guild-scoped deploy instantly registers commands to your one server for testing, on top of whatever the last global deploy already registered there, so while both exist, every command appears twice in that guild. This is inherent to how instant guild-scoped testing works, not a bug, and it clears itself automatically the next time a global deploy runs.

The default is ,, as in ,help. The bot also answers to the word prefixes jason and righteous (jasonhelp works too). The prefix is per-server and changeable: run ,prefix to set your own, which means a prefix printed anywhere on this site is a default rather than a fact about your server. Every slash command works regardless of prefix, so /help is always available if you’re unsure what yours is set to.

Check two things: the bot’s role must sit above the roles it’s trying to act on in your role hierarchy, and the bot needs the matching permission (Manage Messages, Ban Members, Moderate Members) either globally or in that specific channel. Righteous checks hierarchy before acting, so it will refuse rather than fail unpredictably.

Anti-Nuke detects through Discord’s audit log, which means the bot needs the View Audit Log permission. Without it, detection silently never fires. There’s no error message for this, because Discord doesn’t tell a bot it lacks a permission it never tried to use; check your permission overwrites and re-invite with the requested scope if it was trimmed.

Yes. Righteous has a fakepermission system for exactly this, configured per-server. A role granted a permission as a fake permission clears Righteous’s own checks for the matching command without holding anything in Discord, so a moderator can run ,ban while Discord’s own ban button stays greyed out for them. The full mechanic (what one grant does and doesn’t cover, and how to set one up) is the Fake permissions guide under Docs.

Some Last.fm and Spotify commands are user-installable and work outside a server; most moderation, logging and protection features are guild-only by nature, since there’s no server to protect in a DM. Check the individual command’s page on /commands for its availability.

Channel-level permission overwrites can still block a bot even with a server-wide Administrator role, if that channel explicitly denies the bot a permission. Check the channel’s permission overwrites, not just the server-wide role.

There are three separate tiers: Boosting Premium (free, just boost the server), Self Premium ($2.99/mo or $29.99/yr), and Server Premium ($7.99/mo or $79.99/yr, covering the whole server rather than per-member). The full side-by-side perk breakdown lives on /premium: Discord’s own message size limit means ,donate can’t reliably show every perk in one card, which is the whole reason that page exists.

You subscribe with ,donate in the support server, which opens a Stripe checkout; Manage subscription on the same card opens Stripe’s Billing Portal to update your card, see invoices or cancel (plan switching is not offered: cancel and resubscribe to change plan). A subscription renews automatically until you cancel, and cancelling leaves your access running to the end of the period you have already paid for — /refund-policy covers that in full. Buying is Discord-side only, because the checkout is bound to your Discord account. /premium documents what each tier includes; it doesn’t sell it directly.

Check which tier a perk is actually under on /premium: Boosting Premium, Self Premium and Server Premium are three different, non-overlapping products, not tiers of the same ladder, so boosting doesn’t grant Self-Premium-only perks and vice versa. If it turns out you bought the wrong one: purchases are non-refundable except where the law where you live requires otherwise, and you can cancel at any time and keep access for the rest of the period you’ve already paid for. You’re never cut off mid-period for cancelling. A refund or a dispute decided in your favor doesn’t automatically strip what the payment unlocked either; those are handled by hand, one case at a time, because a disputed charge is often a stolen card used against someone who did nothing wrong. /refund-policy is the full version, and a billing problem you can’t solve from there goes to the support server (opens in a new tab).

Server Premium is tied to the guild, not any one member, so it stays with the server regardless of membership changes. Self Premium is tied to the purchasing member’s account, so it follows them, not the server. That covers a handover as well: a server changing owner keeps its Server Premium, with nothing for either party to do and nothing to re-buy, and Self Premium doesn’t transfer to a server or to anyone else. Both rules are stated on /terms.

Server configuration (settings, logging preferences, whitelist status), moderation history, and, if you link an account, your Last.fm username and cached listening data. A few things clear themselves on a fixed schedule: a deleted or edited message’s snapshot after 24 hours, the rejoin role-restore cache after its configured window (12 hours by default, configurable free on every tier, up to 48 hours on Server Premium), internal Stripe webhook receipts after 30 days, and a finished giveaway’s entrant list after 14 days with the giveaway’s own record at 90. Everything else is kept until it’s deleted. You can delete the Last.fm side yourself with ,lf reset confirm: it’s free for everyone, unlinks the account and removes the cached albums, tracks and artists along with your full synced scrobble history, and it answers to delete, remove and forgetme as well. /privacy has the whole list, including the categories with no self-serve deletion command yet, which we remove by hand if you ask in the support server (opens in a new tab). That is the bot; for what this website itself does — which is close to nothing, and sets no cookies — see /cookies.

You can unlink with the account-management command in the Last.fm category. Righteous only reads your Last.fm scrobble data; it never posts, scrobbles or writes back to your Last.fm account.

Join the support server (opens in a new tab) and ask. That’s the fastest path to an actual person, and it doubles as proof the bot and its team are active.

No. The bot’s source is closed, and so is this website’s own code. What is public is the documentation: the guides under /docs live in a public repo (opens in a new tab) that takes community pull requests, so a typo, a clearer explanation or a missing example is a normal PR. This FAQ and the rest of the marketing pages aren’t in that repo: they ship with the private site code, so the way to change one of them is to ask in the support server (opens in a new tab).

Check /blog’s changelog stream: every merge to the bot’s main branch auto-deploys within about two minutes, and the changelog is the dated record of what shipped, rather than a claim made once on this page and never revisited. /status answers the live half of the same question, and renders “unknown” the moment its data goes stale rather than a green tick it can’t justify.