BlockLog

BlockLog records every relevant block event (place, break, interact, container transactions) into a SQLite database. It powers /bl inspect, lookup, rollback, restore and death-drop recovery.

What it does

Logs every block place, break, interact and container transaction.
Natural events (block spread, fade, leaf decay) are skipped so the inspect output stays readable.
Rollback restores attached blocks together: torches, ladders, signs, plants, doors, beds and double-chest halves come back as one unit.
Death-drop recovery snapshots a player's inventory the moment they die, so staff can hand items back without reconstructing them by hand.

Configuration

BlockLog:
  LoggingActive: true
  QueueSize: 50000
  BatchSize: 500
  FlushIntervalMs: 1000
  NearDefaultRadius: 10
  NearMaxRadius: 100
  NearSinceMs: 604800000

Key	Description
`LoggingActive`	Pause logging without disabling the module (e.g. for bulk admin work). The AdminGUI exposes a live toggle.
`QueueSize` / `BatchSize` / `FlushIntervalMs`	Performance settings. Defaults are fine for almost all servers; only raise `QueueSize` if the console warns about a full queue.
`NearDefaultRadius`	Default radius for `/bl near`.
`NearMaxRadius`	Hard upper bound for `/bl near`.
`NearSinceMs`	Time window for `/bl near` (default 7 days).

Permissions

Node	Grants
`muteessentials.blocklog`	`inspect`, `lookup`, `near`, `death`, `help`
`muteessentials.blocklog.rollback`	`rollback`
`muteessentials.blocklog.restore`	`restore`
`muteessentials.blocklog.deathrestore`	`deathrestore`
`muteessentials.blocklog.purge`	`purge`

/bl for usage
BlockLog config reference

BlockLog

What it does

Configuration

Permissions

Related

On this page