Works 100% with 1.5
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.
If you’re here for help, maybe you should try a different page. For plugin bugs, please report them, for other questions or urgent (private) bugs, click me to connect to IRC. Commenting below is NOT the optimal way to get help.
Facts
- Date created
- Aug 24, 2011
- Categories
- Last update
- Jan 20, 2013
- Development stage
- Release
- Language
- enUS
- License
- Attribution-NonCommercial-ShareAlike 3.0
- Curse link
- LogBlock
- Downloads
- 239,402
- Recent files
- R: LogBlock-1.70 for CB 1.4.7-R0.1 Jan 20, 2013
- R: LogBlock-1.61 for CB 1.4.6-R0.1 Dec 23, 2012
- R: LogBlock-v1.60 for 1.4.2 Sep 23, 2012
- R: LogBlock-v1.59 for CB 1.3.2-R0.1 Sep 21, 2012
- R: LogBlock v1.58 for CB 1.3.1-R1.0 Aug 11, 2012
- Reply
- #1471
sgtcaze May 25, 2013 at 16:13 UTC - 0 likes@ImTotallyTechy: Go
Works just fine for me without any console errors. Look at the error you posted, look for the line, "[Server] INFO com.mysql.jdbc.MysqlDataTruncation: Data truncation: Out of range value adjusted for column 'x' at row 1" This means the problem is within the tables on your mySQL server, which is definitely not an issue with logblock.
- Reply
- #1470
ImTotallyTechy May 25, 2013 at 13:09 UTC - 0 likesLike some others, logblock is running fine for me, although it SPAMS console with THOUSANDS of lines of code! Its SUPER annoying and lags like balls.
That was about 2 min worth, I need it fixed, please!
- Reply
- #1469
flawlessbraz1 May 23, 2013 at 22:28 UTC - 0 likesat sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.mysql.jdbc.Util.handleNewInstance(Util.java:407) at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116) at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:343) at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2334) at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2371) at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2163) at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:794) at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.mysql.jdbc.Util.handleNewInstance(Util.java:407) at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:378) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:305) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at de.diddiz.util.MySQLConnectionPool.getConnection(MySQLConnectionPool.java:72) at de.diddiz.LogBlock.LogBlock.getConnection(LogBlock.java:216) at de.diddiz.LogBlock.LogBlock.onLoad(LogBlock.java:63) at org.bukkit.craftbukkit.v1_5_R2.CraftServer.loadPlugins(CraftServer.java:244) at org.bukkit.craftbukkit.v1_5_R2.CraftServer.<init>(CraftServer.java:217) at net.minecraft.server.v1_5_R2.PlayerList.<init>(PlayerList.java:55) at net.minecraft.server.v1_5_R2.DedicatedPlayerList.<init>(SourceFile:11) at net.minecraft.server.v1_5_R2.DedicatedServer.init(DedicatedServer.java:105) at net.minecraft.server.v1_5_R2.MinecraftServer.run(MinecraftServer.java:381) at net.minecraft.server.v1_5_R2.ThreadServerApplication.run(SourceFile:573) Caused by: java.net.ConnectException: Connection timed out: connect at java.net.DualStackPlainSocketImpl.connect0(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.<init>(Unknown Source) at java.net.Socket.<init>(Unknown Source) at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:254) at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:292) ... 24 more
- Reply
- #1468
flawlessbraz1 May 23, 2013 at 21:00 UTC - 0 likesCan someone help me does it brake in 1.5.1 I can't get it to connect anymore
- Reply
- #1467
FlawlessSin May 23, 2013 at 20:43 UTC - 0 likesINFO java.sql.SQLException: Incorrect key file for table './mcprohosting4930/lb@002dchat.MYI'; try to repair it
Looked it up and it says it's due to memory getting full.
When i went to clear the log, it said: Exception, see error log
- Reply
- #1466
flawlessbraz1 May 23, 2013 at 20:00 UTC - 0 likes3:58:19 PM LogBlock: Loading LogBlock v1.70 3:58:19 PM LogBlock: Connecting to ** 3:58:39 PM CONSOLE: [SEVERE] [LogBlock] Error while fetching connection: 3:58:39 PM CONSOLE: link failure
- Reply
- #1465
Shadix64 May 20, 2013 at 22:32 UTC - 0 likes@kdthehun: Go
Install FrameProtect to keep frames safe from griefers.
- Reply
- #1464
Waterflow May 18, 2013 at 14:29 UTC - 0 likes@kdthehun: Go
agree
- Reply
- #1463
fungreenfox May 18, 2013 at 14:16 UTC - 0 likesI have the issue of Logblock making duplicate entries in the sql table of main town. Once a day it happens. This gives an output in the console of 50 lines. When i goto phpmyadmin and check the table(s), it says nothing wrong, all tables are ok. So what is it?
- Reply
- #1462
kdthehun May 16, 2013 at 08:53 UTC - 0 likesI have the issue of LogBlock not logging ItemFrames. Too often theft happens and the thief goes unpunished as we have no records of ItemFrame placement/removal.