Essential Core

Our multi-threaded processing allows you to get the best performance when using the mod.

Overview

• Records player actions (block breaking/placement, interactions, containers, etc.)

• Open Inventories, Ender Chests, and offline player ender chests.

• Performs periodic backups of player inventories and chunks

• Allows for rollback/restore of chunks and inventories

• Has an interactive inspector (with pagination) for consulting history

• Uses background processing (multithreaded) to avoid lagging the server

Core Features

• Fast and efficient data logging for various categories (blocks, containers, interactions, chat, commands, etc.).

• Rollbacks and restores (player/chunk) via commands.

• Multi-threaded

• Logs in files by category → player → date: essential-core /logs///<dd-MM-yyyy>.log. Configurable via config.toml (enable/disable logs, command filter, and thread count).

• Inspector with pagination and clickable buttons for navigation.

• Undo to revert the last rollback.

What does it log?

• NEW: inventory — Player inventory log

• NEW: enderchest — Player enderchest log

• The implemented log categories (FileLogger.java file) include — each log goes to essential-core/events///.log:

• block_break — block breaking by player

• block_place — block placement

• interactions — interactions with blocks/entities (right-click)

• containers — container opening with summarized content

• chat — chat messages

• commands — commands executed by players (filterable)

• sessions — player login/logout

• item_pickups — picking up items from the ground

• item_drops — dropped items (Event: EntityJoinLevel detects ItemEntity)

• item_transactions — (method exists in FileLogger; see note below)

• dimensions — dimension change

• game_mode — gamemode change

• entity_death — entity death

• entity_kills — entity killed by player

• console_commands — commands executed on the console

• server_events — server start/stop

• Observation: some logs are recorded with the player as "SERVER" or "CONSOLE" when applicable (e.g., entity_death records in entity_death/SERVER/.log).