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.
Documentation isnt great. I am trying to clear my logfile. Helpfile says: /lb clearlog [params] Many options in the params list... Have tried /lb clearlog /lb clearlog world /lb clearlog world world /lb clearlog all /lb clearlog all world /lb clearlog all world world
So what is the command?
@deleted_7554077
Ive also had that issue when moving a server. it was because the server name in my server.properties was not capitalized correctly for the logblock config
@briankdk
water and lava flow tend to be the biggest offenders. Look into purging them
my logblock mysql database has grown so big that it crashes the game.....
can i do a command that clear all logs that are over 15 days old ?
Im guessig its this one:
/lb clearlog [params]
But im not sure excactly how, or what params i should use
Im on here looking for info on the error posted by Pr07o7yp3 below. It happens any time a player leaves.
I did post about it in the tickets section, but I don't think its been read.
CB2060, LB1.52dev Would love some info on what the problem might be.
This error spam my console:
@syonxwf
Strange issue...after this happened, other people on the server noticed that mcmmo was acting up as well, leaving people in berserker or superbreaker modes and not taking them out, as well as a couple other issues that just didn't make sense.
Found out the only thing I changed was one of my tips in the simpletips plugin a couple days ago, but just hadn't restarted the server yet. As soon as I restarted the server, it must have screwed something up (I have no idea if that is even the cause or a coincidence, I'm not a java programmer but it doesn't sound like something that would connect in any way, but meh). The tip looked like this: - '%ATip #5: %EType '/kit' to see what kits are available to you; you can use them once a day!' Didn't have the two pairs of single quotes around kit, like it needed. I don't know how that would cause issues with logblock and mcmmo, among others, but as soon as that got changed to normal it started working again.
Again this may have been coincidence, but that's all I changed back and it started working again.
No results on lookup? Recheck mysql settings and service.
I don't know what happened, but all of a sudden logblock has completely stopped working. I used logblock this morning (checked grief, banned griefers and rolled them back) without an issue. Left the house, came back 2 hours later and now it doesn't work. I can place the bedrock in a hole and it will stay there for a second and then appear in my inventory as normal, but nothing comes up in chat. I tried to do a lookup command and a rollback, I get nothing at all (not even an interal error). I was running dev build 108, so I upgraded to dev build 110, no change. I changed my sql database to a new one to test if the database was to blame, but that didn't change anything. I am at a loss here, mostly because it happened without anything changing at all...just plain stopped working.
I am now running my server without logblock and not too thrilled about it, anyone know what the cause of this is?
This Build right "Last stable build (#110), 5 days 21 hr ago" @cookie4270
@Tipj98
There is a dev build out for 1.2.3, I'm using it and it seems to run fine
Is log block updated or not?????
Is there any way from stopping everyone from being able to log with logblock i updated to a dev build recently and it seems all creative players can use the look up tool and i have checked my permissions and my logblock config and if i make lookup false it means no one can use the lookup tools its not critical that I stop this from happening but its slightly annoying
@FireZtreaM I find that just a bit annoying. no harm done really. Just a little imcompatibility with creative probably.
The text will reappear when you relog.
Cheers
I have a problem. I'm using Bukkit 1.2.3 R0.2 with LB 1.52 and LBQ from that mediafire-link.
The problem: If i hit a sign with the lookup-tool in gamemode 1 the signtext disappears. That problem didn't exist earlier. Is it a bug or have i missed something?
how do i UNDO a rollback ?
@nazerb
Download latest development build for LogBlock here - http://diddiz.insane-architects.net:8080/job/LogBlock/
Download latest custom compile of the LogBlockQustioner here - Link Removed: http://www.mediafire.com/?tpp2bzllwltp472
I think this works better then turt2live version. Sorry turt2live but on the rental server yours didnt't work :D
When you rollback you have to do /yes, when i type it in it say not a command?
So i cant rollback :/
Here is an issue I am running into:
There is a problem with your mysql database connection?