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.
Please update logblock to R5 b/c guardian does not seem ready.
@slade87 Wow thanks dude :D
I would prefer LogBlock but guess I have to learn hawkeye noe :D
just in case you need something for R5 in the meantime: http://dev.bukkit.org/server-mods/hawkeye/forum/other/32942-r5-update/#p7 I patched HawkEye to work for R5 for now so we can at least survive R5 until Guradian and stuff gets released
Depending on which comes out first Minecraft 1.2 or CraftBukkit R5 release then LogBlock won't work. Tested LogBlock on R5 1964 and it's broken. So use this on R4 1938 as long as you can. I am hoping for the Guardian plugin :D
It's probably because logblock.tools.tool and logblock.tools.toolblock are missing from the plugin.yml file.
Perhaps logblock.tp being included twice has something to do with it?
Anyway you can open the LogBlock.jar archive (it's a zip file) and edit the plugin.yml to add them in yourself.
Is this still updated properly? Since the last update was for #1337 and i am guessing the 1.2 is going to break this due to the double in the y value and the movearound with the way it stores coordiantes.
I had the same problem. The coordinate fields are too small. I think they were "tiny int". Open the database with the mysql workbench and find the `lb-minecraft` table. You can change the data type to "int" for the x,y and z fields. That should fix the issue.
I got this randomly:
Check your server log. I had that happen when i moved hosts. It was because after the move the server name in the server.properties file was not capitalized correctly for what logblock had initially been set up with. After making the change and restarting the server all was well.
just my experience. D.
I'm having trouble getting logblock to show results. The configuration and SQL is good. It is logging according to the tables. But I cannot seem to check a block after using the following: /lb t /lb t on nor with the toolblock command.
When I place the block or right/left click with my assigned item there is no response. I do run mcmmo which may be conflicting. But I get the feeling I'm missing a small command and just don't understand how to use the plugin like I did with BB.
Hi, I use HawkEye and thinking about switching to LogBlock, but I want to keep everything from HawkEye, I see you have BB import but not HE? =(
Hi i was wondering what is up with LogBlock atm as when i use either the /lb tool or lbblock it says ive made no changes no matter where i do it or use it it shows absolutely nothing can you please help Thanks exmental xD
Howcome my changes to the world weren't being picked up? /lb me said I've made 0 changes
I get this error and idk why
21:35:03 [INFO] [LogBlock] Version check: There is a newer version: v1.50 21:35:03 [INFO] [LogBlock] Connecting to [email protected]:mysql://localhost:3306/minecr aft... 21:35:03 [INFO] [LogBlock] Creating table lb-players. 21:35:03 [SEVERE] [LogBlock] Error while loading: Table 'minecraft.lb-players' d oesn't exist
Do /lb lookup block TNT created area 60 or something like that, you just have to lookup who placed the block TNT within a certain area/ time frame.
In your config file( for each world) , do you have sign text logging set to true? or false? also i think there is an option for paintings and such in there as well.
Does this plugin need to be/or has it been updated to the new bukkit events system?
Is it just me who can't rollback changes to signs, pictures, and ladders? Or is this a known bug?
Am I not supposed to be able to check the queue length from the console? I've noticed recently I get the message "You are not allowed to do that." when using
from the console.
am using lb 1.5 D.