Block History

A server utility that keeps track of placing/destroying of blocks

4.8K Downloads

forgeneoforge

About this Mod

A server utility that keeps track of when a player interacted a block. (Currently it can keep track of block placing/breaking and exploding)

This server utility is meant for server owners to be able to check who griefed someones area.

The logging of explosion damage can be turned off in the config.

The mod comes with the following commands:

/blockhistory (This shows the latest 10 changes in chat. The amount it shows in chat is configurable))

/blockhistory log (This logs the recorded history to a log.txt file located in the blockhistory folder within the mods folder)

Akliz Partner

For questions feel free to join my Discord.

Want to support us?

-Mrbysco

Available Versions

Block History 1.3.1release

MC 1.20, 1.20.1forge, neoforge

January 3, 2025

How to Install Block History on Your Server

Order Server

Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).

Set forge Loader

In the panel under "Egg", select the forge loader and matching Minecraft version (26.1.2).

Install Mod

Open the mod browser in the dashboard and search for "Block History". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.

Compatibility

Mod Loaders

forgeneoforge

Minecraft Versions

26.1.2, 1.21.11, 1.21.8 (+19 more)

Server-side

✓ Required

Recommended RAM

4 GB(min. 3 GB)

Frequently Asked Questions

Block History server crashes on startup – what to do?

Most common cause: wrong forge version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (26.1.2). You can switch loaders with one click in the panel.

Is Block History compatible with forge and neoforge?

Block History officially supports forge, neoforge for Minecraft 26.1.2, 1.21.11, 1.21.8. The Mado dashboard automatically detects incompatible loader combinations.

Server lagging with Block History – how to optimize performance?

Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Block History consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.