PLUGIN GUIDE
FragGuard
Player-facing guidance for the plugins used on Pinnacle SMP.
WIKI LAST REVIEWED: SEPTEMBER 1, 2026This guide covers the published FragGuard 26.2-3 RC 1 feature set. Release-candidate behavior may still change before the stable release.
SECURITY & RECOVERY
FragGuard records world and supported block-entity changes for staff investigations, confirmed rollback jobs, restart recovery, and undo after griefing or accidents.
PLAYER PROTECTION Grief Investigation and Recovery
FragGuard records changes to the Minecraft world so staff can investigate damaged builds and restore an area to an earlier state. It works in the background and does not require players to run commands.
What FragGuard Records
- Blocks placed, broken, or structurally changed by players.
- Explosions, initial fire ignition, fire spread, and blocks destroyed by fire.
- Water and lava flow, bucket and dispenser changes, sponge absorption, and blocks broken by liquids.
- Piston movement and piston-related block changes.
- Entity-caused changes, natural formation, growth, fading, spread, leaves decay, structure growth, and fertilization.
- Supported block-entity data, including container contents, both sides of signs, banner patterns, player-head profiles, lectern books, decorated pots, and supported custom names.
- The location, time, before-state, after-state, and responsible player or environmental cause.
What Players Should Do After Griefing
- Do not rebuild or clean up more than necessary.
- Record the location and the approximate time the damage occurred.
- Contact an administrator and explain what changed.
- Allow staff to inspect the history before making major repairs.
Player Commands
There are no normal player commands. Lookup and rollback tools are restricted to administrators.
ADMIN ONLY Investigation and Rollback Commands
| Command | What it does |
|---|---|
/fg help | Shows FragGuard command help. |
/fg lookup r:30 | Shows recent block changes in a full-height radius of 30 blocks around the administrator. |
/fg lookup r:30 p:2 | Shows page 2 of the lookup results. |
/fg rollback r:30 t:2d 7h 15m | Previews the changes needed to restore the radius to that earlier time and returns a confirmation token. |
/fg rollback confirm <token> | Confirms the single-use rollback preview before any blocks are changed. |
/fg undo <job-id> | Reverses a completed or failed rollback job. |
/fg status | Shows database health, queue usage, coalesced changes, and dropped-write warnings. |
Lookup and rollback radii cover the full world height. Confirmed jobs receive durable IDs, resume after a restart, load existing chunks without generating terrain, and pause when server TPS falls below the configured threshold.
Important Limitations
FragGuard restores block type and structural data before restoring supported block-entity contents such as inventories, signs, banners, heads, lecterns, and decorated pots.
Unsupported block-entity types, or history recorded before block-entity snapshots were introduced, cannot be reconstructed.
Only changes that were successfully logged can be inspected or restored. Damage from before a logging feature existed cannot be reconstructed automatically.
FragGuard keeps recent history rather than a permanent record. Report problems promptly so the relevant logs are still available.