The console is locked or commands are missing
Why the admin console is locked or your server is missing (admins), and why commands do not show (everyone), with fixes.
このページの目次
- When the console will not open or commands are missing
- Console menus show a lock
- 1. Set one trigger
- You do not have Manage Server
- 2. Check your permission
- 3. If you just got it, log in again
- Wrong account, or your login ended
- The bot is not in that server
- 4. Press the Not installed card to invite the bot
- A matchmaker sees no console button
- Saving asks you to try again
- 5. Save again in a moment
- Admin commands are missing
- Commands only work in a server, and some only in your room
- The command name looks different
- The bot is missing, or was added without command access
- 6. Approve again through the invite link
- A new or changed command does not show up
- 7. Wait, then type the command again
- If it still does not work
- Where to go next
- Check it worked
When the console will not open or commands are missing
Start here if the web admin console is locked or does not list your server, or if Kletoi's commands do not show up in Discord. The first part (the web console) is for server admins, and the second part (Discord commands) is for everyone, members included. The causes come in the order they most often apply.
- Look for the Kletoi bot in your Discord server's member list. If it is not there, go to The bot is not in that server.
- On Home, check that the server's card has an Admin console button. If not, go to You do not have Manage Server.
- If the console opens but the sidebar menus show a lock, go to Console menus show a lock.
- Type the
/aboutcommand in Discord. If it does not show in the picker, read The bot is missing, or was added without command access first, and A new or changed command does not show up too if the bot was just updated. If it shows but only/admindoes not, go to Admin commands are missing.
Console menus show a lock
On a server with no trigger voice channel, an admin who opens the console lands on Guided setup first. Sidebar menus get a lock, and hovering a menu shows the hint “locked · opens once you set a trigger”. Pressing them brings you back to this screen. This is not a bug: it makes you set a trigger first. On a server where the bot lacks the permissions it needs, this lock does not apply. The details are in A tour of the web console and logging in.
Set one trigger
On the Guided setup screen that is already open, set a trigger channel: pick an existing one, create a new one, or use the recommended setup. The ways are in A server admin's first 5 minutes. One trigger opens the whole console, and you can skip the other steps. A server admin fixes this.
If creating a new channel is refused like this, your account also needs Discord's Manage Channels permission: “This needs Discord's Manage Channels permission. Manage Server alone can't create or rename channels.”
You are done when the locks on the sidebar menus are gone and the Settings menu opens.
You do not have Manage Server
The admin console opens only for accounts with Manage Server on that server. Without it, the Admin console button does not show. Opening the address directly gives “Access denied”. An empty My servers list with “No servers to manage” can have the same cause. If it opened yesterday but not today, the permission may have changed in between. The console trusts what the bot checks right now.
Check your permission
Ask the server owner or an admin who manages roles whether your account has Manage Server. Permissions are set in Discord, and Kletoi cannot change them. The owner or an admin fixes this.
If you just got it, log in again
The server cards on Home and the My servers list are drawn from the permissions Kletoi received when you logged in. After you get the permission, log out once and log in again: click your name at the top right and press Log out. Logging in is covered in A tour of the web console and logging in.
You are done when the server's card on Home shows the Admin console button.
Wrong account, or your login ended
If you have the permission but still get “Access denied”, you may be logged in with a different Discord account. Click your name at the top right and press Switch account. It clears the current login and opens Discord's approval screen again.
If you have not used Kletoi for a while, or used Log out other devices on another device, the login in this browser ends. Opening a page that needs login sends you to the Discord login, and after you log in you return to the page you wanted. While the bot cannot check your permission right away, an admin console page opened more than 12 hours after you logged in also sends you back to login. What Log out other devices does to a login is in Log out other devices.
If “We could not finish signing you in” appears while you log in, the login could not be finished after you came back from Discord. It shows when the sign-in link has expired or was already used, or when Discord is unstable. Press Log in again to start over. You fix this yourself.
If you reopened a login address with the back button or a refresh, you get a “Something went wrong” screen with code 400 instead of that one. Then press Back home to go to Home and start the login again from there.
The bot is not in that server
Home shows cards only for servers that have the bot. Press the Admin console card to list every server where you have Manage Server, each marked Bot installed or Not installed.
Press the Not installed card to invite the bot
The card opens the invite screen in a new tab with that server already picked. Approve it without removing any permission. What each one is for is in The server permissions Kletoi needs. An admin of that server fixes this.
If you try to save in the console after the bot left the server, you see “The bot isn’t in this server, so changes can’t be made”. Invite the bot again the same way and you can manage the server again. If you open an address directly and get “Page not found”, the address may be wrong or the bot may never have joined that server.
You are done when the Kletoi bot is in the server's member list and that server shows Bot installed in the My servers list.
A matchmaker sees no console button
This is not a bug. The Admin console button shows only to people with Manage Server. A member who was only appointed matchmaker does not see it. A matchmaker first opens the match screen with the ⚔️ button on a room panel (the room needs at least 2 people besides bots) or an address an admin sends them, and later also through the link in the bot's notification DMs, such as the stage nudge. Those DMs go out only while the server's Allow bot DM notifications switch is on. A new server starts with that switch off, so a first-time matchmaker has to get in through the ⚔️ button or an address an admin sends. How to turn the switch on is in I didn't get the invite DM. Admin screens such as settings and members open only for people with Manage Server. A server admin helps the matchmaker get in. The ways are in Appointing and revoking matchmakers.
Saving asks you to try again
If “Please try again in a moment” appears the moment you save a change, Kletoi could not confirm your admin permission with Discord at that moment. The bot may be reconnecting. Your change was not saved. Viewing a screen can still work while saving is held back.
Save again in a moment
Try again takes you back to the screen you were on. Wait a moment, check your change and save once more. Waiting is what fixes it, so nobody needs to step in. If it stays the same after a few minutes, read The bot is not in that server and If it still does not work.
Admin commands are missing
The /admin and /matchmaker commands are hidden by default from people without Manage Server. Without it they do not show in the picker at all. Check again with an account that has it. As in You do not have Manage Server, the server owner or an admin grants the permission. If you have it and still do not see them, the server may have set its own command access in Discord. That setting lives in Discord, and Kletoi cannot change it.
Who can use each command is listed in All commands.
Commands only work in a server, and some only in your room
The /admin, /matchmaker, /riot, /squad and /badge commands work only inside a server. They do not show in the picker in a DM with the bot.
Except /voice help, the /voice commands work only while you are inside a temporary voice channel in the server. Otherwise the answer is “You can only use this inside a temp voice channel.”. Apart from /voice info, they are owner-only, so someone who is not the owner gets “Only the channel owner can do this.”. That is not a bug. How to use them is in Manage your room — name, limit, lock, hide.
The command name looks different
The same command can show under a different name depending on your Discord app language. Apps in Korean, Japanese, Chinese, French or Spanish show that language's name; English and other languages show the English name. The command names in this guide follow the language you read it in, so they can differ from your Discord app language. Then pick the name the picker shows. Only the name differs, not the command. There is nothing to fix.
The bot is missing, or was added without command access
If the bot is not in the server's member list, there are no commands either. If the bot is there but none of Kletoi's commands show, the command access scope (applications.commands) may have been left out when it was added. Kletoi's invite link asks for that scope together with the rest. If the bot was added from some other address, it may be missing. If the bot is there and the scope is right but commands still do not show, the server may restrict in Discord who can use commands. That setting lives in Discord, and Kletoi cannot change it. A server admin fixes this.
Approve again through the invite link
Approve once more through the invite link with every permission left on. Your channels and settings stay as they are. What each permission is for is in The server permissions Kletoi needs.
You are done when the /about command shows in the picker. On an admin account, /admin shows too.
A new or changed command does not show up
Right after the bot is updated, a command that is new or changed takes a while to spread across Discord. This applies only then, so if commands are missing for some other reason, read the causes above first. We cannot promise how long it takes. Waiting is the default, and nobody needs to fix anything.
Wait, then type the command again
Wait a little and type the command again. If it still does not show, you can also restart the Discord app. That is not a sure fix.
You are done when the /about command shows in the picker.
If it still does not work
- Read the Frequently asked questions page first.
- The
/supportcommand in Discord shows how to reach us. - You can also send the bot a DM directly, and the message is passed to the operator.
- You can also write by email: admin@kletoi.com
- If a Discord support server link is set, it also shows at the bottom of the FAQ page and in the
/supportreply.
When you ask, include the server name, the screen you tried to open and the text you saw. If a “Something went wrong” screen shows a Request ID item, include that too.
Where to go next
Logging in and the screen layout are in A tour of the web console and logging in, and the first setup is in A server admin's first 5 minutes. If bot permissions confuse you, see The server permissions Kletoi needs. A matchmaker's ways in are in Appointing and revoking matchmakers, and ending logins on other devices is in Log out other devices. The whole settings page is mapped in Server settings at a glance. If an invite DM does not arrive, see I didn't get the invite DM; if records are missing from a profile, see My records are missing.
Check it worked
You are done when the Admin console button on the server's card on Home opens and the /about command shows in Discord's picker. As an admin, /admin shows too.