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 Sep 23, 2012@DrFusion
/lb rb player DrFusion since 1d area 100 ?
-
View User Profile
-
Send Message
Posted Sep 23, 2012what are the params of /lb rollback? i did /lb params but where do i put the username?
-
View User Profile
-
Send Message
Posted Sep 23, 2012@zenyl
You need to edit the config.yml and add in the correct username / password for your mysql database (as it says in the error...)
-
View User Profile
-
Send Message
Posted Sep 23, 2012soneone said already its planned to add... but when ...
Iam runnng Logblock and CoreProtect (Only for worldedit loggin)... would like to only use LogBlock. Its the best :D
-
View User Profile
-
Send Message
Posted Sep 23, 2012Yes. I'm also waiting for worldedit loggin'. Because now we have two plugins 1 for chest acces logging and 1 fow worldedit logging... Please can you combine these two?
-
View User Profile
-
Send Message
Posted Sep 23, 2012Waiting for Worldedit logging :D
-
View User Profile
-
Send Message
Posted Sep 23, 2012- Your installation guide is missing When I click the hyperlink called "Installation", I come to GitHub, with the following sub-pages, or whatever:
API BigBrother Log Import Commands Configuration FAQ Helpful Commands MySQL Configuration MySQL Connection Problems MySQL Schema Params Permissions
Note, that none of them are called "Installation"
- IRC is down =/ - When I start up the server, I get this error:
16:05:19 [INFO] [LogBlock] Loading LogBlock v1.59 16:05:19 [INFO] [LogBlock] [LogBlock] Connecting to username@jdbc:mysql://localh ost:3306/minecraft... 16:05:19 [SEVERE] [LogBlock] [LogBlock] Error while fetching connection: java.sql.SQLException: Access denied for user 'username'@'localhost' (using pass word: YES) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3593) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3525) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:931) at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:4031) at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1296) at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2338) at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2 371) 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 Sou rce) 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:73) at de.diddiz.LogBlock.LogBlock.getConnection(LogBlock.java:243) at de.diddiz.LogBlock.LogBlock.onLoad(LogBlock.java:89) at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:227) at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:198) at net.minecraft.server.ServerConfigurationManagerAbstract.<init>(Server ConfigurationManagerAbstract.java:50) at net.minecraft.server.ServerConfigurationManager.<init>(SourceFile:11)
at net.minecraft.server.DedicatedServer.init(DedicatedServer.java:105) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:378) at net.minecraft.server.ThreadServerApplication.run(SourceFile:539)
-
View User Profile
-
Send Message
Posted Sep 23, 2012No permission for the SQL-Queries wiki page? Any chance we can get access to this - will help a lot as i'm writing some logblock stuff for my website admin panel.
Cheers
-
View User Profile
-
Send Message
Posted Sep 23, 2012Update LogBlock Questioner?
-
View User Profile
-
Send Message
Posted Sep 22, 2012Its not logging my chest! And I can't find Logblock Questioner! Help!
-
View User Profile
-
Send Message
Posted Sep 22, 2012@deleted_7554077
Yeah sorry about that, it was an undersight by the original author and nothing I can do, its just MySQL churning away. If you don;t want your tables updated, then just bump version in config.yml
-
View User Profile
-
Send Message
Posted Sep 22, 2012Some huge bug fixes in coming updates, try the dev builds at: http://ci.kitteh.org/job/LogBlock/ Report bugs to github.
New stable release tomorrow hopefully.
-
View User Profile
-
Send Message
Posted Sep 21, 2012@flyingtacoz
Ensure proper limits are configured.
-
View User Profile
-
Send Message
Posted Sep 20, 2012@flyingtacoz
/lb redo time <time>
-
View User Profile
-
Send Message
Posted Sep 20, 2012Don't mind my previous post, it just required a permission plugin. I installed one and the problem was gone.
-
View User Profile
-
Send Message
Posted Sep 19, 2012Good.
-
View User Profile
-
Send Message
Posted Sep 19, 2012Sometimes when I restart the server it gives me this error, it repeats it 6 times in a row:
2012-09-13 18:06:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
-
View User Profile
-
Send Message
Posted Sep 19, 2012@flyingtacoz
Install LogBlockQuestioner?
-
View User Profile
-
Send Message
Posted Sep 19, 2012@flyingtacoz
Start making daily backups of your world. Did you try to undo your rollback?
-
View User Profile
-
Send Message
Posted Sep 18, 2012@JonRetribution
I do have MySQL setup and is connected to MySQL, but how do I give the MySQL access to the LogBlock folder?