-
Notifications
You must be signed in to change notification settings - Fork 0
Frequently Asked Questions
Find answers to common questions about installation, performance, compatibility, and troubleshooting.
No. ChestLogger uses a lock-free, asynchronous MPSC memory queue. When a player opens a chest or moves an item, the event is intercepted and placed into an in-memory queue in under 0.01 milliseconds. All disk writes and LZ4 compression happen on a separate background thread, resulting in 0 ms main-thread tick impact.
Yes! ChestLogger was specifically engineered for low-end host durability. It writes sequential batches to prevent disk seek thrashing on shared HDD hosts, and features self-healing CRC32 tail checkpoints so sudden server kills/restarts never corrupt the database.
No. ChestLogger runs entirely server-side.
- Vanilla / Bedrock (Geyser) players can join without installing anything.
- If staff or players do install
chestlogger-fabricon their Fabric client, they get access to the rich in-game History Viewer GUI.
- Focused & Lightweight: ChestLogger focuses exclusively on high-throughput container tracking and non-destructive rollbacks, eliminating unnecessary database bloat.
-
Storage Size: Uses custom binary
.clogfiles with LZ4 compression (< 30 bytes/transaction) instead of massive SQLite/MySQL tables. -
Built-in Web Dashboard: Includes a live browser UI (
http://localhost:8080/) out of the box with zero external web plugins needed.
ChestLogger's Adaptive Recovery Engine automatically detects that only 27 slots remain. During a rollback, it restores items from the missing half into free slots within the surviving single chest instead of losing them.
You can configure the web server port (default: 8080) in:
-
Fabric:
config/chestlogger.json -
Paper:
plugins/ChestLogger/config.yml
All compressed transaction logs and spatial index files are stored in the server's world directory under:
-
world/chestlogger/data/(orworld/chestlogger/indexes/)