Slash Command Setup

Enable slash commands for your existing dedicated Nexus instance.

Already using prefix commands such as !help? You can use slash commands alongside them once your instance is updated and Discord permissions are correct. You do not need to create a new bot or reset its token.

1. Check your instance is updated

Your bot must be running a Nexus version that includes slash commands and has registered them with Discord. If you are unsure, open a Nexus support ticket and ask us to check your dedicated instance. Include your server ID and bot name; do not post your bot token.

Changing an invite link alone does not add slash commands to older bot code. Nexus handles the update and any required restart for hosted instances.

2. Authorise your existing bot

1. Open the Discord Developer Portal and select the application for your existing Nexus bot.

2. Open OAuth2 → URL Generator.

3. Under Scopes, select bot and applications.commands. If an installation type is shown, choose Guild Install.

4. Keep the bot permissions required by your Nexus modules. Slash commands alone do not require Administrator permission.

5. Copy the generated URL, open it in your browser, select your existing server and complete authorisation. You must own the server or have Manage Server permission.

Do not kick the bot first. Use the same application and server. Discord currently includes applications.commands with the bot scope, so an existing installation may already be authorised.

3. Check member access

• In Discord, check that the relevant member roles have Use Application Commands permission. Check channel overrides too.

• Go to Server Settings → Integrations, select your bot and check any command restrictions for roles, members and channels.

• Nexus module settings and staff/member access rules still apply. Seeing a command does not override those settings.

4. Test it

In a server channel, type / and select your Nexus bot in the command picker. Choose one of its available commands and submit it. Test using a normal member account as well as an administrator account to confirm the intended access.

Prefix commands remain available where supported; you do not have to stop using them.

If commands are missing

• Missing for everyone: check the correct bot was authorised, then ask Nexus support to check that its slash commands loaded and registered successfully for your server.

• Visible to admins only: review role permissions, channel overrides and the bot’s command restrictions under Integrations.

• Visible but failing: confirm the bot is online and the relevant Nexus module and access settings allow the command. Send support the command name and error message.

• Recently updated: reload Discord and check again. Repeatedly inviting the bot or resetting its token will not fix a code or registration error.

Need help? Open a ticket in the Nexus support server with your server ID, bot name and a screenshot of the issue.

Discord references: OAuth2 scopes · Command permissions.