PLUGIN GUIDE
FragGuard
Player-facing guidance for the plugins used on Pinnacle SMP.
WIKI LAST REVIEWED: AUGUST 5, 2026Plugin features, commands, and server permissions may change after updates. This guide may not always reflect the newest server version immediately.
SECURITY & RECOVERY
FragGuard records world changes for staff investigations and area rollbacks after griefing, accidents, fire, explosions, liquids, or piston damage.
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 or broken by players.
- Explosion damage.
- Fire spread and blocks destroyed by fire.
- Water and lava movement, including bucket changes.
- Piston movement and piston-related block changes.
- 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 | Restores logged block changes in the radius to their state from 2 days, 7 hours, and 15 minutes earlier. |
Lookup and rollback radii cover the full world height. Rollbacks are processed in batches to reduce server lag.
Important Limitations
FragGuard restores block type and block data, but it does not restore container inventories, sign text, written books, or other tile-entity contents.
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.