Fix an ajLeaderboards board that shows missing or stale values

Check an ajLeaderboards ranking in three places: the original statistic, the board's recorded values and the display plugin. A hologram showing old numbers does not establish that player statistics disappeared. Avoid resetting either store while identifying the failed stage.

Record the board and its source

These steps assume supported builds of ajLeaderboards, PlaceholderAPI and the plugin supplying the statistic. Check their release requirements against your Minecraft version. Note the board's exact name and the placeholder that supplies each player's numeric value. Keep ajLeaderboards data and the source plugin's storage before configuration changes.

ajLeaderboards expects a normal numeric placeholder, allowing commas but not descriptive text. Use a per-player value rather than another plugin's existing top-ten or leaderboard placeholder. A result such as 12 wins differs from a plain number, and a placeholder that remains unexpanded needs fixing at its source.

Check source and registration

Use the documented PlaceholderAPI parsing command for one known online test player. Confirm that the source returns the expected number for that player.
Run /ajlb list as an authorised administrator. Check whether the intended board exists and copy its spelling.
If you intend to create a genuinely new board, use /ajlb add %statistic_player_kills% as a documented example only after verifying that this is the statistic you want. Do not add a second board simply because the first display is wrong.
Use statistic_player_kills, without percent signs, where a command or display expects the board name. Keep percent signs around the complete PlaceholderAPI placeholder instead.

Test the display separately

Check one position's complete display placeholder against the official list. For the example all-time board, a name placeholder is %ajlb_lb_statistic_player_kills_1_alltime_name%. Keep the board, position, time type and output field consistent when comparing name and value.

If the placeholder resolves in a parsing test but appears literally on a hologram, inspect the hologram plugin's PlaceholderAPI support and update interval. Do not replace the source statistic or clear the leaderboard data to fix a presentation problem. Start with one temporary line so you can compare the old and new display without changing every board.

Understand offline and timed values

Some source plugins cannot calculate an offline player's value through their placeholder. Test an online player first and read the source plugin's offline support. Avoid launching a full offline-player refresh on a busy server before understanding its workload and storage access.

Use timed boards for cumulative statistics that increase over time. The official setup guide distinguishes those from non-cumulative values such as a high score, where an all-time display is appropriate. A monthly label does not make every metric a meaningful monthly competition.

Recover the display without erasing history

Restore the previous placeholder line or configuration if the trial fails. Keep source stats unchanged. Send support the source result, board name, complete output placeholder, player online state and redacted errors. A board cache reset is a deliberate history change, so reserve it for a reviewed reset plan rather than routine troubleshooting.

collect the relevant Minecraft logs · back up the server files · check PlaceholderAPI expansion setup

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