Build Events
Adds build events to track block placements and breaks within an area
About this Mod
Build Events (Fabric)
This server-side mod allows you to create build events to track the amount of block placements and breaks within an area using scoreboard objectives.
Details
When a new build event is added, one or two objectives are created.
/buildevents add foo 3 1 4 1 5 9 both will create two objectives: foo_place and foo_break.
You can change how an objective's name is displayed on the sidebar using /scoreboard objectives modify foo_place displayname <plaintext or json>.
If an objective named foo_place exists prior to creating the foo event, then it will be used instead of creating a new one.
Usage
/buildevents add ... to create events. Optionally, end with in <dimension> to track actions in the specified dimension or with in !!global for every dimension, instead of the one the executor is in.
/buildevents remove ... to remove events. Optionally, end with remove_objectives to also remove the objectives.
/buildevents set <eventName> predicate ... to attach a predicate, in order to conditionally track actions. Here is an example for tracking specific blocks.
/buildevents set <eventName> predicate to remove an event's predicate.
/buildevents set <eventName> dimension ... to change an event's dimension or make it global(every dimension).
/buildevents set <eventName> total ... to toggle displaying the total amount of actions on the sidebar for each of the two actions.
/buildevents pause ... to stop tracking actions until re-enabled with /buildevents unpause ....
/buildevents list to view all existing events. Optionally, end with active or paused to view those specifically.
Syntax
/buildevents add <eventName> <from> <to> (place|break|both) [in] (!!global|<dimension>)
/buildevents remove <eventName> [remove_objectives]
/buildevents set <eventName> predicate [<predicate>]
/buildevents set <eventName> dimension (!!global|<dimension>)
/buildevents set <eventName> total (true|false)
/buildevents (pause|unpause) <eventName>
/buildevents list [active|paused]
Available Versions
How to Install Build Events on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set fabric Loader
In the panel under "Egg", select the fabric loader and matching Minecraft version (1.21).
Install Mod
Open the mod browser in the dashboard and search for "Build Events". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.21, 1.20.4, 1.20.3 (+5 more)
Server-side
✓ RequiredRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Build Events server crashes on startup – what to do?
Most common cause: wrong fabric 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 (1.21). You can switch loaders with one click in the panel.
Is Build Events compatible with fabric?
Build Events officially supports fabric for Minecraft 1.21, 1.20.4, 1.20.3. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Build Events – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Build Events 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.
Similar Mods
Rent Modded Server
Install Build Events with just one click on your server.