Universal Community

Bot · Installation

A working guild server starts with one clear route.

Add Luminox to a new or existing Discord server, choose the edition that matches your community and publish the first guided panel without learning a command-heavy workflow.

Add Luminox — Free Use the template route Keep my current server

No external dashboard. Installation, configuration, panels and daily use remain inside Discord.

Luminox helping two Discord administrators transform a guild hall blueprint into an organized set of live systems
Plan the structureConnect LuminoxPublish panels
Free to startInstall before choosing Premium.
Non-destructiveThe wizard audits instead of rebuilding.
Panel-firstMembers click controls after setup.
Edition-awareUniversal or Tibia-focused Community.

Three easy routes

Choose by starting point—not by technical skill.

Every route reaches the same Discord-native result. The difference is whether you are starting from an empty server, protecting an existing structure or deliberately enabling only selected modules.

Recommended for new servers Template-first

Begin with an organized structure.

Prepare the recommended channels and roles first, then let the guided wizard connect Luminox to that foundation.

See the recommended route Existing server

Keep what your community already uses.

Add Luminox, run the safe wizard and connect only the channels and roles your chosen systems need.

Protect the current structure Modular setup

Enable one useful function at a time.

Configure a single panel, verify the member experience and expand only when another workflow adds value.

Build module by module

See the destination

An organized channel structure. A real panel members can use.

The template route is not an abstract setup promise. The captures below show the kind of organized Discord structure and button-driven system you can build—with no separate web dashboard for your members to learn.

Recommended · Template-first

Start organized, then let Luminox make the structure operational.

This is the fastest route for a new or mostly empty Discord server. Begin from the recommended category, channel and role blueprint; then authorize Luminox and connect the bot to that structure through its guided installer.

Discord template

Creates the starting layout.

Categories, channels and roles give every future workflow a predictable home. You remain free to rename or reorganize the structure for your community.

Luminox wizard

Connects and publishes the systems.

The wizard selects an edition, audits what is missing and guides administrators toward the channels, roles and panels required by each enabled function.

  1. 01
    Prepare

    Apply the recommended Discord structure.

    Use the visible channel blueprint as your starting map, then adapt names and permissions to your community before publishing member-facing systems.

  2. 02
    Authorize

    Add Luminox to the server.

    Use Discord’s official OAuth screen, choose the target server and keep the Luminox role high enough to manage the roles and channels you intentionally assign.

  3. 03
    Guide

    Run /install wizard.

    Select Universal or Community Edition. Luminox checks the current server and explains missing requirements without deleting channels, replacing roles or wiping existing data.

  4. 04
    Publish

    Place the first permanent panel.

    Configure one channel, publish its panel and let members use buttons, selectors, forms and private responses instead of memorizing setup commands.

The template and the bot perform different jobs.

Discord creates the starting server layout. Luminox is authorized separately and then connects its systems to that layout. The bot never silently recreates or deletes your server structure.

Already have a server?

Add the bot without starting again.

The guided installer is deliberately non-destructive. It reads the current configuration, shows what is already usable and identifies only the missing pieces required by the edition or function you want to enable.

  • Your existing categories, channels and roles remain yours.
  • Registered identities, Loyalty history and permanent logs are not reset by the wizard.
  • You choose which channels receive panels and which roles operate specialist systems.
  • You can rerun the overview after future changes without republishing everything.
Install in my server Read the technical guide
Installation auditNon-destructive
✓
Edition selectedUniversal or Community
Ready
✓
Existing rolesPreserved and inspected
Ready
→
First panel channelChoose where members will use it
Next
○
Optional modulesEnable only when useful
Later
/install overview
Luminox operating organized Discord systems with guild members inside a fantasy workshop

No external control room

The configured system remains where your community already works.

Administrators use a small set of deliberate setup commands. Once a function is published, members and staff operate it through permanent Discord panels, buttons, selectors, modals, private responses and linked threads.

AdministratorsConfigure channels, roles, limits and editions.
MembersUse guided controls without learning setup syntax.
DiscordStores the visible panels, threads and permanent history.
Understand how Luminox works →

Modular installation

Start with the one workflow people will use this week.

You do not need to configure every Luminox system on day one. A focused rollout is easier to verify, easier to explain and easier for members to adopt.

1

Choose the friction

Private support, recurring events, member identity, moderation or another repeated task.

2

Configure its foundation

Assign the channel and responsible roles required by that function—not the whole product.

3

Publish the panel

Place one clear permanent control surface where the community already expects it.

4

Verify, then expand

Use /install overview, confirm the member experience and add the next useful module.

Permissions without guesswork

Give Luminox the position its assigned work requires.

Discord role hierarchy matters more than a long permission checklist. Luminox can only manage roles below its own role and only interact with channels where the server allows it to work.

01

Place the role correctly

Move the Luminox bot role above every guild or specialist role the bot is expected to assign or remove.

02

Choose purpose-built channels

Grant access to configured panel channels and private-thread entry points instead of opening unrelated areas.

03

Verify before inviting members

Run the overview, publish one panel and test it with the same permissions real members will have.

Review Trust & Safety Open the panel directory Check setup commands

One installation · two public contexts

Choose the edition during setup. Change the plan when capacity requires it.

The edition determines what Luminox understands. The plan determines available functions, limits, history and supported refresh speed. Both public editions begin with Free.

Any game or communityUniversal EditionGame-independent identity, panels and operations. Purpose-built for TibiaCommunity EditionCharacters, worlds, guild ranks and live Tibia context.

Before you install

Clear answers for the first decision.

The technical guide contains exact commands. These answers explain the installation model before you authorize the bot.

Does Luminox create or delete my Discord channels automatically?

No. The guided installer audits the current structure and explains what each selected function needs. You deliberately choose or create the channels and roles that Luminox will use.

Is the template route required?

No. It is the recommended starting point for new servers because it makes the final organization easier to visualize. Existing communities can preserve their current layout and connect Luminox to it.

Do members need to use slash commands?

Daily workflows are panel-first. Administrators use setup commands to configure and publish systems; members normally use buttons, selectors, guided forms and private responses.

Can I begin with only one function?

Yes. A modular rollout is encouraged. Configure one valuable workflow, test it with real permissions and expand only when the community is ready.

Can I change edition later?

Administrators can review edition and configuration choices without treating the server as disposable. Availability and migration checks still apply to edition-specific data and functions.

Do I need Premium before installation?

No. Universal and Community both start with a Free plan. Premium becomes relevant only when your community needs additional functions, capacity, history or supported refresh speed.

Ready when your server is

Install free. Publish one useful panel. Expand with evidence.

Add Luminox through Discord’s official authorization flow, follow the guided route that matches your starting point and keep every daily workflow inside the platform your community already knows.

Add Luminox — Free Follow technical installation Compare editions