Directory

Features

Each card is a module Oxy actually ships. Availability is either available now, configurable by the operator, or planned. Commands listed are the public slash commands related to that module — not invented subcommands.

Moderation

available

Moderation in Oxy Controller is case-based. Each action receives a unique case ID so staff can look up what happened, who was involved, and why — without relying on chat history.

Capabilities

  • Create and store moderation cases with unique case IDs
  • Look up and view existing cases
  • Log moderation actions to a configured channel
  • Apply server-specific moderation configuration
  • Integrate AutoMod events into the same case system
/mod/clear/settings

Configuration: Server settings → Moderation

Documentation

AutoMod

available

AutoMod watches for configured triggers and takes the actions your server defines. When AutoMod acts, it can create a moderation case with a case ID and write to the same logs as manual staff actions.

Capabilities

  • Configure AutoMod per Discord server
  • Define triggers and resulting actions
  • Bypass configuration for roles or channels
  • Log AutoMod events
  • Create moderation cases from AutoMod actions
/settings/mod

Configuration: Server settings → AutoMod

Documentation

Staff Management

available

Promote and demote staff through Oxy rather than editing roles by hand. Action logs record who performed the change. Additional roles and permission configuration live in server settings.

Capabilities

  • Promote members into staff roles
  • Demote members from staff roles
  • Assign additional roles as part of staff configuration
  • Record staff actions in audit logs
  • Control who is allowed to run staff commands
/promote/demote/settings

Configuration: Server settings → Staff

Documentation

Oxford Response

available

Oxy Controller integrates with the Oxford Response API at https://api.oxfd.re/v1. A server owner stores a server key in Oxy; staff then use /oxford to view server, player, location, and operational data. Exact fields depend on the current Oxford API.

Capabilities

  • Store an Oxford Response server key per Discord server
  • Run /oxford to inspect connected server data
  • View players, locations, and operational information when the API provides it
  • Troubleshoot connectivity against the Oxford API health endpoint
/oxford/settings

Configuration: Server settings → Oxford Response

Documentation

Roblox Linking

available

Members can link a Roblox account through Oxy. Linked accounts support verification workflows, Oxford Response relationships, and shift checks that need a Roblox identity.

Capabilities

  • Link a Roblox account to a Discord member
  • Verify the linked account
  • Use the link in Oxford Response and shift workflows
/roblox

Configuration: Server settings and the /roblox command

Documentation

Templates

available

Oxy Templates allow Discord server layouts and configurations to be packaged, shared, and reused. Discover public templates on the template platform, copy a template link, and ask Oxy to install it after confirmation.

Capabilities

  • Browse public templates on the web platform
  • Create, publish, and update templates
  • Share template links
  • Install a template into a Discord server after confirmation
  • Keep private templates restricted to authorised users and/or the owner
/templates

Configuration: Server settings → Templates, plus https://oxcontroller.app/template/

Documentation

Music

configurable

Oxy can join a voice channel and play audio through a configured Lavalink node. Queue, skip, pause, resume, and volume are available to members who have permission. Provider support depends on the Lavalink node — Oxy does not claim specific source catalogues.

Capabilities

  • Join a voice channel
  • Play, pause, resume, skip, and adjust volume
  • Maintain a queue
  • Restrict DJ actions through permissions
  • Use an operator-configured Lavalink node
/music

Configuration: Lavalink is configured by the bot operator; DJ permissions in server settings

Documentation

Tickets

available

Members open tickets into categories you define. Staff get access to the ticket channel, can close it when the issue is resolved, and can send a record to ticket logs if logging is configured.

Capabilities

  • Create tickets from a panel or command
  • Group tickets into categories
  • Grant staff access to ticket channels
  • Close tickets
  • Log ticket activity when a log channel is set
/tickets/settings

Configuration: Server settings → Tickets

Documentation

Applications

available

Create application forms with questions. Members submit answers; staff review, approve, or reject; and the outcome can be written to application logs.

Capabilities

  • Create applications with custom questions
  • Collect submissions in Discord
  • Review, approve, or reject submissions
  • Log application decisions
/applications/settings

Configuration: Server settings → Applications

Documentation

Suggestions

available

Members post suggestions into a configured channel. The community can vote, staff can respond, and the suggestion status can change as it moves through review.

Capabilities

  • Post suggestions to a dedicated channel
  • Collect votes
  • Allow staff responses
  • Update suggestion status
  • Log suggestion activity when configured
/suggestions/settings

Configuration: Server settings → Suggestions

Documentation

Reaction Roles

available

Build a role panel, choose the roles members can claim, add descriptions, and publish it. Members use the panel components to receive or remove roles, within the permissions you set.

Capabilities

  • Create and update role panels
  • Select roles and write descriptions
  • Use Discord components rather than legacy reactions where supported
  • Respect role hierarchy and bot permissions
/reactionroles

Configuration: The /reactionroles command and role permissions

Documentation

Giveaways

available

Create a giveaway with a prize, duration, and number of winners. Oxy ends the giveaway at the scheduled time and selects winners. Rerolling is available where the installed version supports it.

Capabilities

  • Create a giveaway with prize, duration, and winner count
  • End a giveaway
  • Select winners automatically
  • Reroll winners where supported
/giveaway

Configuration: The /giveaway command

Documentation

Shifts

available

Staff start and end shifts in Discord. When Roblox verification is enabled, Oxy can run movement or presence checks against the linked Roblox account. Checks may run periodically; exact intervals are set in the implementation, not documented as a fixed number here.

Capabilities

  • Start and end a shift
  • Store shift records
  • Optionally require a linked Roblox account
  • Run verification or movement checks when configured
/shift/roblox/settings

Configuration: Server settings → Shifts

Documentation

Server Configuration

available

Every Discord server Oxy joins has its own configuration. /settings is the control surface for general options, moderation, logs, staff, and optional modules. Changes in one server do not affect another.

Capabilities

  • Open a per-server settings flow with /settings
  • Configure modules independently
  • Inspect current configuration
  • Use /config, /serverinfo, and /about for related information
/settings/config/serverinfo

Configuration: /settings

Documentation

Developer Tools

configurable

Operators can inspect bot health from Discord and, where the installation exposes it, from HTTP. Website feature and template endpoints support the public site and template platform. Availability of each HTTP route depends on the current installation.

Capabilities

  • Check bot health from Discord with /health and /ping
  • Read bot information with /about and /website
  • Query HTTP health, status, bot info, and shard endpoints where enabled
  • Read website feature and template data where enabled
/health/ping/about/website

Configuration: Bot operator installation; see API documentation

Documentation