Documentation · Server Boost Loyalty

Configure continuous Boost rewards safely.

This guide explains the Server Boost panel, one-unit reward cycles, multiple active boosts, registration requirements, historical reconstruction, unattributed totals and what happens when support ends before a period is complete.

Administrator setup

Publish the Boost panel in its own channel.

/loyalty set channel:#boosts system:Server Boost log

The selected text channel contains permanent boost lifecycle messages and the refreshed Server Boost Loyalty panel. The current panel remains below the fixed history and moves back to the bottom when a new log entry is published.

AvailabilityUniversal and Community Edition from Core.
Reward5,000 Loyalty Points per independently completed boost period.
Period30 continuous days per active boost unit.
ReviewProgress is reviewed hourly; the panel refreshes only when useful.
Member commandNone. Discord boost activity drives the system automatically.

One boost unit

Each unit completes one continuous 30-day cycle.

MomentStored resultLoyalty effect
Boost startsOne active unit receives its own start time.No instant points.
Period in progressThe panel shows the expected reward and next completion time.Still pending.
30 days completeA stable reward ID settles the period once.+5,000 points if eligible.
Boost remains activeThe same unit begins its next 30-day period.Next reward can complete later.
Boost ends earlyOnly the unfinished period is cancelled and logged.Previously confirmed rewards remain.
Removing or transferring a boost

Discord does not provide a transferable progress certificate. When an active unit disappears, Luminox cancels its unfinished period with the stored reason and elapsed progress. A later boost starts a new period.

Several boosts from one member

Ten boosts are ten separately tracked contributions.

When Discord provides enough activity information, Luminox reconstructs and maintains individual boost units rather than treating every booster as equal. If a member has three active units, the panel can show an expected 15,000-point reward when those three current periods complete.

  • Adding another boost creates another active unit; it does not reset older units.
  • Removing one boost cancels one unfinished unit rather than every active period.
  • Boosts shows current active units.
  • Total Boosts preserves current and previously completed contribution.
  • Top Contributors is ordered by total contribution, then current active boosts.

Account requirements

A completed period needs a verified Loyalty account.

The Discord member must satisfy the normal Loyalty rules: at least one verified character, current guild eligibility where required and no active Ban List or Blacklist restriction.

Eligible at completionThe reward is confirmed immediately and added to Loyalty history.
Not registered yetThe completed period becomes a pending registration reward instead of being discarded.
Registers laterLuminox releases valid pending rewards after successful character verification.
Leaves the serverActive unfinished boost progress is stopped; normal account-departure rules apply.
Why pending registration exists

A Discord boost can precede character registration. Keeping the completed period pending allows Luminox to reward the same real account later without assigning points to an unverified identity.

Discord data boundaries

Attributed and official totals are deliberately different.

Luminox combines Discord guild-member boost state, boost system messages and the official server boost total. Those sources can confirm that the server has a certain number of boosts without always identifying every individual historical unit.

Official boostsThe total currently reported by Discord for the server.
Attributed boostsActive units Luminox can safely connect to specific Discord members.
Unattributed boostsThe difference that cannot be assigned honestly with available Discord history.
Historical importActive start dates can reconstruct verified periods, but never invent missing unit ownership.

Unattributed boosts remain visible until later Discord information allows safe attribution or the official total changes. They do not generate guessed Loyalty rewards.

Permanent Discord history

Every lifecycle change explains what happened.

  • Boost tracking started records the initial active units and expected reward.
  • Server Boosts added records additional units without rewriting older progress.
  • Boost progress cancelled records removed units, elapsed days and cancelled expected points.
  • Boost reward confirmed records completed units, points and total completed periods.
  • Boost reward pending registration records earned but unidentified account progress.
  • Historical active boost imported records what was reconstructed and from which Discord source.

The private Loyalty profile separately summarizes active boosts, completed periods, confirmed points, pending points, in-progress points and next reward time. Return to the complete Loyalty guide →

Troubleshooting

Use the panel state before changing stored data.

SymptomMeaningSafest action
Unattributed boostsDiscord confirms more server boosts than identifiable active units.Wait for later Discord events; do not manually guess ownership.
Pending registrationA period completed before the member had a verified account.Have that same Discord account register a valid character.
Next reward appears unchangedThe displayed Discord timestamp is anchored to the real completion instant.Open the timestamp or wait for the next panel refresh; do not restart tracking.
Progress cancelledDiscord reported that one or more boost units ended or moved.Read the fixed lifecycle log for the reason and elapsed days.
Panel missingThe channel or message may have been removed.Run the same /loyalty set command for the saved destination.