The config panel

Almost everything Righteous stores about your server lives behind one command. First five minutes uses the panel to switch a few features on; this page is the panel itself: how it is laid out, and what to do when it refuses you.

Opening it needs Administrator. That gate is checked again on every click, not just when the panel is drawn, so a panel left in a channel stops working for someone the moment they lose the permission.

Open the panel

,config opens page one, and so do the aliases ,settings, ,configuration and ,setting. On slash it is /config panel.

,config

Any ,config word the bot does not recognise opens the panel too. A half-remembered subcommand, or one that has since moved somewhere else, lands on page one rather than on an error. That is deliberate: muscle memory should cost you a click, not a search.

The panel is an ordinary message in the channel you ran it in. Anyone who can read that channel can read your current settings, so open it somewhere staff-only. It stores nothing in memory, so it keeps working after a restart.

Work out which controls you can actually use

Administrator gets you in. It does not get you everything, because each control carries the same gate as the command that owns it. Four kinds of gate sit on individual fields:

A real Administrator passes every permission gate automatically, so those only constrain someone holding a fake permission. Owner-only and premium gates constrain everyone. Refusals are private and name what was missing: You need the Manage Roles permission to change that, or a line pointing at Server Premium.

24/7 is the asymmetric one, and deliberately so: switching it on needs Server Premium, switching it off never does, so a server whose subscription lapsed with the bot parked in a voice channel can still release it.

The one rule the panel looks like it should inherit and does not is ,command disable. Every click runs the invoke checks first (bot blacklist, role restriction, channel disable), but the last two apply only to people without Administrator, and the check straight after them refuses everyone without Administrator anyway. Disabling config in a channel therefore changes nothing about the panel's buttons there: the only people it could stop cannot open the panel to begin with. A bot-wide blacklist is the one gate that reaches everybody, panel included.

A gate that only bites non-admins cannot bite a control only admins can reach.

Move between pages

The dropdown under the panel is the navigation. There is no back button and no page arrows, because a Discord action row holds at most five buttons and the panel has far more pages than that: a select is the only control that scales.

Pick a page and the same message repaints in place; reopening with ,config always rebuilds from page one. New pages are appended to the end of the list and never inserted, so the order reads oddly in places: VoiceMaster and VM Defaults sit far apart, and so do Antiraid and Antinuke. That is the price of never renumbering a panel somebody already has open in a channel.

Clear a field by deselecting it

Nearly every role and channel dropdown accepts an empty selection, and an empty selection is how you unset a value. Open the dropdown, click the currently selected entry to deselect it, and the field is cleared.

There is no "None" option in those menus and there cannot be one: Discord builds role and channel pickers itself, so the bot has nothing to add to the list. The pages carrying one say so under the heading:

Deselect a dropdown to clear it (set it back to none).

Two pickers are add-only and do not work that way. The Autorole page's role picker and the Last.fm page's Who Knows blacklist picker open empty every time: nothing is pre-selected, so there is nothing to deselect, and submitting an empty selection changes nothing at all. They only ever add what you pick, because Discord caps a picker at 25 entries: reading a submission as "this is the whole list now" would silently drop everything past the 25 it happened to show. Removal is a separate control, its own dropdown on the Autorole page, which lists what is stored rather than what Discord offers, and ,lf blacklist remove for the blacklist.

A field pointing at a role or channel you have since deleted is shown as Deleted and ignored with a prompt to pick a new one. That is the panel telling you to set it again, not an error.

Find the page you need

Tickets edits nothing: it points at ,ticket panel, where presets, categories, greeting, limit, transcript, buttons and blacklists are really configured. Trap does nothing until ,trap setup has run, because setup creates the trap channel as well as the settings. Flood protection left the Snipe page for the same reason and lives under ,antispam.

Two surfaces writing the same settings is how one of them goes stale, so a page that stops owning a feature points at the command that does.

Set one field without opening the panel

A handful of settings have their own subcommand, for people who would rather type than click. Each is ,config <field> <value>, and each has a slash form under /config.

,config logchannel <channel>

,config logchannel #mod-logs

The four toggles take no argument: each flips the button the Logging & Welcome page draws.

The prefix is the one Overview setting with a command of its own: ,prefix set <prefix>, which needs Manage Server. Other pages mirror their feature's own command: Antinuke, Antiraid, Autorole and Giveaways do.

Find the Last.fm settings that moved

The server-wide Last.fm settings (the default now-playing colour, the vote reactions, the server embed code, background auto-update, the crown minimum and the crown reset) used to be ,config subcommands. They are now actions under ,lf server: Last.fm features that were only discoverable by someone already inside the server-settings command.

,lf server <action> [value]

,lf server crownminplays 5

Their old ,config lastfm… spellings are gone, so an older tutorial naming one will simply open the panel. ,lf server still answers to the old words as action names, and the panel's Last.fm page still edits the same settings: only the command moved.

Common issues

You have Administrator and a control still refused you. Read the refusal. Owner-only fields (Anti-Join, the Protection Log and every Antinuke rule, each marked 👑 on its page) cannot be reached by any permission, and premium fields want the server's subscription rather than anything about you. How Righteous decides who may run what covers each gate in order.

The Premium page's controls are greyed out. The server does not hold Server Premium. That is a gate the panel can render honestly, because it is the same for everyone looking at the message: so is the 24/7 button, when 24/7 is already off. The autorole history window is never greyed out on either tier, since configuring it does not need Server Premium; only the ceiling it enforces is higher with it.

An old panel does not list a page you were told about. The navigation dropdown is built into the message when it is posted, so a panel that has sat in a channel for months offers the pages that existed that day. Pages are only ever appended and never renumbered, so its options still open exactly what they always did. It simply cannot show you the newer ones. Run ,config again for a panel with the current list.

A setting shows as deleted. The role or channel it pointed at no longer exists. Pick a new one from the same dropdown.

You cannot find a "None" option to clear a field. There isn't one. Deselect the current entry in the dropdown instead.

The Trap page says no trap is set up. Run ,trap setup first: it creates the channel as well as the configuration, and the panel deliberately will not create either.

Nothing on the panel saves and it says the server is not whitelisted. The server's access has lapsed. See Access and the whitelist.

Nothing here fixed it. The shared common issues page works the same ground from the symptom end.