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.
-
View User Profile
-
Send Message
Posted Apr 15, 2012Why is a stable update taking so long?
-
View User Profile
-
Send Message
Posted Apr 15, 2012I've turned on Enderdragon logging. Where exactly is the killing of enderdragons logged?
-
View User Profile
-
Send Message
Posted Apr 14, 2012My son did this command /tppos 100000 1 1 and it fucked Logblock up totaly....
-
View User Profile
-
Send Message
Posted Apr 14, 2012I'm using multiverse, and when I do a lookup on a player with "world creativeworld" or "world survivalworld" I get all that player's results, from any worlds... I'm not sure if rolling back will roll-back only the specified world, or if it does all worlds also. I will test that later. Does anyone know why this problem might be happening?
-
View User Profile
-
Send Message
Posted Apr 12, 2012@wiiztec
Kidding me?
http://dev.bukkit.org/server-mods/guardian/
-
View User Profile
-
Send Message
Posted Apr 12, 2012How is such a prodigious plugin not updated yet?
-
View User Profile
-
Send Message
Posted Apr 11, 2012Will LogBlock ever be able to log & rollback natural block breakage (ex: if a sign pops off a dirt block that was broken) A bit like CoreProtect, that would be amazing :D
-
View User Profile
-
Send Message
Posted Apr 11, 2012@VegasBaby69
You have to change the config file change every thing to true
-
View User Profile
-
Send Message
Posted Apr 11, 2012For me when I use the logblock tool or the logblock block, it never tells me who placed what or anything. The bedrock is just placed and the tool does nothing.
-
View User Profile
-
Send Message
Posted Apr 10, 2012@mrchasez
Yup
-
View User Profile
-
Send Message
Posted Apr 10, 2012Does it keep creating an "import" folder for you guys too?
-
View User Profile
-
Send Message
Posted Apr 9, 2012@DoctorBoyd
Have you tried setting up a temporary server, with only logblock and questioner, with your current config folder and no other plugins? If this works without reproducing the error, more than likely it's conflicting in some way with another plugin. If the error does reproduce in this scenario, it is possible there is an issue with the database itself or the database server/ connection.
-
View User Profile
-
Send Message
Posted Apr 9, 2012http://diddiz.insane-architects.net:8080/job/LogBlock/
-
View User Profile
-
Send Message
Posted Apr 9, 2012@deleted_7554077
where is the download link then :O
-
View User Profile
-
Send Message
Posted Apr 8, 2012@nate302
The error shows up only when a player disconnects from the server.
I'm not seeing an error when using ./stop (I don't use ./reload).
-
View User Profile
-
Send Message
Posted Apr 8, 2012@DoctorBoyd
When is this happening exactly, does it happen when you do a ./reload command? Or is this only happening on a ./stop command?
-
View User Profile
-
Send Message
Posted Apr 8, 2012@arriej LogBlock 1.52 which is a development build is working just fine like forever.
-
View User Profile
-
Send Message
Posted Apr 7, 2012i think its time for an update, this one is not working with 1.2.5
jus saying, hoping on a fix A.S.A.P
-
View User Profile
-
Send Message
Posted Apr 7, 2012@Digitalink2008
Thanks. I was hoping to see it ingame through lb command, though.
-
View User Profile
-
Send Message
Posted Apr 7, 2012@ViscousSummer88
I have found out how to fix my issue... I had to make the MySQL database larger in the 'X' collum and that fixed it.