Why must I register a character?
Registration proves ownership and connects Discord identity to roles, events, Loyalty, GuildBank, Finder and guild membership.
Documentation · FAQ
Start here for quick answers about installation, panels, permissions, editions, data updates and common limitations. Each answer links to a detailed guide when exact steps are needed.
Frequently asked questions
These concise explanations cover the questions guild members and administrators ask most often.
Registration proves ownership and connects Discord identity to roles, events, Loyalty, GuildBank, Finder and guild membership.
Yes, if the character belongs to the configured world. A character outside the configured guild can receive Guest instead of a guild rank.
No. Every Community installation is bound to the verified guild world, so Luminox rejects characters from another world before registration can finish.
Member actions moved to persistent panels. Setup commands still publish and configure those panels.
Yes. Systems are modular. Registration is the recommended identity foundation, but administrators can publish additional panels gradually and verify each one before continuing.
No. /install wizard detects missing configuration and preserves channels, roles, registrations and stored history already connected to the server.
No. They belong to the Discord account. Character names are presentation and eligibility context.
Guild eligibility ends when no registered character remains in the configured guild or the account leaves. Moderation restrictions can remove roles while keeping registration records.
No. Finder reuses the same current online snapshot already collected for Watchlists instead of starting another Tibia request for every suggested player.
No. Monthly means a rolling 30-day window; yearly means a rolling 365-day window.
Their threads are locked and archived in Discord. Luminox does not duplicate complete conversations in its database.
Yes. The Support panel's My Tickets view links relevant created or staff-participated tickets, while Discord remains the storage location for the archived conversation.
A global moderator role grants common staff authority. Sensitive modules can also require a specialist role such as Treasurer, Recruitment, Guildhall Staff or a Support category role.
Discord does not allow a bot to modify the server owner's nickname.
Place the Luminox role above every managed role and member. Discord blocks a bot from managing identities positioned above its highest role.
No. Stable panel messages are reused where possible. Panels move or republish only when their process requires them to remain the final message.
Start with /install refresh. Use /update-all only for registered-character data.
No. Finder, Watchlists, Guild List, progression and other views reuse current online or registered-character information wherever possible.
No local process can send a message after it has completely stopped. Reliable offline alerts require an external uptime monitor independent from the bot host.
Read the Trust & safety, Administrator and Architecture guides.