Inactive [INFO/ADMIN] LogBlock v1.54 - Enderdragon Logging! Tree Grow Logging! [1.4.5]

​

​

Version: 1.50​

​

Find and Backroll those Damn Griefers​

LogBlock release are on DevBukkit:
http://dev.bukkit.org/server-mods/logblock/

LogBlock dev builds:
http://ci.kitteh.org/job/LogBlock/

Please read the installation guide

I won't port LogBlock myself to mcAPI. Source code is available, so it shouldn't be to difficult for someone else to do it, also I'm still here. so I can answer questions. If there is more than one willing, that's up to you to handle that.




The reasons I take this step, are the usual: I quit playing Minecraft about 5 months ago and lastly I was struggling to keep up with updates. The developement of Guardian made slow progress, so I fear it won't be ready to fully replace LB in time.


Download latest dev build: Jenkins
View the source code: GitHub

​

Table of contents:

1. Description
2. Features
3. Why to use LogBlock
4. Example command
5. Older versions
6. Change log
7. Todo list / feature requests
8. Permission nodes
9. Plugins supporting this
10. Support the dev
11. How to post error messages
12. Advertizing

Description:

LogBlock logs block changes into a MySQL database. Block changes can be placed or destroyed block, explosions, burned blocks, sign text changes, chest access, leaves decay etc.
It can be used as griefer identification tool, to find out who build a particular building, or even roll back changes by certain players. Other purposes can be e.g: Undoing of forest fires
All additional features are optional, to keep the database as short as possible. All database actions run in their own threads to avoid server lags.
The use of permissions plugin (or any clone) is possible, but not necessary.
Uses Spout for chest logging (but it's fully optional, and there is no need for the client mod at all).

Features:

• Logging for block placing, block braking, fire, explosions, leaves decay, signtexts, lava flow and chest content
• Very mighty commands system, not only allowing to rollback and redo, but also to tp to blockchanges, delete log ingame etc. Full list of commands.
• Many parameters for lookup/rollback/redo/tp/clearlog commands: Block changes of one ore more player, in a specific area, in a world edit selection, specific block types only, block changes older or newer that a specific date, destroyed/created block only, in a different world and combinations of all these parameters. Full list of parameters.
• Rebuilding map after importing a backup (/lb redo)
• Last parameter to use the parameters of the last command
• Quick ingame lookup of block history a wood pickaxe or a bedrock block.
• All commands accessible from console (exept tools )
• Custom queries for tools.
• Different tool modes (lookup, rollback, redo, writelogfile and clearlog)
• Saves block data like wool color, log type, torch adjustment, etc
• Multiworld and multiserver support (some servers sharing the same database)
• BigBrother log import
• Loggable super pickaxe plugin (not to confuse with WorldEdit's super pickaxe)
• API
• Webstats

Why to use LogBlock:

Example commands: (thanks to tha d0ctor, read more about commands here)

/lb rollback player fire since 1d3h – rolls back fire 1 day 3 hours
/lb rollback player fire since 1d3h area 15 – rolls back fire 1 day 3 hours within a radius of 15 blocks

/lb rollback player thad0ctor since 1h - rolls back thad0ctor 1 hour
/lb rollback player thad0ctor since 1d area 5 – rolls back thad0ctor actions for the last day within 5 blocks
/lb rollback area 10 since 1h30m - rolls back all modifications within 10 blocks since the list 1 hours and 30 mins
/lb rollback area 10 before 06.11.2011 - roll back all changes in an area of 1o before June 11th, 2011
/lb rollback player thad0ctor since 05:36:00 - roll back all changes of thad0ctor since 05:36 (server time)


Download, Command, Configuration and Details:
http://diddiz.insane-architects.net/logblock.php

Changelog:
-> Full changelog

• LogBlock v1.50 # 81 (Dez. 13, 2011)
  Works with CraftBukkit 1.0.1-R1
  • Feature: /lb me shows the total block count
  • Feature: Chest logging without spout
  • Feature: Enderdragon logging
  • Feature: Logging for tree and mushroom grow (thanks to MD5 for the api)
  • Fix: Area param works again with default radius
  • Fix: Rollbacks got slowed down a bit to avoid rare server crashes
  • Fix: If mysql username, password or database only consist of unquoted numbers, LB will read them now
  • Config: World configs changed totally, some names changed and all logging options are now in an own section

• LogBlock v1.41 #63 (Nov. 15, 2011)
  Works with CraftBukkit recommended build #1337
  • Fix: Players with spawnTools permission are no longer allowed to spawn all tools.
  • Fix: Added a check to avoid "The permission xy is already defined!" errors

• LogBlock v1.40 #60 (Nov. 09, 2011)
  Works with CraftBukkit recommended build #1337
  • Feature: Custom auto ClearLog
  • Feature: Reduced error spam. Instead of like 40 line of error code, there is now just a warning stating the MySQL con
  • Feature: The queue will now be dumped after 10 tries even when the MySQL server is connected
  • Feature: Custom material names, allows naming custom blocks
  • Feature: LogBlock will now respond to messages when started without MySQL connection
  • Fix: Log import runs now async
  • Fix: Log import errors won't crash the server
  • Fix: Console commands work again
  • Fix: You can now use upper case letter in tool names (I don't know why you even should, but ...)
  • Config: Added clearlog.auto, clearlog.enableAutoClearlog in main config. Added materials.yml. Removed clearlog.keepLogDays
  • Permissions: Added 'logblock.spawnTools'

• LogBlock v1.32 (Oct. 04, 2011)
  Works with CraftBukkit recommended build #1240
  • Feature: Player info logging: firstLogin, lastLogin, onlinetime, ip. No ingame lookup yet.
  • Feature: /lb queuesize to see the current queue size
  • Fix: Door logging logs now also fence gates
  • Fix: Bukkit api break in CB #1191
  • Fix: time restriction works now as intended. Thanks to xrobau
  • Fix: Players with insufficient permissions can't smuggle bedrock from one world to another
  • Config: Added logPlayerInfo

• LogBlock v1.30 (Sep. 22, 2011)
  Works with CraftBukkit recommended build #1185
  • Feature: Chat lookup /lb chat player diddiz search +admin +sucks +dicks (more info)
  • Feature: Door logging
  • Feature: Dynamic tools, define your own tools
  • Feature: Use since and before to define a timespan
  • Feature: Enderman logging
  • Feature: cake logging (who ate it)
  • Config: Added logEndermen, logCakes and logDoors to world config and moved the tool section in main config.
  • Permissions: logblock.tool changed to logblock.tools.tool and
    logblock.toolblock to logblock.tools.toolblock.

Todo List:

https://github.com/LogBlock/LogBlock/issues

Permission Nodes:
https://github.com/LogBlock/LogBlock/wiki/Permissions

Plugins supporting Logblock:

List (open) List (close)

• DropPlugin
• Superpickaxe
• UndroppableDroppables
• PhysicalShop

When you want to appear your plugin here, tell me about

Support the developer (that's me ):
If you want to support me writing plugins or want to thank me for the plugin/support, you can: Suggest features I missed, report bugs (best with fix ), donate via PayPal, flattr my plugins, gift me The Witcher 2 (thanks to newyoukdaily), 2x 1GB DDR1 modules (thanks to HonestFlames), or send me the inner life of a laptop or netbook with a broken display (need it to build a model aircraft, so there is no need for parts like display and keyboard).

​

How to post error messages:


I won't aswer questions to general MySQL setup/installation/what is MySQL (there are lots of good tutorials out there, use google)
Please read the installation guide before asking a question about installation problems.
Please read the FAQ before posting a error report. It may be solved there.
In case of rollback or lookup problems: Type /lb savequeue and try again (when it's fixed then, it was a consumer problem, see FAQ)
When you post error messages, it's important to paste the whole stack trace!

Advertizing:

Newyorkdailys Plugin Support Buisness (open) Newyorkdailys Plugin Support Buisness (close)

Still can't get LogBlock working, or any other plugin? Are you getting errors in your console and cant figure out why? Newyorkdaily offers Basic/Advanced Plugin support.

• General/Advanced troubleshooting: FREE!
• Plugin Installations: 1-2 Plugins - FREE!
• 3 or More Plugins - $2

Click on the link below to connect to him now!
http://wbe001.mibbit.com/?settings=7cb4fd3cdd72754df475fb92a0b65f6c&server=irc.Mibbit.Net&channel=#CBPluginSupport

There is a LogBlock irc channel: #logblock at irc.esper.net.
You can ask me on skype. My name is 'hawky.diddiz'.

 

Therefore is LB the wrong plugin.

Just tested and it works

Afaik LB uses fewer ram and creates a smaller database, but sadly I've no exact data.
-> http://forums.bukkit.org/posts/257311

The exact command you used, the lb version and the error message could help to figure out what's wrong

 

@DiddiZ

Could you add bone meal to the logging? In 1.6.6 you can grow tons of grass and flowers via bone meal even in protected areas and it doesn't log. Basically a new way to grief, well it may not be all to harmful its certainly annoying especially when it happens on very large scales.

 

Bukkit doesn't provide the necessary hook for that atm.

 

Ah, then perhaps in the future

 

Sure

 

Ok so since last update i don't know how to do the old /lb rollback playerarea I used to need to undo someones grief in a 20x20 by lets say 4hrs ago. how do i do that with new commands?

Also is there a away to do it on a date? So we found someone griefed on 5/20/2011 I want to roll that back but its 6/7/2011... do i need to put in seconds still? or can i put 4 days? instead I want to do it in a player area tho to...

I tried /lb rb area since 32 d and it said it changed stuff but i want to only undo one persons greif?

 

@DiddiZ - are there way to optimize this to use more threads or work faster?

Here's some stats: We run 100+ players on Herocraft. Within 30 mins, I shut down the server while LogBlock was running. It said it had to push 15000 blocks through its current queue. I think tis may be degrading our performance quite harshly.
We are NOT monitoring "very" laggy things like leafs/lava etc - we're just doing block breaks and chests. Your thoughts?

 

Dates are implemented, but bugged, the next update will fix that.
/lb rb area since 32 d player <name>

Don't think the MySQL server would be very happy about multiple threads spamming inserts
But since chest logging seems to slow the consumer down, I'll try to imporve performance for next update.
But 15k blocks should use lesser than 1MB ram, so that shouldn't cause laggs.
Besides you can adjust the consumer settings. (decrease delay, increase blocksperrun)

 

Proposal.

Background:
I have players on the server, they can be called a "temporary griefers." The bottom line is that the player under the nickname (Player) broke the house player under the nick (Player2), player (Player) Sorry for the broken home before (Player2), and (Player2) wanted to rebuild the house. But, (Player) has already built his own house, and did not want to be rolled back. How then to proceed?

Method:
There is only one way to help both players. Try to make the team, rolled back at a certain time. For example (Player) broke a house in the time interval (12:00-13:00) and built a house in the interval (14:00-15:00). Need a player (Player) to roll back its activities in the interval (12:00-13:00), for example the command (/lb roollback Player t:12:00-13: 00), or something like this. Thank you.

 

Area or selection won't work?

 

I'll try your methods and see what we can get - It was just alarming to see that many blocks being pushed forward.

 

This is a great idea. I even did not think about it. It is advisable to select the area to work worked.

 

May I get an ETA on when the next update is supposed to be out?

 

Uh, hm, some days

But not the FAQ
-> https://github.com/DiddiZ/LogBlock/wiki/FAQ

 

Hey when you say chest logging, like do you mean it can show what players took out and put in?

 

i'm concerned with the plugin seeming to not have an automatic clear of old data from the database, is it true that all data is kept forever? I'd like to only keep logs for 7 days.

 

Year

set keepLogDays to 7

 

A small problem.
At 1 screenshot we see that all okay, I have empty inventory, plant stand.


At 2 screenshot we can see that I dug a pit, and cut down the plants with a shovel, and some do not cut down, I just dug and the plants themselves disappeared.


At 3 screenshot shows how I recovered with (/lb rb player pomo4ka), inventory remained in place. Recovered from those plants which personally I mowed.

 

Okay, and I'm having a queue overload problem, I placed a block, and its been 30 minutes and it hasn't been logged

 

It's the same problem as with torches. Bukkit doesn't tell when there a items adjected to a broken block that breaks too, when someone mines the block.

I know, noone likes to read FAQs, but:
https://github.com/DiddiZ/LogBlock/wiki/FAQ

 

Thank you. We will wait for updates.

 

Sorry heh, I thought it was problem on my end, Anyway, can I just set use scheduler to false?

 

Could you possibly make it so you can left click with the LogBlock too? That's one of the features I miss from BB.

 

That has only an effect when the sonsumer doesn't run at all.

Hm, would be very easy. You meant to use the block like the wood pickaxe?

 

Yes Thank you!

 

delayBetweenRuns: 6
forceToProcessAtLeast: 700
timePerRun: 100
That means it runs 700 entries every 6 seconds?

 

Yup

 

In a nutshell because I'm a bit short on time...

Bugs:

• Logblock creates mammoth amounts of rows in the lb-main table in my database at db4free.net.
• Logblock will not log or allow me to see history of the block (it says it is empty on a block I had just placed down)
• Logblock will spam the console with this error when I attempt to stop the server or do /reloadall;
  
  Code:

  2011-05-16 17:57:41 [INFO] [LogBlock] Waiting for consumer ...
   2011-05-16 17:57:41 [INFO] [LogBlock] Remaining queue size: 42

  and continue to spam until it had counted down to 0 and then continue the original process. Sometimes, it can be massive numbers, as in 10000+ and will lag players out and deny players to join back in until the process has concluded, which could take hours.
• No ability to change which block can be the logblock and the logtool.

Hope anyone can help and if you need me to, I'll provide more information.

 

I'm getting this error, When using toolblock it shows the history but rolling back gives 0 blocks found and then this following-

I used the command "/lb rollback player playername area 10"

Code:

22:17:57 [SEVERE] Exception in thread "Thread-13528"
22:17:57 [SEVERE] java.util.ConcurrentModificationException
22:17:57 [SEVERE]       at java.util.Vector$Itr.checkForComodification(Vector.java:1119)
22:17:57 [SEVERE]       at java.util.Vector$Itr.next(Vector.java:1096)
22:17:57 [SEVERE]       at de.diddiz.util.MySQLConnectionPool.reapConnections(MySQLConnectionPool.java:76)
22:17:57 [SEVERE]       at de.diddiz.util.MySQLConnectionPool.access$0(MySQLConnectionPool.java:74)
22:17:57 [SEVERE]       at de.diddiz.util.MySQLConnectionPool$ConnectionReaper.run(MySQLConnectionPool.java:89)

 

Year, since you are using a free hoster, you should only log the basic things as block place and break, Depending on the count of your players, it overcharge the MySQL server soon. Best thing would be to setup a local one.

That's both the same problem. Since the queue isn't in the database, you can't read it. That the queue take ages to process is a sideeffect of using a remote MySQL server.
-> https://github.com/DiddiZ/LogBlock/wiki/FAQ

set in config lookup.toolid and lookup.toolblockid to the wanted types.

You'll most likely to have to add a time. Default is 30 minutes, when the griefing was longer ago, use:
"/lb rollback player playername area 10 since 99 days"

Hm, that's new. Does it occur once or repeating?