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.
Hey, I'm just wondering how much space of MYSQL this uses, I have found free ones for 10MB, and others different, I don't want my database to be inaccessible when It gets full, please reply ASAP
siemaeniu500 report errors in tickets section! For you siemaeniu500 your error link: Error: http://dev.bukkit.org/paste/7057/
Make it Log Worldedit,
i could really use that
@Bubelbub
The Link is now and forever United World Miners Jenkins BlockLog
What version of MySQL did you guys use and found the best results? I am trying to get this plugin to work and it looks great!
My idea is to add command logs. So you know who did what command.
@Bubelbub
The version I uploaded had some bugs in it so I removed it.
@daviDOS4
What do you want me to do with the mailing system?
Can you please support a Mail System? For example the Mailing System from Essentials
@Anerach
You could write the Link here:
http://ci.unitforcesoft.com/job/BlockLog/lastStableBuild/me.arno.blocklog$BlockLog/
Then nobody must wait for moderator.
@bugsy592
I've uploaded an update. It's waiting for approval by a mod.
It appears there were still some unfixed bugs in that version. I'll re-upload it when I've fixed the bugs.
Does this work with 1.4.5, and also when will it be updated?
ps that MySQL info helped me a lot thanks
ive now run the latest snapshot of blocklog for a couple days now 1 day on testbed clean build and one day on my regular server, the only problem is if you update from a previous version you need to clear your database of old blocklog entries, or i had to anyway due to some conflicts, since that point the plugin has been running stable on my 1.3.2 server
i will start testing against the latest bukkit build for 1.4.5 sometime today or this weekend
How do I see who griefed?
to go back to the tekkit questions, ive run block log for 1.2.5 for about a week on my tekkit server, and occasionally im still having issues arise, im sure its on the tekkit side of thing though as its not well put together to begin with, what one of my admins did find is an old version of core protect that works decent with tekkit
as far as the last snapshot of blocklog, i havent been able to test it due irl work and family gatherings and cousin getting married, but i plan on testing it thoroughly now that i have a little time for the next couple days
for the time being i have been running the last release build of blocklog on my regular bukkit server with no issues for 3 weeks or better, i will create 2 testbed servers one on 1.3 and the other on 1.4 and report back tomorrow with the latest snapshot
@redmin7
Yes and the update is finished. I just need to be sure there are no bugs in it.
i have 2 questions. do u need mySQL and when r u updating?
@Jamesst20
I'll wait for a beta/recommended build.
Please update with newest Bukkit API, there have been change that must be recompiled. Thanks !
Read HERE for more info
I have some good news everyone. I've fixed every bug I could find in blocklog. However, I don't want to release the new version yet. I'm looking for some people that are interested in running this version on their server for a few days to make sure it doesn't have any bugs. PM me if you're interested.
maybe but, it did not register copper ore break or any other block added by tekkit, ive tried to run it and that was the result i got
edit: ok i tried it again on my tekkit server and it is working, all blocks are being recorded for break events, it doesnt give the name like it does for normal blocks but it is working, which is good cuz i didnt want to use swatchdog on my tekkit server since they dont have sql support
edit: i updated to tekkit 3.1.3, if you run tekkit dont, along with all the issues with tekkit itself, it also causes blocklog to spam the console with errors when blocklog does its autosave