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.
How can moderators look logs in game?
@MineCleric
It can't log what you put/take in/out of your chest. And it logs the water and lava placement.
Can this plugin log what you take in and out of your chest. Can also log who added water and lava?
@Esaych
Just put the server online, using a whitelist or just make sure there's no one online and say /blconvert from the console and It'll start converting your database to mysql. Just make sure your mysql settings in the config are correct.
Ahhh now I get this block thing. It's perfect, thanks!
And yeah, I know it isn't uploaded yet - already dl'ed 1.5 thanks to the subscription email.
@Y19
Well, not in v1.5 which is waiting to be approved but Its done on my computer and the sources are already on github. For the wand, both left and right clicking works, so you could click a solid block with the a block as the wand.
Alright, I'll check if I can find a way to do it.
@Anerach
Already? that's awesome :)
About the wand - I don't get it - how does it work both ways?
When I use a block, it checks the history of an air block, and when I use a blaze rod, it checks the history of the solid block (not air). Am I missing something?
Locations: yeah, no functionality other than displaying them while searching the logs.
Oh and about players who trigger creepers - it should be possible, since it was done in logblock, even though logblock doesn't handle it very well - it logs the player as the one who broke the blocks, so you would never know it was actually a creeper.
@Y19
When you use a block as the wand, you can still hit blocks with it, they wont disappear in creative so it works both ways.
But what would the use be for that location to be stored? Just to display it?
Alright.
Yea, you're right.
I really appreciate your feedback and suggestions.
Btw, I've already finished Chat, kill and death logs (Tested it). :p
The thing is, if you want to use both a placeable and a regular wand, you would have to change the config file every time you'd want to switch. I think 2 tools would make inspecting blocks much more convenient.
Locations of kills and deaths can be useful in various scenarios.. for instance when someone kills another player's animals, or when someone kills another player while they are AFK using lava or fire.
Search: Split the results into pages, so each page would print out a configurable amount of results (perhaps limit it to 15 or so), and you would be able to navigate through pages either by moving to the next page, previous page or a specific page (using its number/index) with commands like /blnext /blprev /blpage 15.
Location of creeper triggers: Useful when someone intentionally lures creepers into another player's home in order to destroy it.
I could try thinking of more scenarios where these features would be useful, but basically, I just believe the more information - the better, and in case some people don't want certain information logged, they should be able to disable it in the config of course :)
@Y19
A block tool? You mean, like a wand but placeable? That's already supported.
Why should the kill and death logging contain a location?
The log search command could give you like 10.000 results in the chat or what?
I don't know if its possible to check who triggered a creeper but I'll check it and again, why location?
Besides these things I don't quite understand yet you do have some awesome suggestions.
2 things I forgot to suggest:
- Automatically clean up logs, according to configurable filters
- Log names of players who triggered creeper explosions (including location)
@Y19
Great suggestions, thanks!
Hi, a few feature suggestions, since your planned features list is empty:
- chat logging
- player connect/disconnect logging
- kill logging (players, animals and monsters) and player death logging (falling/burning/drowning/void) - including locations
- log items placed in a chest or taken from it
- a block tool, similar to logblock's toolblock
- a log search option (like /blrollback, except you get results in chat instead of a rollback), plus a command that teleports you to the location of a result
- item drop & pickup, including item drop upon death
- change "Environment" to "Explosion" or, if possible, TNT/Creeper/Ghast/Enderdragon/Endercrystal
- better rollback (and search, in case you will add it) filters: time ranges (since X until Y), specific blocks, specific actions
Looking forward to use this as my primary logging plugin, just waiting for a few features :)
@Joelyyyy
Verified it.
It'll be fixed in the next update.
@Joelyyyy
I'm leaving for school soon but I'll take a look at it when I get back.
@Beardednerd
I'm almost certain it has something to do with your database not with the plugin. Check your config.yml, perhaps you didn't fill in everything correctly.
I'm not sure if this a mod issue or a database issue, so maybe someone with more experience with this can advise me. Every morning, when the first person logs in after the server having been empty all night, everything goes to hell and I get a spam of
in my server window. No one seems to notice in game, so it appears to just be a minecraft/mysql disconnect. I am using WAMPServer and my MySQL server logs show no errors or shutdowns. Once I restart WAMP and the MC server, it clears up. This has happened three nights in a row now.
Is this ticket worthy? Or does anyone have a suggestion on where I can start to find a fix for this issue?
@Anerach
No I am sorry we seem to have a misunderstanding. I mean BlockLog will not show block actions OR interactions. The reason I mentioned breaking the chest and having an action show up was to show that BlockLog was indeed installed and running correctly.
See the pictures below: In the first, a chest was just put down - as expected there are no interactions
and in this one, I had already placed the stone block I was previously holding into the chest, closed the chest screen and checked again using the wand:
Still nothing. In the image you can see that I was still using 1.3.1 at the time of trying this, even after updating to 1.4.1 the issue still persists.
Edit: After re-reading your reply a few times I find myself lost as to what exactly the plugin should display when you hit a chest. You say it only reports 'interactions' - does that mean interactions with the chest, a la opening it, or moving actual items to/from the chest, or does it just mean placing/destroying a chest block?
Either way, hitting a chest displays nothing at all.. Unless I'm doing it wrong..?
@abcedea
It looks a lot like LogBlock because it serves the same purpose as LogBlock. You should chose for yourself which one is better.
This looks a lot like LogBlock... What in this plugin is different than LogBlock that would make me want to change?
@Esaych
This is fixed in v1.4.1 which is waiting for approval.