Explain why CoreProtect has no record of an older action

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

An empty lookup can reflect scope, retention or logging settings rather than a broken database. Work through those possibilities before telling a player that an event did not happen.

Follow the procedure

Write down the reported world, location, account, action type and approximate time. Check the server’s timezone and whether the report refers to a different backend or restored world.
Run a read-only lookup with an explicit time range, small radius and appropriate action category. Check the exact world and position before broadening filters.
Inspect the relevant logging option in the installed CoreProtect configuration. Establish what was enabled at the incident time, using saved configurations or change records where available.
Check retention and recent purge history. Also identify any database replacement, migration or backup restore that could explain why older records differ from current gameplay.
Create a disposable action of the same supported type and query it after processing catches up. This distinguishes current logging failure from unavailable historical evidence.
Report the narrow conclusion: no matching retained record was found under the tested conditions. Keep uncertainty explicit and use other evidence before moderation or restitution decisions.

Check the result

The investigation should identify a concrete scope mistake, current logging fault or historical coverage limit where possible. A successful new test proves present logging only. It does not prove older events were recorded, and an empty historical result does not prove no event occurred.

If the result is wrong

If current actions are also missing, collect status and database errors and investigate the processing queue. Preserve the existing database while seeking support. Do not reinitialize storage, import random tables or accuse a player solely because one filtered query returned nothing.

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