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 20, 2012 at 00:45 UTC - 0 likes

    @tiwar: Go

    Please read the FAQ.

    @Carnaxus: Go

    As long as you're running the latest build of CraftBukkit you are able to use the latest build of LogBlock.

    @Wizards1234: Go




  • Avatar of Wizards1234 Wizards1234 Aug 19, 2012 at 22:46 UTC - 0 likes

    Just wanted to point out that "/lb commands" gives a line that says

    Look at github.com/DiddiZ/LogBlock/wiki/Commands for the full commands reference.

    Just wanted to let you know so you could edit it. :D

    Gamer. Brony. Tweeter (Twitter person). Server Manager. Failure at using Permissions Plugins like PermissionsEX...

  • Avatar of Carnaxus Carnaxus Aug 19, 2012 at 22:09 UTC - 0 likes

    My CraftBukkit build is 2149...which version of LogBlock works? Thanks!

  • Avatar of tiwar tiwar Aug 19, 2012 at 14:31 UTC - 0 likes

    hi i also experiences "queue overloaded" spam in the console. I was alone on the server and it spams. Now running 1.5.8. I changed time per run to 1000 and delay betweenruns to 1. but no difference. I never had this problem before from 1.5.7 and backwards

    Last edited Aug 19, 2012 by tiwar
  • Avatar of vxnick vxnick Aug 19, 2012 at 10:35 UTC - 0 likes

    @zSwayz: Go

    Thanks - I tried that but still no luck. Here's the relevant part of the config (Essentials Group Manager):

        - -logblock.rollback
        - -logblock.clearlog
        - -logblock.hide
        - logblock.*
  • Avatar of Pr4w Pr4w Aug 18, 2012 at 17:09 UTC - 0 likes

    Hey, is there a way to convert from Hawkeye to Logblock ?

  • Avatar of jamietech jamietech Aug 18, 2012 at 02:40 UTC - 0 likes

    @Hvarr: Go

    permissionDefault is if the permission is given by default. TRUE means all players have it, FALSE means players only have it if it's assigned to them.

    @zSwayz: Go

    Check the FAQ.

    @Bimmr: Go

    Give them the correct nodes.

  • Avatar of zSwayz zSwayz Aug 18, 2012 at 02:26 UTC - 0 likes

    @vxnick: Go

    try giving them logblock.* then negating all permissions you don't want them to have before that node.

    I do things.

  • Avatar of vxnick vxnick Aug 17, 2012 at 19:50 UTC - 0 likes

    @Hvarr: Go

    I'm having the same problem - I've added the permissions "logblock.tools.tool" and "logblock.tools.toolblock" for my moderators, but they still don't have permission to spawn the tools (they also have the "logblock.spawnTools" permission). I have no problem spawning them myself.

  • Avatar of Bimmr Bimmr Aug 17, 2012 at 19:48 UTC - 0 likes

    Staff doesn't have permission to use logblock tool...


    I have moved to SpigotMc.org If you would like to continue to get updates, please visit my projects there.


Date created
Aug 24, 2011
Last update
May 06, 2016
Development stage
  • enUS
Attribution-NonCommercial-ShareAlike 3.0
Curse link
Reverse relationships
Recent files