LogBlock logo

Works 100% with 1.7 / 1.8

The best block logging and rollback solution for the savvy server administrator.

LogBlock is the best block logging plugin for Bukkit server. Not only is it awesomely powerful, it’s blazing fast! Everything is logged into a MySQL database, allowing developers to hook in and produce things such as player stats and even administrative panels. Every loggable action can be logged with LogBlock: WorldEdit, leave decay, fire, sign changes, explosions, chest changes, player and animal deaths, chat, commands and more!

Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.

LogBlock will very rarely break between Minecraft / Bukkit updates, however if you find it does, please be sure to try a development build from above, as we generally test new releases there until deemed stable.

What is LogBlock?

LogBlock is a tool which allows you to keep track of almost everything on your server, while also giving you the ability to rollback (revert) or redo changes made by users and natural occurrences such as liquid flow or leaf decay. Additionally, LogBlock is able to log and rollback chest contents, sign text and more! LogBlock was originally created by bootswithdefer for HMod, ported to Bukkit by DiddiZ and is now actively maintained by md_5, ammar2 and the community of developers on Bukkit. We accept pull requests on GitHub frequently which means that community developers can add features they wish to see quicker than LogBlock developers are able to from tickets. All database actions are run not only in their own threads, but are queued into a consumer to minimize lag on the main thread. This is great for larger servers! All optional features (not dependencies below) are enabled and disabled from within the config file allowing complete control over what is logged thus ensuring database size is kept to a minimum.


Most virtual chest plugins are not compatible with LogBlock. Because they do not set the player who is opening the “chest”, LogBlock can’t do what it’s meant to be able to do, thus, making errors in your console. Please report these issues to the fake-chest plugin developer, NOT LogBlock developers.

Issues are read more frequently on the GitHub Issues page as compared to the comments below. When updating to LB1.57, if you already have a large database and have changed your columns to MEDIUMINT, INT or LARGEINT, you do not need the updater to fix this for you automatically. To stop this behaviour, simply change “version” in the configuration to ‘1.57’.

If you are experiencing an error such as this please read the FAQ for answers.

If you're receiving errors regarding players from the consumer such as "[Consumer] Failed to add player <playername>" then change all `playerid` columns to MEDIUMINT or INT in each table that contains them. This may take a long time if you have a lot of rows.

Optional Dependencies

  • WorldEdit (Recommended)
  • Permissions plugin
  • LogBlock Questioner

Need help?

Found a bug or an issue? Please report it (and attach code if you know how to squash it) on our ticket manager.

Just need help in general or have an urgent, more private bug? Join us on IRC at irc.esper.net #LogBlock and ping a +o or +v for faster help. Webchat is available here if you don't have a client, or prefer to use it.

As always, check if your question is on the FAQ before asking!


  1. Installation
  2. Permissions
  3. BigBrother log import
  4. Configuration
  5. MySQL Configuration

More Information

  1. FAQ (read me first!)
  2. Command reference
  3. Configuration
  4. Helpful Commands
  5. MySQL Connection Problems
  6. MySQL Schema
  7. SQL Queries
  8. Parameters

Are you a Developer?

If you wish to contribute to the LogBlock project, head on over to the GitHub page, fork the project and submit your pull request(s).

If you wish to develop a plugin that interacts with LogBlock in some way, read up on the API here. Support for API and more can be found in the IRC channel, which is listed above.

Developer builds can be found here. (These builds have not been approved by the BukkitDev staff. Use them at your own risk.)

Still need help? Join us on IRC at irc.esper.net #LogBlock and ping a +o or +v for faster help.

Please do not post comments requesting support. Report bugs here or, alternatively, talk to a real person. Commenting below is a surefire way to not receive help.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of jamietech jamietech Aug 13, 2012 at 23:35 UTC - 0 likes

    @bluehasia: Go

    There's a web-stats repo on DiddiZ's github, check that out, you might need to fork it and fix it though.

    @DuskShadowBrony: Go

    If it's the tool, right click the block you want information about. If it's the toolblock right click an air space for information or left click a block for information.

    @deleted_8156133: Go

    The main developer of Guardian, md_5, took over LogBlock as well and is solely working on it. Think of LogBlock as the new-old Guardian ;-]

    @CountIgor: Go

    Make sure that you're giving the right nodes. Check out the 'Permissions' page on the wiki.

    @Joeri1234: Go

    Please report bugs and requests to the issue tracker.

    @jwpwns: Go

    Check out the 'Permissions' page on the wiki. :)



  • Avatar of jwpwns jwpwns Aug 13, 2012 at 21:49 UTC - 0 likes

    what is the perm node for /lb toolblock and /lb tool i cant get it to work

  • Avatar of Joeri1234 Joeri1234 Aug 13, 2012 at 21:42 UTC - 0 likes


    I think there is a bug that chests are not rolled back correctly. I tested it myself. All block changes etc get rolled back correctly but not chests. Could you look into this please.

    Also is it possible to store the contents of a chest when it gets broken?

    thanks in advance.

  • Avatar of CountIgor CountIgor Aug 13, 2012 at 21:16 UTC - 0 likes

    Better and faster than ever, which is great, but I can't get my permissions working. Neither 'logblock.*' or any single nodes seem to work. Only OPs have access. I use bPermissions 2.9.14

    Last edited Aug 13, 2012 by CountIgor
  • Avatar of deleted_8156133 deleted_8156133 Aug 13, 2012 at 18:59 UTC - 0 likes

    @jamietech: Go

    That's very sad. They start that plugin to take over HawkEye, LogBlock, and BigBrother. Then they just abandon it. Wow.

  • Avatar of DuskShadowBrony DuskShadowBrony Aug 13, 2012 at 16:41 UTC - 0 likes

    After i get the wand, how do I find out who broke a block? I looked at the commands but saw nothing to do this.

    ~~ MineZ Survival Expert (Globally Ranked)

  • Avatar of bluehasia bluehasia Aug 13, 2012 at 14:15 UTC - 0 likes


    i was referring to more like a website page that can read the data base and put say all the information about one player up for display

    Last edited Aug 13, 2012 by bluehasia
  • Avatar of abcedea abcedea Aug 13, 2012 at 11:22 UTC - 0 likes

    @bob7l: Go

    Worldedit's can already be logged, but not in this plugin. (See CoreProtect, I assume it'll be implemented soon along with physics and piston logging etc) I use both plugins, LogBlock for its speed in rollbacks, and CoreProtect to ensure large-scaled griefs are rolled back properly. :)

  • Avatar of bob7l bob7l Aug 13, 2012 at 08:06 UTC - 0 likes

    Well now I'm just confused, you force people to use worldedit yet the plugin doesn't log worldedit's? Is this planned? I'm sure the current worldedit dev wouldn't mind adding support for logblock :)

    Open for custom plugins! Skype: bob7l.bob7l.bob7l

  • Avatar of jamietech jamietech Aug 13, 2012 at 07:26 UTC - 0 likes

    @yurikoma: Go

    Click on the downloads section here

    @bluehasia: Go



Date created
Aug 24, 2011
Last update
Jul 25, 2015
Development stage
  • enUS
Attribution-NonCommercial-ShareAlike 3.0
Curse link
Recent files