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 Jan 1, 2013@PhanaticD
quote from the description
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.
-
View User Profile
-
Send Message
Posted Dec 31, 2012for pretty much every player that joing is says consumer failed to add player
-
View User Profile
-
Send Message
Posted Dec 31, 2012I have chest logging enabled but rollbacks do not seem to work for chest contents. I was looking at the commands but i see nothing about this can anyone fill me in on how to make this work?
-
View User Profile
-
Send Message
Posted Dec 31, 2012Hello can someone please help me i am trying to use 1.4.6 logblock and tryed the other one it wont generate a folder for my server i really need logblock please how to fix this? if someone can help me fix this reply please i really need this to work
-
View User Profile
-
Send Message
Posted Dec 30, 2012@jamitech: permissionbukkit all work if I use logblock.*: true but not single perm :|
-
View User Profile
-
Send Message
Posted Dec 30, 2012@FlashLight32
Which permission plugin are you using?
-
View User Profile
-
Send Message
Posted Dec 30, 2012@Hangar
Try this
http://forums.bukkit.org/threads/dev-logblockquestioner-v0-03-so-many-questions-1-2.20823/
-
View User Profile
-
Send Message
Posted Dec 30, 2012hello, if I use separate perms like logblock.lookup: false logblock.rollback: false logblock.clearlog: false logblock.hide: false logblock.tp: false logblock.me: false logblock.ignoreRestrictions: true logblock.spawnTools: true logblock.tools.toolblock: true logblock.tools.tool: true I got only the perm tools.toolblock with /lb permissions I trye to add logblock.*: true and negate other perm I don't want without success :| pls help me or fix this little bug thx in adavance :)
-
View User Profile
-
Send Message
Posted Dec 29, 2012My previous comment has been solved by changing the row type to bitint from int.
We now have another problem... 29.12 09:14:49 [Server] INFO at java.lang.Thread.run(Thread.java:722) 29.12 09:14:49 [Server] INFO at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 29.12 09:14:49 [Server] INFO at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 29.12 09:14:49 [Server] INFO at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) 29.12 09:14:49 [Server] INFO at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53) 29.12 09:14:49 [Server] INFO at de.diddiz.LogBlock.Consumer.run(Consumer.java:291) 29.12 09:14:49 [Server] INFO at de.diddiz.LogBlock.Consumer$BlockRow.executeStatements(Consumer.java:457) 29.12 09:14:49 [Server] INFO at com.mysql.jdbc.ResultSetImpl.getInt(ResultSetImpl.java:2702) 29.12 09:14:49 [Server] INFO at com.mysql.jdbc.ResultSetImpl.parseIntAsDouble(ResultSetImpl.java:7199) 29.12 09:14:49 [Server] INFO at com.mysql.jdbc.ResultSetImpl.throwRangeException(ResultSetImpl.java:7970) 29.12 09:14:49 [Server] INFO at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:927) 29.12 09:14:49 [Server] INFO at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:982) 29.12 09:14:49 [Server] INFO at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:987) 29.12 09:14:49 [Server] INFO at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1025) 29.12 09:14:49 [Server] INFO at com.mysql.jdbc.Util.getInstance(Util.java:382) 29.12 09:14:49 [Server] INFO at com.mysql.jdbc.Util.handleNewInstance(Util.java:407) 29.12 09:14:49 [Server] INFO at java.lang.reflect.Constructor.newInstance(Constructor.java:525) 29.12 09:14:49 [Server] INFO at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) 29.12 09:14:49 [Server] INFO at sun.reflect.GeneratedConstructorAccessor54.newInstance(Unknown Source) 29.12 09:14:49 [Server] INFO com.mysql.jdbc.exceptions.jdbc4.MySQLDataException: '4.294992861E9' in column '1' is outside valid range for the datatype INTEGER. 29.12 09:14:49 [Server] SEVERE [Consumer] SQL exception on insertion:
-
View User Profile
-
Send Message
Posted Dec 28, 2012@Hangar
There is one in the LogBlock 1.52 download, that's the version of the questioner I am using. Be sure to use the correct version of LogBlock though. http://dev.bukkit.org/server-mods/logblock/files/2-log-block-v1-52/
-
View User Profile
-
Send Message
Posted Dec 28, 2012Is there a link to the questioner on the main page here?
-
View User Profile
-
Send Message
Posted Dec 28, 2012We seem to have a continual error in our console...
28.12 12:09:25 [Server] INFO at java.lang.Thread.run(Thread.java:722) 28.12 12:09:25 [Server] INFO at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 28.12 12:09:25 [Server] INFO at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 28.12 12:09:25 [Server] INFO at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) 28.12 12:09:25 [Server] INFO at org.bukkit.craftbukkit.v1_4_6.scheduler.CraftTask.run(CraftTask.java:53) 28.12 12:09:25 [Server] INFO at de.diddiz.LogBlock.Consumer.run(Consumer.java:291) 28.12 12:09:25 [Server] INFO at de.diddiz.LogBlock.Consumer$BlockRow.executeStatements(Consumer.java:452) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2310) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2325) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2407) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2111) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2626) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2140) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1986) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3525) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3593) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1039) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.Util.getInstance(Util.java:382) 28.12 12:09:25 [Server] INFO at com.mysql.jdbc.Util.handleNewInstance(Util.java:407) 28.12 12:09:25 [Server] INFO at java.lang.reflect.Constructor.newInstance(Constructor.java:525) 28.12 12:09:25 [Server] INFO at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) 28.12 12:09:25 [Server] INFO at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown Source) 28.12 12:09:25 [Server] INFO com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '21665524' for key 'PRIMARY'
-
View User Profile
-
Send Message
Posted Dec 27, 2012@CollinPotato9
I'm pretty sure you have to enable this in the configuration.
@DanishDude93
Yes, you need MySQL to be configured for you to run most/any commands related to LogBlock. I'm sure it will give you an error if you don't have MySQL set-up when trying to start your server also.
-
View User Profile
-
Send Message
Posted Dec 27, 2012Is MySQL needed? Regardless of what lb command I execute, it says
"No database connected. Check your MySQL user/pw and database for typos. Start/restart your MySQL server."
-
View User Profile
-
Send Message
Posted Dec 27, 2012Hello. I am on LogBlock version 1.61 and LogBlock is not rolling back items in chests. Is anyone else getting this issue?
-
View User Profile
-
Send Message
Posted Dec 26, 2012Possible problem with single perm? logblock.spawnTools: true logblock.tools.tool: true logblock.tools.toolblock: true logblock.rollback: false I got only the perm block.tools.toolblock in /lb permissions
-
View User Profile
-
Send Message
Posted Dec 25, 2012Would it be possible to not log block changes in newly generated chunks for a couple of secounds? I have a small and weak server, so as soon as anyone goes out to explore new parts, the consumer starts stacking up, only for logging unneacesary waterflows.
-
View User Profile
-
Send Message
Posted Dec 24, 2012@jamietech
Does not work.
The biggest issue is since param is not working correctly. I know i'm using it right, i've been using logblock since 1.8 beta.
-
View User Profile
-
Send Message
Posted Dec 24, 2012@SuperPyroManiac
Are you using the correct time? Use
.
-
View User Profile
-
Send Message
Posted Dec 23, 2012Im having a problem where it says "Error, check server.log". Is there anyway i can resolve this?