Command reference
Every active command, exact syntax, access level and related panel.
Browse commands →Luminox Documentation
This is the step-by-step manual for Luminox, a Discord-native, panel-first guild bot. Start with your role or task; every guide explains what administrators configure, which panel members use and what remains visible inside Discord.
Before you begin
These terms appear throughout the guides. Understanding them once makes the rest of the documentation much easier.
Choose a path
You do not need to read everything or understand the source code. Choose the guide that matches your next action and follow it in order.
Choose an edition, verify the guild, map roles and publish the first panels.
Set a timezone, verify a character, choose a main and receive the correct guild role.
Map Tibia promotions, demotions and registered Guest access to managed Discord roles.
See every reward source, level threshold, profile field and eligibility rule.
Understand continuous reward cycles, multiple units, attribution and pending registration.
Create hunts, bosses, quests and general events from their channel panels.
Configure treasurers, review deposits, accumulate small contributions and audit logs.
Protect selected channels, apply isolation and preserve an accountable audit log.
Add, review, edit and lift timed or unlimited Discord sanctions.
Connect reviewed characters, guilds and bounties to Community intelligence.
Understand level, death and guild-roster panels with rolling time windows.
Use safe refreshes, timed cleanup, automatic history limits and backups.
Understand permissions, what Luminox stores and which conversations remain in Discord.
Begin with one guild problem and find the smallest group of features that solves it.
Recommended setup journey
Use /install wizard to detect missing configuration without deleting existing data.
Configure guild, world, ranks, guest role and global moderator roles.
Assign dedicated channels for registration, economy, events, intelligence and support.
Use /install overview and test every panel with the correct access level.
Administrators use setup commands to publish and configure each system. Members and staff then use buttons, selectors, forms and private threads in the assigned Discord channels. No external web dashboard is required. Slash commands remain mainly for installation, private overviews, targeted maintenance and a few personal utilities.
Reference
Every active command, exact syntax, access level and related panel.
Browse commands →Every panel, setup command, prerequisites and intended audience.
Browse panels →Permissions, missing messages, failed interactions and synchronization checks.
Solve a problem →Use Use cases to choose the first useful module, review Trust & safety, then compare Free and Premium. You do not need to understand the architecture before starting.