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.
- WorldEdit (Recommended)
- Permissions plugin
- LogBlock Questioner
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!
- FAQ (read me first!)
- Command reference
- Helpful Commands
- MySQL Connection Problems
- MySQL Schema
- SQL Queries
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.
Could someone update the Questioner?, DiddiZ announced on the LogBlock forum post today that he was giving up Mc, so he wont be updating anymore.. but someone could feel free to take the source and do it :/
Hi, I have a question. For some reason I cant see chest accesses. What I do is i type this command while im next to a chest that was USED AFTER I installed logblock so it should of logged it. So i type: /lb area 3 chestaccess and it says no chest accesses were made in this area. I used all the chests in my MPWorld but nothing...Any help?
@quickclay Latest is actually LogBlock 1.52
Link - http://diddiz.insane-architects.net:8080/job/LogBlock/
Logblock 1.51 seems to load fine in 1.2.3 CB 3024. Haven't tested if it actually works though. Seems to think 1.5 is newer than 1.51 though.
2012-03-05 07:01:27 [INFO] [LogBlock] Loading LogBlock v1.51
2012-03-05 07:01:27 [INFO] [LogBlock] [LogBlock] Version check: There is a newer version: v1.50
2012-03-05 07:01:27 [INFO] [LogBlock] [LogBlock] Connecting to [email protected]:mysql://127.0.0.1:3306/minecraft...
@waremanu Why isn't it working? Saying "Not working" doesn't tell us nothing and also you won't get any help or suggestions if we don't know thats wrong.
Post your LogBlock version. CB version, paste your config and the error message.
CB 1.2.3-R0.2 Developement build here - http://diddiz.insane-architects.net:8080/job/LogBlock/
Working LogBlockQuestioner here - Link Removed: http://www.mediafire.com/?tpp2bzllwltp472 (Other unofficial fix for LogBlock also included)
LogBlock don't work for 1.2.3-R0.1
So are you saying that the latest BigBrother dev build works with 1.2.3? As my server is currently under a lot of pressure to get the new bukkit but I require BigBrother or some other rollback plugin. I have found that LogBlock is not suited for rolling back water flow or lava.
If its not updated enough, but there are circumstances as to getting it work please PM me? I have had it working on my 1.1.0 servers, But with limited function.
how do i set it up if the database is on a different device(offline plugin testing)
There are dev build versions for 1.2.3 on Jenkins:
Just started to test #109.
Seems its the only of this tools that currently work on MC 1.2?!? no new dev builds for BigBrother or Hawkeye that I saw..
Edit: Correction, seems BigBrother has a new Dev-build too: http://ci.nexisonline.net:8080/job/BigBrother/
Thank you! I'm going to use this now :)
@Odiumxxx Lol I had posted it too with LogBlockQuestioner. So it wasnt really neccessary ... but i hope theres gonna be a offical release.
Updated for CB 1.2.3-R0.1
I loved this plugin, and needed it desperately for my server, so I've updated it for CB 1.2.3-R0.1
I've also noticed there's alot of fuss about working versions, and the inclusion of a functional questioner. So I've taken the liberty of including a freshly compiled version of the questioner.
Both are working fine on my CB1.2.3-R0.1 server.
Diddiz: You'll find I've sent you a Pull Request for the above update.
Thanks again for a brilliant plugin. :)
Hi, i need logblock for version 1.2.3 craftbukkit so i can start my server again :S Be hurry!!
umm it seems that logblock doesnt work for me..i downloaded both of the new player updated logblock and logblock questioner and it doenst seem to work....and it seems im not he only one..i have 1.2.3
is it me or does logblock not working for 1.2.3
my mysql is fine btw i tested with older version of logblock works just fine
Separate LogBlockQuestioner by turt2live - http://bit.ly/AcQDrE
I have the logblockquestioner jar, though.. it probably needs the update then. Ill look for it.
Well then you guys need the LogBlockQuestioner.jar I can't remember the link but there is one so look. I'll try to find it.
Did not work for me, I have that same problem. I even tried to remove Defaultcommands plugin and I still get Unknown command when I type /yes after a rollback question.
@EszesBence92 Lolz, mysql is a must have. No way around it.