Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsUse LogBlock’s two-stage workflow: first run a narrowly filtered lookup, inspect the returned player, time, block and coordinate data, then run /lb rollback with the same filters. Back up the world and LogBlock’s MySQL database before a broad rollback. If the result is incomplete, do not immediately add force; LogBlock may be deliberately protecting newer edits or blocks excluded by its configuration.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Java servers with free DDoS protection and up to three free backups a day.
This guide covers the permissions, commands, parameters, review process, recovery options and failure cases involved in undoing griefing without erasing legitimate work.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What LogBlock records and can restore
LogBlock is a Minecraft server plugin that writes block changes to a MySQL database. Its project description covers breaking, placing, modifying and burning, while the server listing describes logging for nearly all block and entity changes, querying those records and rolling them back. Chest and sign changes can also be rolled back when those changes were recorded.
A rollback can only act on records that exist in LogBlock’s database. It cannot reconstruct an edit made while the plugin was disabled, disconnected from MySQL, misconfigured, or otherwise unable to log the event. Confirm that the plugin is enabled and that its database connection is healthy before investigating a missing change.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
Check your version before using commands
The published server listing documents native and tested support for major version 1.19. That is not a guarantee for every newer Minecraft release or every older LogBlock build. Check the plugin build installed on your server against the Minecraft version and test a lookup on a non-production world after upgrades.
Permissions and prerequisites
Give administrators only the nodes required for their duties. The important permissions are:
logblock.lookup— run/lb lookupand use lookup functions.logblock.rollback— run/lb rollback,/lb redoand write query logs.logblock.tp— teleport to a numbered lookup result with/lb tp.logblock.ignoreRestrictions— override rollback and lookup restrictions. Reserve this for trusted senior administrators.logblock.spawnTools,logblock.tools.toolandlogblock.tools.toolblock— use LogBlock’s in-game inspection tools.
The wildcard permission logblock.* grants every listed node. Treat it as full LogBlock administration, not as a convenient default for moderators.
You also need a current world backup and a database backup process that your staff know how to restore. A world-only backup may leave your audit history in a different state from the restored blocks; a database-only backup cannot restore the world itself.
The safe rollback workflow
1. Preserve a recovery point
For a small, clearly bounded incident, follow your normal snapshot policy. For a radius rollback, a long time window or an entire build, create a world backup and back up the LogBlock MySQL database first. Record the server time, world name and the exact command you intend to run. Do not treat a rollback as a substitute for a backup.
2. Run a narrow lookup
Start with the smallest area and shortest credible time window. For example, while standing near the damaged build:
/lb player Griefer area 30 since 2h destroyed coords limit 100
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
This asks for changes by Griefer within a square area of radius 30, during the last two hours, limited to destroyed blocks, showing coordinates and up to 100 rows. When running the command from the server console, include an explicit world parameter, for example:
/lb player Griefer world survival area 30 since 2h destroyed coords limit 100
Console commands require world <worldname> because the console has no player location.
3. Inspect every returned row
Confirm the player name, action, block type, timestamp, count and coordinates. A lookup result is evidence for the rollback scope, not an automatic approval. If the output is paginated or capped, raise limit deliberately and repeat the lookup rather than assuming the first page is complete.
Use /lb tp <number> to visit a numbered result when the lookup included coords. Without coordinates, LogBlock cannot determine where to teleport. At the target, compare the logged event with the current build and note any legitimate changes made after the griefing.
4. Execute the rollback with the reviewed filters
Once the rows and location are correct, run the matching rollback:
/lb rollback player Griefer area 30 since 2h destroyed
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
Use the same player, world, area and time filters you reviewed. The rollback command is also available as /lb rb and /lb undo. It applies to block changes and, when those event types were recorded, chest and sign changes.
Most installations ask for confirmation according to the askRollbacks setting. Read the confirmation and resulting count before accepting. The silent parameter suppresses questions and minimizes messages; reserve it for scripted, already-reviewed operations rather than interactive emergency work.
5. Check the result count and server messages
Compare the number of changes LogBlock reports with the rows you reviewed. Save console output when investigating a dispute. A lower count is not automatically an error: LogBlock checks the current block state and may skip an event if the block was changed again later or is protected by rollback rules.
6. Use last only after verifying the previous query
/lb rollback last reuses the parameters from the previous query. It is useful after a lookup when you have confirmed that the query is exactly the one you want to apply. Because it reuses the prior parameters, running an unrelated lookup first changes what last means. Treat it as a convenience shortcut, not as a safety check.
Free tools Windows power users keep installed
One-click scans. No signup required.
LogBlock parameters you will use most
| Parameter | Effect | Important qualification |
|---|---|---|
player <name> |
Includes changes by the named player. | Prefix the name with ! to exclude that player, such as player !Builder. |
area <radius> |
Searches a square around the current location. | area 0 targets one block for tool queries; console use still needs world and a location. |
loc x y z or loc x:y:z |
Targets a specific coordinate and can be combined with area. |
Use the coordinate format supported by your installed build and verify the world. |
world <name> |
Selects the world to search. | Required for console commands. |
created, destroyed, both |
Filters block action types. | Rollback defaults to all unless you specify an action type. |
before <time> and since <time> |
Define the time window. | Use a window wide enough to include the incident, then narrow it after reviewing timestamps. |
limit <number> |
Controls how many lookup rows are displayed. | The documented default is 15; it limits displayed rows, not necessarily the events in a rollback. |
coords |
Displays coordinates in lookup output. | Required when you plan to use /lb tp <number>. |
force |
Replaces a block even when its current type is not the expected type. | It can overwrite newer or unlogged work; use only after inspecting the conflict and preserving a backup. |
silent |
Suppresses questions and reduces messages. | It removes an interactive confirmation safeguard. |
last |
Reuses the previous command’s parameters. | Verify the immediately preceding query before invoking it. |
Practical rollback examples
Undo a player’s recent block breaking near a build
- Stand at the center of the affected build.
- Run
/lb player Griefer area 30 since 2h destroyed coords limit 100. - Inspect each row and teleport to suspicious results with
/lb tp <number>. - Run
/lb rollback player Griefer area 30 since 2h destroyedand accept the confirmation only when the scope is correct.
This is safer than rolling back every event in the radius because it excludes placements and modifications that may belong to other players.
Restore a known coordinate
For a single damaged block, use a coordinate filter rather than a large radius. A lookup can combine loc x y z with area 0 when using a tool query. Include the world when issuing the command from console. Inspect the event history before changing the block, because a location may have several edits by different players.
Exclude a trusted builder
When an incident area contains work by a player you want to preserve, use the exclusion form, such as player !Builder, and still inspect the resulting rows. Exclusion changes who is selected; it does not prove that every remaining event is malicious.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
Search both placement and destruction
Use both when you need to understand a complete griefing sequence, such as blocks being removed and replacements being placed. For an actual rollback, choose created, destroyed or the default all only after deciding which actions should be reversed.
Why a rollback may restore only some blocks
Partial results are often LogBlock’s safety behavior. The FAQ identifies two common causes: a block was modified later by another player, or it is listed in rollback.dontRollback. LogBlock avoids replacing a block when its current state no longer matches the state expected from the logged event, because doing so could destroy newer work.
Later edits by another player
Suppose a griefer destroys a wall and a builder repairs part of it before you roll back. Restoring the old destruction record across the whole area could remove the repair. LogBlock can skip that conflicting event instead. Look up the location again, identify the later edit and decide whether a narrowly scoped action is appropriate.
Protected block types
The dontRollback configuration can exclude dangerous or disruptive blocks such as lava, TNT and fire. This prevents an administrative mistake from recreating hazards. Review the configured list before assuming that a missing lava or fire change indicates a database failure.
Natural spreading blocks
The replaceAnyway setting affects naturally spreading blocks. Changing it alters how aggressively those states are replaced during a rollback, so check the configuration documentation and make a backup before changing it on a live server.
When force is justified
force tells LogBlock to replace a block even if its current type is not what the recorded event expects. That can recover a deliberately overwritten target, but it can also erase a legitimate repair or an unlogged edit. Use it only for a clearly identified conflict, with a recovery point, and never as the default response to a low result count.
Undoing a rollback and handling logs
Use redo to reverse an over-broad rollback
/lb redo <params> redoes the changes in reverse order and is the normal recovery path when a rollback removed too much. Keep the original command and its output so you can reproduce the exact parameter set. If the rollback affected a large area, stop players from continuing to edit that area while you verify the redo.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Keep world restoration separate from log deletion
/lb clearlog <params> deletes matching records from the LogBlock database. It does not merely hide them, and the command documentation warns that this operation ordinarily cannot be undone. Perform a lookup first, then use /lb clearlog last only when the immediately preceding query is the exact set of records you intend to delete. A world rollback does not require clearing the audit history; treat log retention as a separate maintenance decision.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchConfiguration switches that affect safety
askRollbackscontrols confirmation prompts before rollbacks.askRedoscontrols confirmation prompts before redos.askClearLogAfterRollbackcontrols confirmation around clearing logs after a rollback.rollback.dontRollbacklists block types protected from restoration.replaceAnywaychanges handling of naturally spreading blocks.
Review these settings in the active LogBlock configuration, not just in a template file. A silent command or disabled confirmation setting changes the amount of protection an administrator gets at execution time.
Troubleshooting “0 block changes found”
- Check the command syntax. Confirm the player name, action type, radius or coordinates, and time expression. Remove an overly narrow filter temporarily to test the log.
- Widen the time window. Replace a short
sincevalue with a longer period or add a matchingbeforeboundary if the incident time is uncertain. - Specify the world. Console searches need
world <worldname>; an incorrect world produces no matching rows. - Verify the exact player name. Names are not interchangeable with nicknames or display labels. Use a broader lookup to identify the recorded name.
- Check the action filter. A search for
destroyedwill not show a placement. Trybothwhen you are unsure. - Confirm that the block is logged. Use LogBlock’s lookup tool or toolblock feature on the target location and ensure the event predates the incident window.
- Inspect the server console. Look for MySQL connection failures, SQL errors, plugin startup errors or permission-denied messages.
- Investigate a partial result separately. Check for later edits and
dontRollbackrules before consideringforce.
A zero-result response generally means the parameters do not match, the event was not logged, or the selected time span is too short. It is not evidence that the blocks were never changed.
Operational practices for administrators
Use least privilege
Moderators who only investigate incidents usually need logblock.lookup, while the staff member who executes restorations needs logblock.rollback. Add teleport or tool permissions only when the role requires them. Keep logblock.ignoreRestrictions and the wildcard node with senior administrators.
Make every rollback reproducible
Record the operator, server time, world, lookup command, rollback command, reported count and any use of force or silent. This creates an incident trail independent of the blocks being restored.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Prefer several narrow operations to one uncontrolled radius
Divide a large griefing incident by world, player, time window or build. Review each slice, execute it, and check the result before moving to the next. This limits collateral damage and makes redo practical if one slice is wrong.
Test after upgrades
After changing Minecraft, LogBlock or MySQL versions, test logging, lookup, teleport and rollback in a disposable world. Confirm that permissions still resolve and that the active configuration contains the expected confirmation and blacklist settings.
Quick Recap
Decision checklist before you press confirm
- Is there a current world and database recovery point?
- Is LogBlock enabled and connected to MySQL?
- Did the lookup use the correct world, player, action and time window?
- Did you include
coordsand inspect the relevant rows? - Could another player’s newer work be inside the selected area?
- Are any target blocks protected by
rollback.dontRollback? - Are confirmation prompts enabled, and are you intentionally using
silent? - Have you saved the exact command so a mistaken rollback can be followed by
redo?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
