Getting Started with Oxy Controller

This guide is for a server owner or administrator who has never used Oxy Controller. You will invite the bot, grant the permissions your modules need, open /settings, and verify that Oxy responds in your server.

What is Oxy?

Oxy Controller is a Discord bot and server-management platform. It combines moderation, automation, staff tools, community modules, Oxford Response integration, Roblox-connected workflows, and server templates. It is configured per Discord server — nothing you change in one guild is applied to another.

Setup steps

1. 01

   Invite Oxy Controller

   Open the Get Oxy link. Discord will ask you to choose a server and authorise the bot with applications.commands so slash commands can register. Use the production OAuth2 invite once it is configured — do not invent a client ID.

2. 02

   Choose the server

   Select the Discord server you want to configure. You must have permission to add bots to that server. After the invite, wait for slash commands to appear. If they do not, try restarting Discord or waiting a short time for command registration.

3. 03

   Grant required permissions

   Oxy only needs the Discord permissions for the modules you enable. Typical needs include View Channel, Send Messages, Embed Links, Read Message History, and Use Application Commands. Moderation may need Manage Messages, Moderate Members, Kick Members, or Ban Members. Tickets may need Manage Channels. Reaction roles and staff tools may need Manage Roles. Music needs Connect and Speak. Grant only what you intend to use. The bot role must sit high enough in the role list to assign roles below it.

4. 04

   Run /settings

   In any channel Oxy can see, run /settings. This opens the per-server configuration surface. If the command is missing, the invite did not include applications.commands, commands have not finished registering, or Oxy cannot see the channel.

5. 05

   Configure the server

   Start with General settings. Confirm the server is the one you expect, then enable only the modules you need. Unused modules can stay off.

6. 06

   Configure moderation

   If you want cases and staff actions, open the Moderation section. Choose whether actions create cases, and how those cases are stored and viewed. See the Moderation documentation for case IDs and lookup.

7. 07

   Configure logging

   Pick a log channel Oxy can write to. Moderation, AutoMod, staff, tickets, and other modules can send events there depending on what you enable. The channel should not be publicly writable if logs contain staff context.

8. 08

   Configure staff roles

   In Staff settings, choose which Discord roles count as staff and who may run /promote and /demote. Action logs should identify the responsible moderator.

9. 09

   Configure optional Oxford Response integration

   Only if you operate an Oxford Response private server and own the Oxford API package. Add the server key from Oxford’s Server Management → External → API Key. Never paste a real key into examples, tickets, or this website. See Connecting Oxford Response.

10. 10

    Test the bot

    Run /ping and /about. Then test one module you actually enabled — for example /help, a harmless /mod lookup, or /oxford if a key is configured. If a command errors, check channel permissions, role hierarchy, and the Troubleshooting section below.

Recommended first setup

1. Invite Oxy and confirm /ping responds.
2. Set a log channel.
3. Configure staff roles before promoting anyone.
4. Turn on moderation cases.
5. Add AutoMod only after you understand how cases are created.
6. Leave Oxford, Roblox, music, and templates off until the core staff flow works.

Permissions

Discord permissions are granted at invite time and can be changed later on the bot role and in channel overrides. Oxy cannot assign a role equal to or above its own highest role, and cannot moderate members whose top role is above the bot.

Updating Oxy

Server configuration lives with Oxy, not in a file you edit by hand. When the bot process is updated by the operator, slash commands and module behaviour can change. After an update, re-open /settings and confirm the options you rely on. This site documents V5 behaviour; if a control is missing in your server, the installed version may differ.

Troubleshooting

Slash commands do not appear

• Confirm the invite included the applications.commands scope.
• Wait for Discord to register commands, then restart the Discord client.
• Confirm Oxy is still a member of the server.
• Try /help in a channel the bot can see.

Oxy says it is missing permissions

• Inspect the bot role and channel overrides.
• Move the bot role above roles it needs to assign, without placing it above roles it should not control.
• For tickets, grant Manage Channels in the category where tickets are created.

/settings does not open

• Run the command in a server channel, not in a private message, unless your installation explicitly supports DM configuration.
• Confirm you have the permission Oxy requires to change settings — typically a server administrator or a configured staff role.

Oxford commands fail

Confirm the server key is present in settings, that the Oxford API package is active on that Oxford server, and that https://api.oxfd.re/v1/health is reachable. Never rotate or paste keys in public channels. See the Oxford Response documentation.