Log
Well, thank you everyone who has supported the development of Log, but I have to sadly announce that I have stopped working on it.
UPDATE 20/12/2013: I have begun work on an official successor to Log, available now on BukkitDev under the title exLog.
Log is a plugin that logs block changes. It's aim is to be a feature-filled but lightweight alternative to BigBrother.
Log is designed for small-medium sized servers where the main focus is identifying and banning the griefer, rather than fixing the griefed structure (backups should be used for that).
Compatible with 617 onwards. Latest build officially tested on 1597.
Download From "Files" above
How to Use <- Read this or you don't get support!!!
Features:
- Logs block place and destroy events
- Lets you look up block place and destroy events using a stick
- Permissions support
- Block type/material logging
- A block to check air and other non-clickable blocks
- Plaintext buffered SQL alternative to prevent memory leaks
- POSSIBLE: Auto-delete support - prevent buildup of old stuff
- PLANNED: Rollback
@RunasSudo
Boner.
@RunasSudo
Awww yeah. Can't wait!
@OZ4RK
After 0.9 enters 'Release' phase, so hopefully next week or the week after. No guarantees though.
@RunasSudo Any ETA on 1.0? Thanks!
@zaklampje
Rollback is coming out in 1.0. You can check future feature plans here.
Omg thankyou!!!! finally!. something that tells me who destroyed that block with out having to get MySQL or anything liek that.. Simple and easy.. Thumbs up to this :D
When are u gonna add rollback? Need that, since big brother is no more :(
@superdupernova
This is strange...
Please file a ticket and we'll (by which I mean I will) look into it.
EDIT: According to the Permissions page, it doesn't seem there is support for player.hasPermission
File a ticket for an enhancement and I may implement support in 0.9
@groveham
.... Silly me, I forgot to add instructions for the config file (facepalm)
In the file
plugins/Log/config.properties
you can edit stickItem and boneItem
I'll be sure to add that to the instructions right away!
(If you were talking about the actual feature, rather than changing the tool, PLEASE PLEASE PLEASE read the instructions next time)
@groveham
Use the bone.
Hit the "face" of the adjacent block to check the "air" that is on that "face" you hit with the bone.
I logged in just to tell you how much I support your work. Your plugin in my eyes is the leading edge in capturing griefers over time.
I look forward to rollback, perhaps something that can hook into worldedit selections, then typing"/lrollback <#> <unit of time> Unit of time can work much like the /clean feature, using Day, hour, or minute.
please add roleback soon :D
Is it possible to bind this plugin to another tool, such as a cobweb or a piece of bedrock, this would allow you to place it and see who changed that block that the cobweb or bedrock is occupying, and right click to see who placed/changed the block?
Using a stick can get a bit annoying as you need to place a block to see who has destroyed one that was in its place.
It uses player.haspermission, but it still doesn't seem to work.
@Jeroeny If the water was placed as a block (i.e, using hacked in water blocks, not buckets) you can right click the water with a bone. Support for buckets will come soon.
@superdupernova This used to be compatible with that (it may still be, if it uses player.hasPermission), but since official BukkitPermissions and such came out, official support has been removed.
Is this not compatible with permissions by yeti? That's the only reason I could think of for it not working.
Hi
It says ''A block to check air and other non-clickable blocks'', I 've red the instructions but I'm not sure, can I see if someone placed lava or water and how?
Thanks
@jodizz57 No, Log does not require any extra software. Next time, though, please read the instructions.
@Mr_Fuman Log already has such functionality. "Place" a bone to check a non-clickable block. Next time, though, please read the instructions.
I gave my mods 'log.*' but they can't check blocks with sticks or bones. They can do /log and see the menu, but can't actually do anything.
Does this require anything other than just downloading the plugin and putting it in the plugin folder. I dont want to start a MySQL Server.