Installation
Wizard plus permanent overview
/install wizard/install overviewThe wizard detects missing configuration and offers only the next safe steps. It does not erase existing channels, guild verification, roles or data. Overview always shows the active profile and current configuration.
Safe setup order
Configure authority before publishing member actions
- Verify the guild and world. This establishes the identity boundary for Registration and guild membership.
- Map ranks and Guest. Place the Luminox role above every role it must manage.
- Configure global moderators. Add every legitimate moderator role, then define specialist roles for protected modules.
- Publish Registration. Test verification, timezone, main selection and role synchronization with a controlled account.
- Add member panels. Events, Finder, Loot and Loyalty become useful once identity is reliable.
- Add protected operations. GuildBank, Recruitment, Guildhall, Support and moderation should be tested with both authorized and unauthorized accounts.
Discord permissions
Administrator is a Discord permission
Luminox does not maintain a second administrator list. A Discord member with the Administrator permission receives administrator access. Place the bot role above every rank, Guest, Alerts and specialist role it must manage.
| Permission | Used for |
|---|---|
| View Channels, Send Messages, Embed Links, Read Message History | Every configured panel and permanent Discord log. |
| Manage Messages | Stable-panel position, cleanup channels and obsolete panel removal. |
| Create / Manage Threads | Support, events, Guards and Website proposals. |
| Manage Channels | Online, Finder, Guard and event counters in channel names. |
| Manage Roles and Nicknames | Rank, Guest, Alerts and synchronized identity presentation. |
| Add Reactions | Event signup compatibility and Friend Time clock reactions. |
Even with the correct permission checkbox, Discord blocks changes to members or roles positioned above the bot. The server owner nickname is never editable by a bot.
Staff access
Multiple global moderator roles
/moderators roles add role:@Vice Leader/moderators roles overviewSpecialist actions add a second requirement: Treasurer for GuildBank review, Recruitment for recruitment review, Guildhall Staff for room management and category roles for Support. Administrators bypass specialist-role requirements.
Refresh tools
Choose the lightest correct operation
/install refreshRefreshes configured panels and avoids heavy Tibia character scans./registration refreshReposts only the Registration panel./guildbank refreshMoves the GuildBank control panel to the bottom./guildhall refreshRedraws Guildhall rooms and keeps the live controls below fixed logs./update-allAdministrator-only registered-character refresh with cooldown./updateMember refresh for personal registered data.Cleanup and history
Keep useful records without storing everything forever
- Automatic local backups run every 24 hours, retain 30 daily copies and 12 monthly copies.
- Support and event conversations remain archived Discord threads instead of being copied into another transcript store.
- Old Loyalty detail, GuildBank review detail and temporary states follow documented cleanup periods.
/autodelete setsupports immediate cleanup or timed deletion from ten minutes to thirty days;/autodelete disableremoves either rule explicitly.
Launch checklist
Test one allowed and one denied path
- Run
/install overviewand verify every configured channel and role mention. - Confirm a normal member cannot use administrator or specialist actions.
- Confirm a moderator without the specialist role is denied where two-role access is expected.
- Create one test registration, panel refresh, event and private ticket.
- Verify permanent logs remain above live control panels.
- Check mobile presentation and channel counters after the first automatic refresh.
- Keep the bot process owner, environment credentials and backup directory outside normal Discord staff access.
Operations
Stop cleanly and keep publishing credentials private
Run the bot with the project start or development script and stop the active process with Control + C. Backup management commands are intentionally not published to every Discord server.
The optional Website publisher is connected privately by the deployment owner. Never paste repository credentials into Discord commands, panels, screenshots or data files. Read the Website publishing guide →