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.
@deleted_7554077
dude.. you are awful aggressive in your post.. If someone has a problem, you should try to be nice and not be a dick with your responses. Telling them "Configure it correctly" is not helping at all. Trolls like you need to get their account removed. He was looking for an answer and instead got an asshole like you.
This plugin even with dev builds has issues on 1.2.3. Log block questioner does not load up. Getting these errors
@xsolar66
I had same problem with people having permissions to use tools.You can deny that permission, you should not have to do it but it will fix the problem.
just add this to your groups
logblock.tools.toolblock false
logblock.tools.tool false
Hmm I ran into an odd bug with the march 4th dev build. It worked perfectly fine at first for a while, However randomly stopped logging (server hasn't been restarted in about 2 days?)... I'll update this post when I get a server restart in. Hopefully it's a minor glitch and LB will reload fine.
Edit: The problem was, I was using the lb tool that was previously in my inventory from the last time I was on after just logging in. Allowing it to read but say no results found. I just got a new tool with the /lb tool command and it worked np
Looks like the permissions work just fine for me. Configure it correctly.
Hi @DiddiZ , It seems that on the latest dev build of LogBlock, it doesn't matter what permissions set up you use, if anyone gets their hands on a piece of bed rock, it can be used as a look up tool - even if they have no permission nodes for logblock whatsoever.
Do I really need to say that it is already working fine on CB 1.2.3
The reason why it isn't working is because you don't know how to configure it correctly :D
You guys need to update for 1.2.3!
@wzehrung
With this, LogBlock can't find permissionsex as permissions? This really needs to be fixed :/
A quick followup comment to my previous. Make sure your not running peerblock when trying to dload from the dev builds list :D
So is this
http://diddiz.insane-architects.net:8080/job/LogBlock/lastSuccessfulBuild/artifact/LogBlock.jar
Working with 1.2.3
Ofcourse it does :D I am not here to talk trash :D
I will help as much as I can.
Glad to see a person who got LogBlock working.
So follow wzehrung instructions :D
OK, so I removed everything related to LogBlock used the version here:
http:diddiz.insane-architects.net:8080/job/LogBlock/lastSuccessfulBuild/artifact/LogBlock.jar
and the LogBlock Questioner from here: Link Removed: http://www.mediafire.com/?tpp2bzllwltp472
LogBlock now WORKS, I can use the lookup tool AND it does log chest access WITHOUT Spout like KJanar had stated :)
Hope this helps others!
Help! I have logblock installed, but when I go to use the tool nothing happens. I have the database set up and the permissions installed. Help.
Please update this plugin soon! Thanks
It kept working with 1.1-R4 but 1.1-R6 doesn't work anymore..
Why is your database called lb-minecraft?
Haven't got that error yet
I got this:
OMG
Try a direct link then - http://diddiz.insane-architects.net:8080/job/LogBlock/lastSuccessfulBuild/artifact/LogBlock.jar
Hi guys, having consistent trouble accessing the dev builds site. I'm sure its getting hammered as this is a very popular plugin.. But would there be any other way to get a newer build to suit 1.2.3?
I laughed.
LogBlock 1.52 is working great for me. Logging everything, logs blocks, chest access if needed and NO SPOUT.
I said goodbye to SPOUT when VanishNoPacket stopped needing it.