Documentation · Membership lifecycle

Reconcile characters that leave the configured guild.

This guide explains the automatic inactive-character flow used by Community and Founder editions: detection from the official Tibia roster, verification, retry safety, account-level eligibility, role changes, Loyalty resets, recruitment settlement and permanent Discord logs.

Requirements

It runs from existing Community identity configuration

Guild sourceA verified Tibia guild and world configured with /guild set.
Identity sourceCharacters registered through the permanent Registration panel.
Discord accessGuild rank mappings and an optional Guest role configured through the rank system.
Readable outcomeA configured moderation log channel for membership, role and Loyalty changes.

There is no manual “mark inactive” command. Luminox begins this workflow when a fresh official guild roster no longer contains a previously known member.

Detection flow

Roster differences become pending departures first

  1. Luminox stores the latest valid official guild roster.
  2. A later valid refresh is compared with the previous roster.
  3. Missing names enter a pending-departure queue instead of being penalized immediately.
  4. Up to ten pending names are verified per pass to keep work bounded.
  5. Confirmed results are grouped by owning Discord account before any connected system changes.
  6. Unresolved entries remain queued for a safe later retry.

Roster reconciliation is serialized per Discord server, preventing overlapping refreshes from resolving the same departure twice.

Verification safety

A missing row is not enough evidence

Character remains in the configured guildResolve the pending item without changing the account. This protects against transient roster inconsistencies.
Fresh Tibia data confirms the departureContinue to account-level reconciliation and evaluate every registered character owned by that Discord account.
Tibia data cannot be trustedKeep the item pending, log a warning and retry later. No Loyalty or role penalty is applied from uncertain data.

Account-level decision

All registered characters decide the outcome

Another registered guild character remainsThe Discord account stays guild-eligible. Loyalty is preserved and the log lists how many eligible characters remain.
No registered guild character remainsGuild-only access and rewards are reconciled because the account no longer represents an active member of the configured Tibia guild.
Discord account is absentThe guild departure can still be recorded. Role editing is skipped because the member no longer exists in that Discord server.
Character recordThe verified character is not deleted merely because it left the guild. Ownership and history remain available.

Main and Discord access

Identity remains; active guild representation changes

  • If the previous main is no longer in the configured guild but another registered guild character remains, identity synchronization can choose the highest-level eligible character as the new main and log the automatic change.
  • If no registered guild character remains, Luminox recalculates its managed rank and Guest roles with forceNotInGuild.
  • Unrelated Discord roles are outside this managed set and are not removed by the membership lifecycle.
  • Discord hierarchy can block a role change; blocked roles are listed in the moderation log rather than hidden.

Read Guild Rank Sync → for role mappings, Guest access and hierarchy requirements.

Connected value

Rewards follow current guild eligibility

LoyaltyAnother character remains: balance and eligibility remain. None remain: the balance is reset with reason left_configured_guild, private profiles are cleared and the change is logged.
RecruitmentAnother character remains: no departure settlement is required. None remain: recruitment records are notified and the still-unprotected reward portion is reversed according to the retention rules.
NicknameAnother character remains: the eligible main can be refreshed normally. None remain: Loyalty notation and managed identity are refreshed when Discord still allows Luminox to edit the member.

Current views and history

Active data and historical evidence have different jobs

  • Current guild lists use the latest official roster, so departed characters stop appearing as active members.
  • Guild-only Loyalty eligibility excludes accounts with no registered character left in the configured guild.
  • Historical Discord logs, completed events, support threads and other retained records are not rewritten just because membership ended.
  • The moderation log distinguishes Registered character left guild from Member left guild.
  • The log includes departed characters, previous ranks, remaining eligible characters, managed role changes, removed Loyalty and detection time.

Troubleshooting

Check the data boundary before forcing a refresh

Departure remains pendingTibia data could not be verified safely. Allow a later scheduled pass before treating it as a fault.
Account stayed eligibleCheck whether another character registered to the same Discord account still belongs to the configured guild.
A role remainedConfirm the role is managed by Luminox and that the bot role is above it in Discord hierarchy.
No readable log appearedReview the moderation-log channel configuration and the bot's Send Messages and Embed Links permissions.