Least practical access
Administrators configure systems. Moderators receive shared access through configured roles. Sensitive modules can require an additional specialist role.
Product · Trust & safety
Powerful guild tools should remain understandable and controlled.
Luminox shows who can perform each action, requires staff review for sensitive decisions and removes temporary details when they are no longer useful. Important conversations remain archived in Discord.
Design principles
Safety is built into every feature, not hidden in a setting.
Explicit review
GuildBank deposits, recruitment claims, room requests and other protected operations distinguish a request from a confirmed decision.
Automatic cleanup
Temporary reports, detailed reward history and completed requests follow clear retention periods instead of growing forever.
History stays in Discord
Support and event conversations remain archived Discord threads. Luminox keeps only the small amount of information needed to find and operate them.
Discord access
Roles define who can act
Luminox uses Discord's own Administrator permission for unrestricted server administration. It does not maintain a secret second administrator list. Global moderator roles are configured explicitly and specialist responsibilities can add a second role requirement.
AdministratorConfigures channels, roles, editions and protected systems.
ModeratorUses shared staff actions when one configured moderator role is present.
SpecialistAdds focused authority such as Treasurer, Recruitment, Guildhall or Support category access.
MemberUses guided panels where the enabled module and configured role rules allow it. Community Tibia systems can additionally require registration or guild eligibility.
Community Edition identity
Game ownership is proven before it becomes authority
Community Edition character registration uses a temporary verification code placed in the public Tibia character comment. The verified guild establishes the configured world, and the selected main drives managed nickname and rank behavior. A character cannot silently belong to two Discord accounts.
Blacklist and Ban List restrictions are checked against connected character identities. Staff actions retain the responsible Discord and character context in human-readable logs. Universal Edition does not claim game-character verification and uses Discord identity for its game-independent features.
Where information is kept
Keep only what the feature needs
| Information | Where it lives | Why |
|---|---|---|
| Server settings and linked accounts | Luminox data store | Panels, permissions and registered identities need it. |
| Support and event conversations | Discord private or archived threads | Discord already stores the complete conversation. |
| Images added to tickets | Discord attachments | The bot does not need a second copy of the file. |
| Approved public Website media | Website repository | Only reviewed files that pass automatic checks reach the gallery. |
Performance and external data
Collect once and reuse whenever possible
Online snapshots and registered-character data feed multiple panels: Watchlists, Finder, progression, Guild List and attendance can derive their views from shared current data. This avoids making a new Tibia request for every visible panel.
Heavy character synchronization remains separate from lightweight panel refresh. Administrators can redraw presentation without launching an unnecessary full scan.
Optional Website publishing
Review first; publish a cleaned web copy
The Website panel opens a private Discord proposal. Staff checks the description, credit and permission to publish. An approved file is then checked and cleaned by the publishing service instead of being downloaded onto the Luminox computer.
Private connection
Repository credentials are configured outside Discord. They are never entered into a panel, button or public message.
Honest limitations
What Luminox cannot promise
- A bot cannot modify the Discord server owner's nickname.
- A bot cannot manage a member whose highest role is above the bot role.
- Discord controls interaction-token lifetime and archived-thread availability.
- External Tibia or Discord outages can delay a refresh even when stored data remains safe.
- No local bot can report that it is offline after the complete host process has stopped; external uptime monitoring is required for that guarantee.
Before installation
A responsible administrator should verify five things.
- Bot role position and only the permissions required by enabled modules.
- Verified guild, world and Discord rank mapping.
- Global moderator roles and each specialist role.
- Private-channel visibility for Support, staff and review processes.
- Backup and credential ownership outside normal member access.
Need reassurance before installing?
Review the permissions or ask us in plain language.
Tell us which feature worries you and what access your guild is comfortable granting. We can explain the requirement without asking you to understand the source code.