LogBlock
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.
Notices
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!
Installation
More Information
- FAQ (read me first!)
- Command reference
- Configuration
- Helpful Commands
- MySQL Connection Problems
- MySQL Schema
- SQL Queries
- 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.
@Faffling94
Yes, it works with 1.5.2.
Use the latest dev build here: http://ci.md-5.net/job/LogBlock
I'm also having issues with actually logging. It seems to think it works fine, but it refuses to log any single thing. Yes, it's connected to MySQL, I've octuple-checked.
@xMinecraft
Its just worldedit debug, ignore
Accepted EditSessionFactory of type de.diddiz.worldedit.LogBlockEditSessionFactory from de.diddiz.worldedit
WTF?
Hello, whenever I do /rollback {params} (and I am op and the Owner to my server), it says that it does not detect any blocks. I am 100% sure I have the params down. To test this, i made a block, then i got a wooden pickaxe out and hit it, it said that i had created that block when I did. Then I got my wand out and selected the block, both first position and second position. I then did: /lb rollback sel 30 minutes
It said: 0 blocks found rollback aborted! I then went into the server log and all i saw was that i issued the command. I also heard something about a questioner and that i would have to type /yes or something, but i must not have that because I can do many commands without being asked. I have the latest 1.4.7 version (which works completely fine other than this problem on my 1.5.2 server) installed. Please help!
Doesn't wotk with me either
the explosion of tnt minecart : there is an issue because it's not recorded. thanks for update.
Doesn't work with 1.5.2
No issues here on 1.5.2 so far
According to my admins this does not work for 1.5.2 I can't get on the server to check for myself sorry I get the message "internal server error" (I'm working on fixing that as we speak/type
Please add Flatfile database support like SQLite, because my server-hoster has no MySQL-Database support!
@gbprogamer
I prefer logblock because of its efficient data storage methods. I think a global config would help so you wouldn't need to configure different logging standards on a per world basis, but other than that I find logblock to be better for my own server.
@Etsija
Use the bedrock on the chest/pedestal/etc or wherever the egg was, and it'll return all block edits to you.
@Etsija
Well you don't even need to look in them... Use the lookup command.
i like core protect much more
Hi, we have a tricky problem: someone on our server stole an enderdragon egg from another player, and we haven't been able to catch the thief with usual admin tools (pickaxe/bedrock). How would I start solving the mystery by looking into our MySQL tables?
@deancohen1994 If there is nothing showing up with /lb tool or /lb toolblock, check your console startup log and see if LogBlock throws you any errors, in the case it does, post them here.
@rautamiekka There is a permission which allows this to be asked, negative out the permission and you will not get this asking you. Alternatively, you can simple edit your config.yml to make it so it does not ask you this, ever.
@RaesWolf There could be...? Have you tried adding it to the custom ID's?
Cool plugin, but wehn you go to make the new version for 1.5.1?
@LeemurBFB
I believe it means that your mysql database size is too big. if you are using wamp I believe you can increase the integer limit on the database...hope I helped! :)
Attention ! with newest Dev-Build craftbukkit-1.5.1-R0.3-20130424.084500-7.jar was Logblock not working on my Server !