Examples match release 1.0.0. Back up your configuration before editing. Use this plugin's reload command where supported; restart after dependency or JAR changes.
Inspect a block
Activate your license first. CoreProtect is not required; xCheck stores its own history.
Receive the inspector pickaxe. Hold it and click a block to open its recorded history; inspection does not break blocks.
Example
Inspect the adjacent position on the clicked face, including a position where a block was removed.
Inspector
Toggle inspection with any held item. Run the command again to leave inspection mode.
Example
Inspect the block you are looking at within six blocks.
Example
Look up recorded activity for an exact player name across worlds. Requires xcheck.player.
Example
Entries show player, action, material, world, coordinates, date and time. The hopper cycles action filters; arrows change pages. Filters apply to the already loaded result set.
GUI
Dates, limits and storage
Dates use dd.MM.yyyy HH:mm:ss, without milliseconds.
Change the display timezone using a valid Java zone ID. Invalid IDs fall back to UTC.
config.yml
Search the last seven days by default; accepted runtime range is 1 to 90 days.
config.yml
Load up to 500 entries by default; accepted range is 45 to 2000. Each menu page holds 45 entries.
config.yml
Rate-limit lookups per player. This does not add milliseconds to displayed dates.
config.yml
Delete entries older than the retention period at startup and hourly. Set at least one day; deleted history cannot be restored without a backup.
config.yml
SQLite storage is created automatically. Stop the server and back up the entire xCheck folder, including any WAL files, before upgrades.
Database
Apply timezone, messages and lookup settings. Retention is applied at the next scheduled cleanup or startup.
Example
What is recorded
Recording starts after installation with an active xCheck license. Earlier activity cannot be reconstructed.
Records player block breaking and placement. Cancelled events are ignored.
Recorded
Records block interactions, not proof that the final action succeeded.
Recorded
Records material-total additions/removals around player inventory actions. Metadata-only changes and moves with unchanged totals are not recorded. Automation acting at the same time can affect observed differences.
Recorded
Container entries use the inventory location. Inspect the other half if necessary.
Location
No rollback, CoreProtect import, item-metadata audit, or automatic hopper, explosion, piston, fluid or plugin-driven world-change logging.
Scope
Resolve missing history
An empty result does not prove that nobody changed a block.
Check activation. Recording and inspection need a valid key for product xcheck.
Example
Use Java 21 for Paper 1.21.x and Java 25 for Paper 26.x. Other server software, including Folia, has not been verified.
Compatibility
Increase the lookup period or result limit if needed, and check the configured retention period.
Troubleshooting
Database write errors or a full history queue are reported in the console. Check free disk space, filesystem permissions and startup errors.
