1Roster change detectedPending
2Tibia character recheckedSafe retry
3Account eligibility resolvedAll characters
4Connected systems reconciledLogged
Bot · Membership lifecycle
Keep departed characters out of active guild systems.
Luminox compares the official Tibia guild roster with verified Discord identities. When a registered character leaves, it confirms the change before reconciling access, Loyalty, recruitment rewards and active guild views.
In plain English
Leaving the guild does not erase the member's identity.
A registered character can disappear temporarily from a roster refresh, so Luminox does not punish the account immediately. It verifies the character again and retries later when Tibia data cannot be trusted.
After a confirmed departure, the character remains registered for history and ownership. What changes is the account's active guild eligibility—and only when no other registered character from that account remains in the configured guild.
Account-aware decisions
One departed character does not automatically remove everything.
The account stays active.
Guild eligibility, Loyalty and access remain because the same Discord account still owns a registered character inside the configured guild. If the old main left, Luminox can select the highest-level eligible guild character as the new main during identity synchronization.
Guild eligibility ends cleanly.
Managed guild roles are recalculated, Loyalty is reset and unprotected recruitment value is settled proportionally. Unrelated Discord roles and the verified character record are not silently destroyed.
Connected outcomes
Every dependent system receives the same answer.
Discord access
Only Luminox-managed guild and Guest access is recalculated. Discord hierarchy safeguards still apply.
Loyalty eligibility
The account loses its active Loyalty balance only when no eligible registered guild character remains.
Recruitment protection
If the departed member generated a recruitment reward, only the still-unprotected portion is reversed according to elapsed membership time.
Active guild views
Current guild lists and eligible rankings stop treating departed characters as active members while historical Discord records remain readable.
What remains
History stays useful after access changes.
- Verified character ownership and stored identity history.
- Readable moderation and membership-change logs in Discord.
- Historical event, ticket and contribution records where their own retention rules allow it.
- The ability to recognize the account if the character later returns.
What changes
Only current guild state is recalculated.
- Current managed guild roles and Guest access.
- Eligibility to earn or retain guild-only Loyalty.
- Current guild lists, rankings and member-only workflows.
- Recruitment rewards that have not yet reached full protection.
Automatic, but explainable
See the exact verification and retry flow.
The technical guide documents prerequisites, account cases, role behavior, Loyalty settlement, logs and troubleshooting without asking staff to mark members inactive manually.