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
R5
WILL THIS AWESOME PLUGIN BE UPDATED FOR R5 !!!
@Angry_Joe
i use permissions 3 it is not log it is other plugins that is stoping it from working
@Angry_Joe
What multiworld plugin are you using? I have Multiverse and it works for me.
Also multi world support is greatly needed. I used to use this plugin, and I loved it, but now I can't use it because:
It no longer works with Permissions 3
And it does not work with multiple worlds
:( All my plugins are compatible with these 2 problems, and I think this awesome plugin should be too! Plus, this is the only decent grief protector out there :P
I hope you are working diligently on this plugin. With the last stable version, 0.8.2, checking blocks with this plugin lags the server out and boots everyone. This is completely unacceptable, and has gone on for too long.
No longer works with old permissions :( Please fix this compatibility error! I need it!
When will RollBack Be added? and instead of saying
Block Changes: Block [ID] was destroyed/placed by [Player Name] at [Time]
I would like it to be instand of the ID I would like it to be the block name because I dont know all the block off the top of my head :3 I know Its ALOT of work to make a plugin but it would help me and many other people out.
-Zach
Please refrain my last message... But you really have to say somewhere that there is a 1.1 release out...
Hey when do you think a 1.1 plugin will come out?
How do you select air blocks? You said in your change-log that you can do this now?
Yeap if the databes grow big, and u use the stick it generate lag, because on a larger database hard to find the u need .
it is for small-medium server because lag big servers ?
Ok, this IS my favorite log plugin.
I tried No Grief Block Logger, it was missing the multiworld thing...
Then I tried AdvLog+, it it just upset me.
Just please do something to make it multiworld compatible.
Please update it, it's my favorite log, but it hasn't been working right. Half the blocks aren't logged.
Hey, I just discovered that it's not multiworld compatible. xD
You should really update it...
world_name_here:0;64;0;Gimlao;true;1;30/1/2012 12:00
I need that feature.
Would it be possible to add a command like /log <player> to see all the logs about a player ?
Or maybe, since it would be a very long thing to display in the chat...
It could create a logdata_<player>.db2 ?...
I hope i'm overlooking something, because from what I gather from your source code, your lookup algorithm performs an O(n) loop over the entire database for each lookup. Furthermore, it appears that you read the entire database from disk for each lookup.
For a 50MB database (Which has over 1078000 lines), this operation can take an excessive amount of time and resources. And no, you can't just use the lack of SQL as a scapegoat. There are plenty of data structures that are more suited to this task which could work in logarithmic time, as opposed to linear.
@Ankenmann2
Logs all blocks after installation just fine for me.
Not to be rude, but this plugin doesn't log half the blocks placed. Good other than that though (using 0.8.2)
@deleted_8201057
in 1.0 there is going to be a rollback