Investigate a changed build before rolling it back
When a build changes unexpectedly, start by finding what happened rather than rolling back a whole area immediately. Block Log records useful player and environmental history. A small, reviewed rollback is easier to verify and less likely to undo somebody else’s work.
Add Block Log to your world
- Open the plugin page and choose an existing world you own, or create a new world with the plugin selected.
- Check the included requirements. Each world supports up to eight plugins, including dependencies.
- Start a sleeping world, or use the dashboard restart option for a running world. Adding, removing and updating plugins takes effect when the world restarts; coordinate with anyone playing.
Inspect the location and narrow the search
Operators can toggle inspection mode and click or attempt to break a block to read its history without changing it. Turn inspection off when finished. Use a player name, a time window and a radius around your position to narrow the lookup. Replace Alex with the player you are investigating.
/inspect
/lookup Alex 30m 16
/inspectReview before applying a bounded rollback
Back up important work and keep the affected chunks loaded. After checking the records, roll back only the intended player, time and area. Large jobs are spread over ticks, and unloaded locations can be skipped; the command starting successfully does not mean every matching location was changed.
/rollback Alex 30m 16
/blog statusCheck the result and correct a mistake
Walk the small test area and compare the blocks with the expected earlier state. Restore undoes the last rollback, not an arbitrary historical version. Unresolved restore entries remain recorded so you can load their locations and retry instead of losing them. Keep retention in mind when deciding how long to wait before investigating.
/restore
/blog statusCheck the result
- Make and log a harmless block change in a test area, then verify lookup, rollback and restore in order.
- Restart with a pending restore location unloaded; load it and check that the remaining restore can be retried.
Limits and compatibility
- Dropped items, mobs and every later physics change are not restored. Container transactions in unchanged containers are history, not general inventory rollback.
- This is not a backup replacement. Ambiguous legacy world history requires binding to its original world, not guessing a destination.
These instructions are for JetRift’s own Block Log plugin. JetRift does not install arbitrary Paper, Spigot, Forge or Fabric extensions. Commands use player names from your world; replace example names before running them. Operators can use the dashboard Console without the leading slash.
Full command reference · Current client and hosting limits