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.
Used to work great! Favorite logging plugin. But as of late I'm using the latest dev version on LogBlock on the newest Bukkit beta build and I'm getting this
And it won't connect to the database. I know I have the right info in the config! Any idea why it's doing this?
Happens...
@briankdk
wow - LOOOL - i got confused for a minutte....
logblock / blocklog :-)
By a mistake i installed blocklog a few days ago (thought i updated logblock) - no wonder the server has been TOTALY fucked up for the last 2 days ! Random lockups and stuff.
Blocklog has been deleted, and hopefully everything is back to normal.
sorry for the fuckup....
@deleted_7554077
thx,..... log block has so many pages...couldent find the correct one....
@briankdk Why are you posting this here? This is LogBlock website not Block Log.
Go here please: http://dev.bukkit.org/server-mods/block-log/
And the command is "/blfullsave" like the looks of it.
after last update i suddenly got this one in my gameconsule
BLOCKLOG Blocklog reached an internal storage of 700! you can fix this by using the command /blocklog fullsave
If i then do that...the error comes back i 1 minutte.... and that keeps happening.....
I can also see this one in the log:
[LogBlock Consumer] Queue overloaded. Size: 1419
what is going on ?
Does the latest logblock, log who created fire with firecharges/cannonballs? Current dev I'm on for 1.2.3 beta only show fire destroyed block, not who create the fire.
Can anyone help me? I would prefer a java coder opinion. I am getting this error for LogBlockQuestioner which should be compatible with CB 1.2.3 since its running good on my private home pc server but on the rental linux server with Java 6 where home pc has java 7 I get this error.
17:10:07 [SEVERE] Could not load 'plugins/LogBlockQuestioner.jar' in folder 'plugins'[0m
org.bukkit.plugin.InvalidPluginException java.lang.UnsupportedClassVersionError de/diddiz/LogBlockQuestioner/LogBlockQuestioner : Unsupported major.minor version 51.0[0m
at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:150)[0m
at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:287)[0m
at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:211)[0m
at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:207)[0m
at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:183)[0m
at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:56)[0m
at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:156)[0m
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:425)[0m
at net.minecraft.server.ThreadServerApplication.run(SourceFile:490)[0m
Caused by: java.lang.UnsupportedClassVersionError de/diddiz/LogBlockQuestioner/LogBlockQuestioner : Unsupported major.minor version 51.0[0m
at java.lang.ClassLoader.defineClass1(Native Method)[0m
at java.lang.ClassLoader.defineClass(ClassLoader.java:634)[0m
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)[0m
at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)[0m
at java.net.URLClassLoader.access$000(URLClassLoader.java:73)[0m
at java.net.URLClassLoader$1.run(URLClassLoader.java:212)[0m
at java.security.AccessController.doPrivileged(Native Method)[0m
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)[0m
at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:41)[0m
at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:29)[0m
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)[0m
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)[0m
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:334)[0m
at java.lang.Class.forName0(Native Method)[0m
at java.lang.Class.forName(Class.java:264)[0m
at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:139)[0m
... 8 more[0m
Any suggestions?
@Praaga If you might of noticed there is a link just above my comment to some dev builds. Those are the only official ones to work on CB 1.2.3, there are also some unofficial ones from other coders.
Anyone know when the update will be released? getting some errorsnshit + i suddenly loose things in the database....
LogBlock 1.52 (check your version please by opening the LogBlock.jar file with WinRar and open plugin.yml and look for the version number) works very well from builds 2034 to 2062.
Logging everything. I think you need the LogBlockQuestioner too since I solved a problem yesterday where LogBlock 1.52 wasn't working untill LogBlockQuestioner wasnt updated or you can try removing it totally so LogBlock won't depend on it.
Hope that fixes your problem. You might find a link to uodated LogBlockQuestioner somewhere in the comments.
Yeah, no matter what I do, the dev build is pretty much broken. Is it not logging or something?
weird, what about /logblock?
by the way, how to figure out who ignited certain block?
@darkknightcz
Yep, not working. I wonder why. Nothing comes up when I right click.
minechomp - get the wooden pickaxe and use right button on mouse
I'm using the latest dev build and the tools don't seem to be working at all. I have MySQL installed and working.
I have the latest dev build.
/yes and /no won't work
I'm not the only person I know who has these issues. anyone have a fix?
EDIT: I just deleted the Questioner because I couldn't find an updated version. It works now.
Guys, there's a dev build out for 1.2.3-R0.1 so you can probably expect a recommended build.. If you really need this plugin, go try out the dev build :)
Having no problems with logblock/questioner/stats here on 1.2.3
How would one undo a auto-rollback from banning a player?
ie undo player xyz (what goes next? need to undo all worlds rolled back and since all time?)
Thanks for this epic plugin!
Well I apologize to everyone that thinks I am being rude. Sorry for that but thats what you get when you don't first read the wiki and ask so stupied questions.
@Redstoner_Pro You didn't really give a lot of info also to make solving the problem easier (Don't feel bad, neither did the other guy). CB version, LogBlock version. Basicly no information.
But I am truly sorry that it ain't working for you.
Tip of The DAY! - Download a R5 - 7 compatible version of LogBlockQuestioner 0.0.2 Link is in the comments somewhere far far away like 10-20 pages back.