Documentation · Troubleshooting

Find the cause before forcing a full refresh.

Use this guide when a command, panel, role or data update does not work as expected. Start with Discord permissions and saved configuration, then run only the smallest relevant refresh.

Registration

Character not found or verification delayed

  • Use the exact Tibia character name.
  • Confirm the character belongs to the Discord server's configured world.
  • Place the verification code at the beginning of the Tibia comment.
  • Wait for Tibia.com to expose the updated comment, then use Register character again with the same name.
  • Blacklist and Ban List restrictions are reported explicitly.
  • Timezone is completed inside the first registration flow when missing.

Roles and nicknames

Check hierarchy first

  • Luminox must be above every role it assigns or removes.
  • Tibia guild rank names must match mappings in /ranks overview.
  • Registered characters outside the guild receive Guest only when Guest is configured.
  • No registered characters means guild roles are removed and managed nickname cleanup runs.
  • Discord prevents bots from changing the server owner's nickname; this is reported as a skipped operation, not a sync failure.

Panels

Panel missing, stale or above newer messages

  1. Run /install overview and confirm the channel is configured.
  2. Check View Channel, Send Messages, Embed Links, Read Message History and Manage Messages.
  3. Use /install refresh for visible panels.
  4. Use the system-specific refresh when available.
  5. Reserve /update-all for actual character-data refreshes.

Buttons and private responses

Interaction failed or disappeared

Discord interactions must be acknowledged quickly. Retry once after the bot is fully online. Private responses intentionally expire according to their content: confirmations disappear quickly, while verification codes and paginated reading views remain longer.

Threads

Archived is not deleted

Support and completed-event threads are locked and archived. They disappear from the normal active list but remain in Discord's archived thread browser. Client cache can temporarily show an old thread or unread badge even after cleanup.

External data

Temporary fetch failures

A warning such as fetch failed usually means Tibia.com or the network did not answer that refresh. Luminox keeps the last valid panel and retries on the next scheduled cycle instead of replacing it with empty data.