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.
Was wondering how I would allow moderators to be asked to rollback a banned user?
@Hoeze
In the config there is a option for doing this :-)
How do I find out who has caused a creeper to blow up?
where do i download 1.5 ?
I cant use the chestaccess, its just saying it wouldn't accist. Thats very annoying, because its one of the best feuters for me.
Is the latest logblock compatible with craftbukkit 1.1?
@quickclay
This may solve your problem, it may not. Depending on who you _want_ to have access to /lb tool. Subtract these permissions from the groups you don't want to be able to spawn lb tools:
Hope this helps!
- Llama
Is there a way to keep someone from being able to spawn an infinite number of "tools", by dropping their tool each time?
It would be nice if you were required to /lb tool off with the tool in inventory to be taken away, before you can spawn a new one. That would solve the issue. Thanks!
@Crayder
Should answer all of your questions!
https://github.com/DiddiZ/LogBlock/wiki
I'm an idiot. Yes, LB works fine with latest dev builds.
@Iv_Ollieee
seems good
Does the current log block version work with the 1.1 dev builds?
Mapping values not allowed.D: How to fix that?
How heavy is LogBlock on a server?
Also, how can I set it so that only admins can view block changes with right click?
@Crayder
Anyone?
I read the FAQ but It only stated why it doesnt rollback all changes. Well I have a world that I want restored daily, including blocks people have placed. Is there a work around for this? I want 478/478 restored all the time, everytime.
SuperPerms or bPermissions support please!
Do chests automatically log if Spout is detected as installed?
FYI. If you are looking for a link to the latest 1.0.1 version (v1.50), see the old Bukkit Forum's LogBlock page. Also note that even though that link show it to be tested under CB#1337, the Change Log states that its compatible with 1.0.1-R1.