BlockLog
BlockLog
Description
BlockLog is an Anti-Grief plugin with rollback support and a lot of other features for you to use.
This plugin is still in development and constantly gains new features!
Please report any bug found using the ticket system.
Our Jenkins is hosted by United World Miners - Minecraft Server!
Features
- MySQL support
- Specify how many blocks a rollback should change over a time span to prevent lag
- Rollback players or just explosion damage
- Rollback the whole world or just a small area
- Undo the last rollback or any rollback at any time
- Simulate a rollback to see how many blocks will be affected
- Cancel any active rollback
- Per world log options
- Logs blocks destroyed by mcMMO's skills
- Highly customizable, turn off any kind of logging
- Automatic database purge
- A fully functional grief report system build-in
- Search commands to search the database
- See a player his last edits in the whole world or just over a small area
- Both automatic and manual save options
Logs
- Player placed blocks
- Player destroyed blocks
- Blocks destroyed by fire
- Fire extinguish
- Use of buckets
- Explosions
- Interactions with chests, doors, etc.
- Leaves decaying
- Tree growing
- Portal creation
- Block form
- Block fade
- Block spread
- Chat
- Deaths
- Kills
Planned Features
- I'm open for suggestions!
How to install MySQL
See here
Metrics Graph
Support Me
I've put lots of time in developing this plugin. If you like it I would really appreciate it if you donated.
This seems like a useful plugin. The only problem i'm getting is: directly after placing it into the plugins folder and reloading the server the wand doesn't do anything, all i get is this nice little sponge that doesn't do anything. has anyone gotten past this?
@Jamesst20
I agree this plugin is not useless its awesome as you can keep track of everyone on your server. The great this is it does it all for you xD
Lol useless comment. You gave up after 5 mins xd
Given up. Plugin sucks. Doesn't do what it should. Update was ages ago. Summary: Bad Plugin
How do I find out who placed a block? TOO COMPLICATED. Please Explain how to do the thing I wanted the plugin to do in the first place
Log specified group only option.
Update please
Soo... is this plugin no longer being maintained? It's broken for 1.6.2 and last update was Feb 2013. Would be a shame, it's the best solution out there ..
Please correct "MySQL support" to "MySQL required" or something similar :(
How the fuck do i find out who broke a damn block, this is completely unexplained.
Jenkins is down ..
added to thew wiki
permissions: blocklog.admin: description: Gives access to all the blocklog commands children: blocklog.moderator: true blocklog.reload: true blocklog.config: true blocklog.purge: true blocklog.autosave: true blocklog.moderator: description: Gives access to most of the blocklog commands children: blocklog.user: true blocklog.wand: true blocklog.notices: true blocklog.save: true blocklog.rollback: true blocklog.storage: true blocklog.queue: true blocklog.search: true blocklog.help: description: Gives access to the help command blocklog.wand: description: Gives access to the wand command blocklog.notices: description: Everyone with this command will receive messages from blocklog blocklog.save: description: Gives access to the save commands blocklog.autosave: description: Gives access to the autosave command blocklog.rollback: description: Gives access to all the rollback releated commands blocklog.config: description: Gives access to the config command blocklog.reload: description: Gives access to the reload command blocklog.storage: description: Gives access to the storage command blocklog.queue: description: Gives access to the queue command blocklog.purge: description: Gives access to the purge command blocklog.search: description: Gives access to the search command
What are the permissions for the plugin?
ive been running the plugin for over a week now on 1.5.1 and i have yet to see these errors surfrock
I'm the spam king on this thread...
You need to disable chat and command logging per-world in order to sanitize the inputs for now. It has fixed the problem for us, and at best it's all still logged in the standard log anyway.
Sorry...one more...
The second crash (after having to fix the int(12) thing) was when a user said "/msg king hey let's pvp"
This leads us to believe, since the error spit out was: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's pvp', '1364766010', '23', '-4454', '76', 'world', '535')," The DB save isn't sanitizing the input and you can actually screw up your db with things like /msg. Best case you drop the queue...worst case someone pulls a "/msg ' DROP TABLES" or something.
Sorry for the comment spam...been diagnosing/dealing with this all morning. Our server was up and everyone was on IRC, but no one could join. It was because the ram went out of control...we suspect due to the queue building up since it couldn't write to the DB, until we maxed out.
My suggestions:
The way we're dealing with this will be a cronjob that will scan server.log every 5 minutes or so, and look for a timecode line within the 5 minutes before with this text: "You have an error in your SQL syntax;" and if it finds that, enforce a plugin reload. This should prevent the out-of-control-bl-queue from actually crashing the server. I can put the bash script here when I get around to writing it.
FYI...the only thing I can seem to find to purge the queue is plugin reload, or full server reboot. Kind of sucks...if we don't notice it for a while we're gonna have a rapidly out of control queue
So, I fixed that by moving all x, y, and z to INT(12) (btw I msised the ones in interactions, duh) but now I have a separate issue. My queue gets something corrupted in it, and it won't write to sql anymore...the problem is if we get a messed up entry in the queue (like when I'm messing with the stats plugin) it won't write, and then the queue just grows and grows and refuses to write. Is there a way to purge the queue? I know I can purge already written stuff from the db, but nothing seems to touch the queue.