Bot · Guild identity
Let Tibia promotions update Discord access.
Community Edition maps verified Tibia guild ranks to managed Discord roles, follows promotions and demotions automatically and gives registered outsiders a separate Guest role without touching unrelated server roles.
In plain English
The guild website becomes the authority for guild access.
Administrators connect each Tibia rank to the Discord role that represents it. When Luminox confirms a member's current rank, it removes the other managed rank roles and applies the correct one.
A registered character outside the configured guild can keep a Guest role instead. That allows guests to preserve verified identity without receiving member channels or guild authority.
One identity, one managed state
Roles follow current membership instead of old assumptions.
Replace the previous guild role.
The new mapped role is added and obsolete managed rank roles are removed in the same synchronization outcome.
Reduce access automatically.
Discord permissions follow the new verified rank rather than waiting for staff to notice the Tibia change manually.
Keep identity without guild access.
A valid registered character outside the guild receives the configured Guest role instead of a guild rank.
Remove only managed identity.
When no registered character remains, Luminox clears its managed guild and Guest roles while preserving unrelated Discord roles.
Connected safeguards
Restrictions cannot retain old guild access.
Ban List or Blacklist
Restricted accounts lose configured guild-rank roles even if the Tibia character remains registered.
Guest fallback
A restricted but still registered account can remain identifiable through Guest instead of receiving guild channels.
Role hierarchy
Luminox reports roles it cannot edit instead of claiming a successful synchronization.
Permanent moderation log
Important membership and managed-role transitions remain readable in the configured Discord log.
Registration links the Discord account to a real Tibia identity.
Luminox checks the configured guild and current rank.
The rank mapping or Guest fallback determines managed access.
Only editable managed roles change; the result remains traceable.
Stop maintaining promotions twice
Map each guild rank once and keep Discord aligned.
The technical guide explains rank mappings, Guest access, exact-name fallback, permissions, restrictions and safe troubleshooting.