Simple flow
Member action, system check, useful Discord result
They use a command, panel, button, selector or form.
The relevant character, event, Loyalty, bank or staff system checks the request.
Guild settings, registered identities and current online data are read once where possible.
The bot updates a panel, counter, thread, log or private response.
Shared data
One online snapshot powers multiple Community features
In Community and Founder editions, Members Online, Enemies Online, Finder, playtime, event attendance and session statistics reuse compatible cached Tibia data. A panel refresh does not imply a new request for every displayed character.
Fast live panels without multiplying Tibia requests as new visualizations are added.
Storage
Keep important totals; clean temporary detail
- Account balances remain even after old reward details are cleaned.
- Looking for team, Guard duty and active reports remove themselves after their useful period.
- Support and event conversations remain in archived Discord threads.
- GuildBank and recruitment keep enough information to review or reverse a reward correctly.
- Guildhall keeps current rooms and occupants while permanent decisions remain visible in Discord logs.
- Daily backups retain 30 copies; monthly backups retain 12.
Service policy
Plans change refresh speed, capacity and useful history
| Plan | Eligible external data | Cached panels | Identity Tracker | History |
|---|---|---|---|---|
| Free | 15 minutes | 5 minutes | 60 minutes | 1 year |
| Core | 10 minutes | 3 minutes | 45 minutes | 2 years |
| Growth | 5 minutes | 2 minutes | 30 minutes | 5 years |
| Scale | 2 minutes | 1 minute | 15 minutes | 10 years |
| Founder | 1 minute | 1 minute | 15 minutes | No commercial cleanup |
These are service-policy intervals, not a promise that every system performs an external request on every cycle. Immediate actions can update a panel sooner. If Tibia or Discord temporarily fails, the last valid result remains visible instead of being replaced by an empty panel.
Editions
One foundation, three different purposes
Changing a public edition or plan changes capability and service policy without deleting the server's existing configuration. Founder activation remains restricted to the authorized Lumina server.