GriefWatch
by qStars
GriefWatch is a client-side Fabric monitor that flags block breaks near other players, so server staff can follow up on possible griefing.
What it does
Each client watches for block breaks. When a break happens, GriefWatch finds the closest other player within a set range and checks whether that player swung their arm in the last couple of ticks. A break that lines up with a swing raises a red alert, which is the higher-confidence result. A break near a player without a matching swing raises a yellow alert, which covers a wider net and stays silent.
GriefWatch is a monitoring aid, not an anti-cheat, and its alerts are leads for a person to check. Its own notes warn that a red alert only identifies a suspect when that player's entity is loaded on the client, meaning within entity render distance. Beyond that range the server stops sending the swing packets, so the mod cannot match a break against them. The break itself still appears in the world, and the yellow silent alert covers that gap. The mod depends on Fabric API and is published for Fabric alone, for 1.21 – 1.21.11.
Key features
Dual alert system
Red and yellow alerts operate separately, and each uses its own distance limit and trigger count.
Swing-matched red alerts
A red alert is raised when a break and a nearby player's arm swing happen in the same window.
Silent yellow alerts
A yellow alert is raised without a sound when a break occurs near a player whose swing does not match.
Teleport to event
A red alert lets the viewer teleport to the event's coordinates, and a yellow alert does too.
Event log
Each event is stored with when it happened, where, the block involved, how far the player was, and whether the swing matched.
Compatibility
Latest build for each game version and loader.
1.21.x12 of 12 versions with builds
Only full game releases are shown. This mod publishes no snapshot builds.
Requirements
Dependencies declared by the latest file for each loader.
Required 1
Use cases
Who it’s for: Server staff and moderators who want leads on possible griefing, and players who run a client on a server with monitoring. It is not a tool for judging players automatically.
How it compares
Simple F3 master is client-side only, open source under the MIT License and published for 1.21.1 – 1.21.5, so it covers an earlier version range than GriefWatch. SkyTracker is also client-side only, under the MIT License, but is not open source and has files for 1.21.11 only. C.I.M.I.H. is client-side only, under the MIT License, not open source, and covers 1.21.7 – 1.21.11.
| Mod | Loaders | Game versions | Environment | Updated |
|---|---|---|---|---|
| GriefWatch | Fabric | 1.21 – 1.21.11 | Client-side only | 2026-07-12 |
| Simple F3 master | Fabric | 1.21.1 – 1.21.5 | Client-side only | 2025-05-25 |
| SkyTracker | Fabric | 1.21.11 | Client-side only | 2026-06-15 |
| C.I.M.I.H. | Fabric | 1.21.7 – 1.21.11 | Client-side only | 2026-05-13 |
Questions
Does GriefWatch need Fabric API?
Does the server need GriefWatch installed?
Can GriefWatch confirm who broke a block?
In the catalog
GriefWatch is one of 8,016 Management mods on ModsFinder, and one of 5,930 Management mods for Fabric. 19,862 mods support Minecraft 1.21.11.
Similar mods
What the author says
It's a monitoring aid, not an anti-cheat needed. Don't just go demoting players because 'the mod said so'. GriefWatch can only positively identify a suspect (a red alert) when the responsible player's entity is loaded on your client, which means they have to be within your entity render distance. Beyond that distance…
Official listing
- Modrinth page
- modrinth.com/mod/griefwatch
- Owner
- qStars
- Published
- 2026-07-12
- Updated on Modrinth
- 2026-07-12
- Facts verified
- 2026-10-15