Templates

Templates

Package, share, and reuse Discord server layouts with Oxy Templates.

Oxy Templates allow Discord server layouts and configurations to be packaged, shared, and reused. The web template platform lives at https://oxcontroller.app/template/ — this documentation site does not replace that product.

  • /templatesIdentify a template from a link and run the install flow.

What a template contains

A template is a packaged server layout plus metadata: name, description, visibility, owner, and a stable link. The layout covers the supported Discord structure (channels, roles, and related configuration that the current installer knows how to apply). Oxy will not apply a layout without confirmation.

Public and private templates

  • Public templates can be discovered on the template platform and installed by servers that are allowed to use templates.
  • Private templates are restricted to authorised users and/or the template owner, according to the implementation. They must not appear in public discovery.
  • Visibility is chosen by the creator when publishing, and can be updated later.

Creators, ownership, and profiles

Each template has an owner. The owner can update metadata, change visibility, and publish new versions. Template profiles on the web platform show the templates a creator has made public. Ownership transfer, if offered, is defined by the platform — this page does not invent a transfer command.

Discovery, links, and metadata

Browse public templates at the template platform. Each template has a link you can copy. That link is what you give Oxy in Discord. Metadata (name, description, visibility) travels with the template so staff can confirm they are installing the right layout.

Intended installation flow

  1. 01

    Find a template

    Open https://oxcontroller.app/template/ and choose a public template, or obtain a private template link from the owner if you are authorised to use it.

  2. 02

    Copy its template link

    Use the platform’s copy-link control. Do not rewrite the slug by hand unless you know it is correct.

  3. 03

    Give the link to Oxy Controller in Discord

    Run /templates and provide the link in the way your version asks (option or follow-up). Oxy fetches template metadata.

  4. 04

    Oxy identifies the template

    You should see the template name, visibility, and enough metadata to know what will be applied. If identification fails, the link is wrong, the template is private, or the platform is unavailable.

  5. 05

    Confirm installation

    Oxy does not apply a layout until you confirm. Destructive or structural changes must not run on a silent yes. Cancel if the metadata is not what you expected.

  6. 06

    Oxy applies the supported server layout

    Only supported parts of the layout are applied. Anything the current installer cannot map is skipped rather than guessed. Review the server afterwards.

Downloads and one-click workflows

The web platform can expose download and one-click installation entry points. One-click still has to land in Discord and still requires confirmation inside Oxy. A download is a layout package; it is not an automatic apply.

Discord template import

V5 includes Discord template import where implemented. If your build exposes it, you can bring a Discord-native template into Oxy’s template system. Confirm against the installed version before promising this to a community.