Documentation · Automation

Keep Discord clean without turning every refresh into heavy work.

This guide explains what Luminox updates, what it preserves and what it removes. It covers channel cleanup, live panels, scheduled data checks, temporary replies and local backups.

Channel cleanup

Delete messages immediately or by age

/autodelete set channel:#utility mode:Always/autodelete set channel:#utility mode:Timed minutes:60/autodelete disable channel:#utility

Always removes every new unpinned message immediately and works through older history in small safe groups. Timed removes messages after a chosen age from 10 minutes to 30 days. Disable removes whichever rule is active without needing to remember its mode or duration; using it again is safe and simply reports that Autodelete was already disabled.

ModeNew messagesExisting messagesBest use
AlwaysRemoved immediately.Cleaned gradually in small groups.Command or utility channels where normal conversation is not allowed.
TimedRemain until the configured age.Eligible old messages are cleaned over scheduled passes.Temporary coordination, media or short-lived discussion.
DisabledUntouched by Autodelete.No further cleanup from that rule.Normal channels or maintenance pauses.

Pinned messages are preserved. Autodelete changes only the selected channel rule and does not remove stable Luminox panels from unrelated configured channels.

Stable panels

Reuse when possible, reposition only when position matters

Most panels edit their existing Discord message. Final action panels such as GuildBank, Loot, Guildhall or Event Board may move to the bottom after a permanent log entry is published. Restarting the bot should discover and reuse stored message IDs rather than creating duplicate stable panels.

Edit in placeRoutine data refresh with no need to move the controls.
RepositionDelete/recreate only the live panel after a fixed audit message is published.
Split panelCreate the exact number of safe messages when Discord limits require pagination.
Fixed logNever rewritten as part of the live panel refresh.

Private responses

Expiry follows usefulness

Very shortSuccess acknowledgements and errors that no longer require action.
Reading timeOverviews, paginated histories and configuration details.
RegistrationVerification-code responses remain long enough to update Tibia.com and are removed when registration finishes.

Discord controls the underlying interaction token lifetime; Luminox schedules deletion within that supported window.

Refresh hierarchy

Do not use a heavy scan for a visual problem

ToolPurpose
/install refreshRedraw configured panels without heavy character scans.
System refreshReposition Registration, GuildBank or Support when required.
/updateRefresh one member's main identity.
/update-allAdministrator-only full registered-character synchronization.

Local backups

Automatic, rotating and owner-operated

  • One automatic backup every 24 hours.
  • Keep the latest 30 daily backups.
  • Create one monthly backup on the first day.
  • Keep 12 monthly backups.
  • Backup commands are not exposed to administrators of every installed Discord server.

Sustainable data

Balances outlive detailed history

Luminox keeps confirmed balances and the links needed for review while cleaning old reward detail, old transaction detail and temporary information. Full Support and Event conversations remain in Discord threads.

  • Cleaning old detail does not subtract the confirmed balance.
  • Pending records remain until staff reviews them or their documented deadline passes.
  • Looking for team, Guard and report information is deleted after it stops being useful.
  • Completed specialist requests use time and count limits while the readable Discord log remains available.

Read Trust & safety → for the wider storage and permission model.