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.
clearly i'm dumb... fixed and actually working on MC 1.0.0
I can't get the dev builds to work on 1.0 MC at all, they seem to work, they load up and everything but they dont actually log, and trying a /lb rollback just errors every time.
Just running LogBlock and MySQL on the same server shouldn't have any performance issues or very little. The only time I could see you ever getting any performance issues is when your doing a very large rollback that requires the mysql server to do an extensive read. Creating alot of HD IO possibly bogging down your server when its doing the long read. I can safely say those type of rollbacks never happen or very rarely to not be a problem.
If you were to move your mysql server to an external server you wouldnt get the read lag, but you'd get a host of different things, like taking extremely long to do a read to an external server, all that data would have to go across the internet, increasing your network usage, which could be bad if you run on a limited amount of bandwidth
My server hosts about 20 people and the mysql server is on the same machine everything runs fine, I can say i get no lag while doing rollbacks, i keep logblock logs a month back the database is almost 2gb
I have talked to many plugin developers and they recommended running MySQL outside the server for BETTER performance? Can we get some feedback on this?
I would not recommend anyone to run the MySQL-server outside their own server. That would lead to bad performance since a lot of data would have to be transferred back and forth between the MySQL-server and the Minecraft-server, causing LogBlock to work a lot slower. It would also be an uptime-issue, you would be dependent whether that MySQL-server is online or not.
MySQL is free and easy to install, and you should run it on the same server, or at least on a server in the same network as your minecraft-server.
I guess the only reason you would need to rent an outside mysql-server would be if your minecraft-server is hosted in a place where they don't offer you a mysql-server.
LogBlock: Version check: Your version is up to date LogBlock: Connecting to [email protected]:mysql://localhost:3306/ LogBlock: Updating tables to 1.31 ...'
It sits there for about 3 min then crashes the server whenever i reload... Not sure what to do :?
Some plugin developers have switched to bukkitdev and/or just simply copied their old information onto bukkitdev. The forum thread of logblock is still active and the author has published a new logblock for the 1195 craftbukkit dev build: http://forums.bukkit.org/threads/info-admin-logblock-v1-30-chat-lookup-dynamic-tools-new-loggers-1185-1192.4543/
Any chance in getting lobglock updated to 1.8 1185?
You can get LogBlock from the official thread:
> > Download Here < <
i need the link D: now!!!
Shouldn't you file a ticket instead of leaving a comment?
@baggerboot I strongly suggest you don't post links to direct downloads unless you got them from DiddiZ or permission from him. Next time, post a link to the actual logblock thread.
Hey, brilliant plugin but I'm getting some serious problems. Logblock often doesn't work and everytime I attempt to use a command it prompts me with an error: 'Current queue size: x' It refuses to work until this counter hits 0, and it can be from anything from 500 to 80,000. It also goes up as well as down so once I see this error message I'm pretty stuck. I'm running CraftBukkit 1060 and LogBlock 1.26. Older versions (say when Craftbukkit was in the 900s) worked and so I know the config settings are set up correctly. Can anyone let me know what's wrong? Thanks.
Guys, bukkitdev's new...Everybody's got to move to the new system. It'll come. Just give a brother a minute. There's always the thread on classic bukkit if your authors haven't fully ported over.
I guess DiddiZ will update his post soon. For the people who really want to download LogBlock, here are the download links.
Link Removed: http://www.mediafire.com/?cz4qmvnwj82cb1d
Link Removed: http://www.mediafire.com/?gqn62kq5m7ebidt (recommended to download this one as well)
I am not the creator of LogBlock. All credits go to DiddiZ, not me. Also note that this is an older version (1.24 if I remember correctly), and I am not sure whether it is compatible with #1060 or not.
getting this.... any ideas?
12:11:44 [SEVERE] [LogBlock Consumer] SQL exception on INSERT INTO `lb-main` (date, playerid, replaced, type, data, x, y, z) VALUES (FROM_UNIXTIME(1314558702), 24, 0, 272, 0, '3184', 67, '1337');: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Out of range value for column 'type' at row 1 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3591) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3525) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1986) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2140) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2620) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2570) at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:779) at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:622) at de.diddiz.LogBlock.Consumer.run(Consumer.java:272) at java.util.TimerThread.mainLoop(Timer.java:534) at java.util.TimerThread.run(Timer.java:484)
No Download? If there is one i reccomend you put in a different spot. i cant see it :D
Worst page in history @DiddiZ :P