Explain an EssentialsX balance leaderboard that looks out of date

Applies to: EssentialsX Economy; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A balance leaderboard may lag behind the provider’s current account values. Establish whether the issue is the ranking display, the underlying balance or a different economy service.

Before you start

EssentialsX economy settings affect player money and the plugins that use its economy service. Keep player UUIDs, the active provider and the exact EssentialsX build in your change record. Use a normal test account rather than an operator.

Work through the check

Choose two test accounts with known different balances, and record the active provider’s direct balance output.
Read the installed EssentialsX help and configuration comments for balance ranking and excluded accounts before changing anything.
Make one small documented balance adjustment on the test copy, then compare the direct result with the next leaderboard output.
Check whether a separate scoreboard or hologram plugin supplies the displayed ranking, including its refresh and placeholder settings.

What to compare

Compare a known player’s direct balance with their expected ordering rather than judging the first page alone. Offline-player inclusion and cached ordering can differ from a live balance lookup.

Confirm the result

The direct balance should reflect the controlled adjustment. The leaderboard should eventually order the included accounts according to its documented refresh behavior.

If the result differs

Do not assume the richest visible account represents every account in storage. Offline identity records, exclusions and another plugin’s cached ranking can make separate lists disagree.

Recover safely

Remove the test adjustment through a supported command. Keep the old display settings if changing exclusions exposes accounts you intended to hide; do not rewrite player balances to force a ranking refresh.

Documentation and related help

Check the EssentialsX Economy maintainer documentation and EssentialsX Economy maintainer reference against your installed release before applying changes.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report