Modrinth · Minecraft mod
blockchangetracker
A simple block change tracking mod
Quick answer
Which blockchangetracker release matches 1.20.6 Forge?
blockchangetracker 1.0.0 targets 1.20.1, 1.20.2, 1.20.3 with Forge. Do not install it on the client. It must be installed on the dedicated server. No extra mods listed for this file.
Where it goes
Is blockchangetracker required on the client, server, or both?
Do not install it on the client. It must be installed on the dedicated server.
This file is marked server-only.
What else does blockchangetracker 1.0.0 need?
1.0.0 on 1.20.6 Forge. Every mod below is checked against that same setup.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add blockchangetracker without breaking your instance.
Built for blockchangetracker 1.0.0 on 1.20.6 Forge. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use 1.0.0. It targets 1.20.1, 1.20.2, 1.20.3 with Forge; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
Do not install it on the client. It must be installed on the dedicated server.
- 04
Pick the file you checked
Use the “Get this file” button beside 1.0.0. It opens that exact file at the source.
About this project
What does blockchangetracker add?
Mod Description
Block Change Tracker is a Forge mod for Minecraft 1.20.1. It helps you track block break or place events within a specified cuboid area and records statistics to the vanilla scoreboard in real time. Whether blocks are broken by players mining manually, TNT explosions, fire burning, or other entity-caused block changes, all can be accurately tracked (configurable block whitelist filtering is supported). Region configurations are saved within the world save, so no reconfiguration is needed after reloading the game.
Key Features
Region Tracking: Define a cuboid region via commands and choose to track either block break or place events.
Multiple Destruction Source Coverage: Real-time detection of player block breaking/placing, plus periodic scanning to capture block changes caused by explosions, fire, the Wither, and other non-player direct actions.
Scoreboard Integration: Statistics are recorded to a designated vanilla scoreboard under the virtual player #blockchange.
Whitelist Filtering: Configure blocks to exclude from tracking (flame and soul fire are ignored by default to prevent miscounting from natural extinguishing).
Pause / Resume: Pause or resume tracking for all regions or a specific region, convenient for stage-by-stage observation.
Region Naming: Assign a custom name when creating a region for easier subsequent management (pausing/resuming a specific region).
Persistence: Regions, pause states, and scoreboard names are saved to the world save and automatically restored after restart.
Multi-dimension Support: Each dimension (Overworld, Nether, End) maintains its own independent tracking region list.
To customize the whitelist, edit the configuration file config/blockchangetracker-common.toml (generated after the first launch).
Command Tutorial
All commands use the /blockchange prefix and require sufficient permissions (admin permissions by default; directly usable in single-player mode).
- Create a Tracking Region
Basic syntax (without region name):
/blockchange <break|place> [regionName]
Parameter description:
: The scoreboard used to record statistics. It will be created automatically if it does not exist (type: dummy).
& : Two corner coordinates defining the cuboid region. Order does not matter; the mod automatically calculates the minimum/maximum coordinates.
<break|place>: Tracking mode. break counts block destruction events, place counts block placement events.
[regionName] (optional): Assign a unique name to the region for subsequent pause/resume operations. If omitted, the region has no name but can still be managed via the scoreboard name.
Examples:
/blockchange myboard 10 60 10 20 70 20 break
/blockchange myboard 10 60 10 20 70 20 place spawn_area
Notes:
If you create a region with an existing region name, the old region with the same name will be removed and the new one takes effect.
If the region name is omitted but you create a region with an existing scoreboard name, the old region bound to that scoreboard name will be replaced (to avoid duplicate counting).
Multiple regions can be created; even if they share the same scoreboard, scores will be accumulated.
Project description from Modrinth.
Pick your setup
blockchangetracker by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
1.20.5
1 loader build1.20.4
1 loader build1.20.3
1 loader build1.20.2
1 loader build1.20.1
1 loader buildCheck the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
blockchangetracker versions and loaders
1.0.0
blockchangetracker-1.0.0.jar
21 Aug 2026
Looking for an older file? The official Modrinth project page is in Resources.