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

Discussion in 'Inactive/Unsupported Plugins' started by DiddiZ, Feb 15, 2011.

  1. Offline

    DiddiZ

    Version: 1.50​
    [​IMG]
    [​IMG]
    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 :D)
    • 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:
    [​IMG]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)

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



    Support the developer (that's me :D):
    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 :D), 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).

    [​IMG]


    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)
    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'.
     
  2. Offline

    Sayshal

    some of these commands could be simplified.. like area? is that a radius? im so confused by the command layout.
     
  3. Offline

    TerrorBite

    I recently got the following when using the "reload" command, this usually happens after the server's been running for a while:

    Code:
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: '<NoAuthorGiven>' of 'CommandBook' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: '<NoAuthorGiven>' of 'CommandBook' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: '<NoAuthorGiven>' of 'CommandBook' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    10:40:43 [SEVERE] Nag author: '<NoAuthorGiven>' of 'CommandBook' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin
    This is a little worrying... I've also been getting OutOfMemoryErrors that I can't pin down to any particular plugin and seeing this makes me wonder if it's LogBlock.

    Edit: It was version 1.22 of LogBlock, I'm now running 1.24 in hopes of a fix.
     
  4. Offline

    DiddiZ

    Yup, is it.
    Did you saw this?
    https://github.com/DiddiZ/LogBlock/wiki/Params
    Um, wouldn't think so. These async tasks are some lookups, rollbacks etc that never finished, but they won't use much ram. 2 mb each a _maximum_, a few kb more likely.
     
  5. Offline

    Sayshal

    I really want to give this a chance, but at the moment, Big Brother is still simpler.
     
  6. Offline

    WarOfLiberty

    I've run into a problem with my queue not saving correctly.

    The problem seems to appear when I have bukkitcontrib or mChat running. When I don't have them running though I still have a slight problem of the queue building up, but it clears eventually. When bukkitcontrib or mchat is running the problem never clears. I've attempted to manipulate the consumer settings on sever occasions but i've had no luck so far. Here is my consumer settings:
    We average about 10-20 people on our server, we seem to hit the problems a lot when we get to 20 people. Any ideas?
    Also, sometimes I have all 4 CPU cores running at 100%.
     
  7. Offline

    Incendia

    Small problem, turning off the toolblock doesn't remove the item itself. my players just got a shitload of bedrock ._.
     
  8. Offline

    DaLeberkasPepi

  9. Offline

    Infectedd

    On check with bedrock:

    10:53:20 [SEVERE] [LogBlock Lookup] Exception:
    com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'itemt
    ype' in 'field list'
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou
    rce)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at com.mysql.jdbc.Util.handleNewInstance(Util.java:407)
    at com.mysql.jdbc.Util.getInstance(Util.java:382)
    at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)
    at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3593)
    at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3525)
    at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1986)
    at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2140)
    at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2620)
    at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2570)
    at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1474)
    at de.diddiz.LogBlock.CommandsHandler$CommandLookup.run(CommandsHandler.
    java:445)
    at org.bukkit.craftbukkit.scheduler.CraftWorker.run(CraftWorker.java:34)

    at java.lang.Thread.run(Unknown Source)
     
  10. Offline

    RustyDagger

    permissions page on github needs updating at the top to reflect that bukkit perms can be used.
     
  11. Offline

    DiddiZ

    Your loss :D
    That's the reason. You have either to lower your cpu usage, or to increase forceToProcess further.

    Hm, can add a workaround.
    Sure
    Which LB version?
    Right, ty, updated.
     
  12. Offline

    Infectedd

  13. Offline

    DiddiZ

    kk, then how does your -chest table look like? Are there uppercase letter in the column names?
     
  14. Offline

    Narmotur

    Question for you, chat logging, love it, doesn't seem to work with HeroChat, any way I can make it log more than just /commands when using HeroChat? Also, and I know the answer is probably no, but is there any way to add logging of the world and x, y, z of the chat or at least /commands? It was helpful a few times in the past investigating user shenanigans with BB. Thanks for all your work so far!
     
  15. Offline

    Infectedd

    loggedWorlds:
    - world
    - NewWorld
    - freebuild
    mysql:
    port: 3306
    host: localhost
    password: ********
    user: ******
    database: minecraft
    logging:
    logCreeperExplosionsAsPlayerWhoTriggeredThese: false
    logKillsLevel: PLAYERS
    hiddenPlayers: []
    hiddenBlocks:
    - 0
    clearlog:
    dumpDeletedLog: false
    keepLogDays: -1
    questioner:
    askRedos: true
    askClearLogs: true
    askRollbacks: true
    askClearLogAfterRollback: true
    rollback:
    replaceAnyway:
    - 8
    - 9
    - 10
    - 11
    - 51
    dontRollback:
    - 10
    - 11
    - 46
    - 51
    maxTime: 2 days
    maxArea: 50
    consumer:
    delayBetweenRuns: 5
    forceToProcessAtLeast: 20
    timePerRun: 200
    useBukkitScheduler: true
    lookup:
    toolID: 280
    toolQuery: area 0 all sum none limit 15 desc silent
    toolblockID: 7
    toolBlockQuery: area 0 all sum none limit 15 desc silent
    defaultDist: 20
    defaultTime: 30 minutes
    linesPerPage: 15
    linesLimit: 1500
    version: '1.24'
     
  16. Offline

    DiddiZ

    Chatlogging as far from beeing done :D
    The first will totally come, I'll add some regex to parse commands to chat.
    I'm not sure about coords, as this would require entries in the world main tables ... making the database larger and lookups slower.
    @Infectedd
    Didn't meant you config, but your mysql table
     
  17. Offline

    Infectedd

    @DiddiZ oh. I'm dumb, whatever. The per-world configs contain no caps in the tablenames, and how can i see the contents of the mysql table?
     
  18. Offline

    Raycrash

    I would like a little tutorial or something.
    Especially for the config.

    I'm not sure right now how long the tracking of player goes.
     
  19. Offline

    Infectedd

    @DiddiZ : i found how to open a table, but looks like it doesn't support "-"s
    mysql> SELECT * FROM lb-newworld;
    ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that
    corresponds to your MySQL server version for the right syntax to use near '-neww
    orld' at line 1
     
  20. Offline

    DiddiZ

    Year, also have to update the wiki, per world config is still not mentioned there.
    Log is kept forevery, until you enable autocleaning by setting keepLogDays to a positive value.
    SELECT * FROM `lb-newworld`;
     
  21. Offline

    Infectedd

    Here's the contents of lb-newworld-chest:
    +-----+--------+----------+---------+-----------+
    | id | intype | inamount | outtype | outamount |
    +-----+--------+----------+---------+-----------+
    | 41 | 0 | 0 | 0 | 0 |
    | 181 | 0 | 0 | 0 | 0 |
    | 569 | 0 | 0 | 0 | 0 |
    | 640 | 0 | 0 | 0 | 0 |
    +-----+--------+----------+---------+-----------+
    lb-main-chest outputs a huuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuge list of
    #### 0 0 0 0 where #### is a normal number
    lb-freebuild-chest does the same
    lb-world-chest : Empty set (0.04 sec)
    and the lb-prefixed tables are:

    lb-freebuild
    lb-freebuild-chest
    lb-freebuild-sign
    lb-main
    lb-main-chest
    lb-main-sign
    lb-newworld
    lb-newworld-chest
    lb-newworld-sign
    lb-players
    lb-world
    lb-world-chest
    lb-world-sign
     
  22. Offline

    Kainzo

  23. Offline

    DiddiZ

    This is an old format, it should have beed deleted.
    So you have to delete the chest table manually
    Make sure your MySQL user has access to the LogBlock folder, or disable clearlog.dumpDeletedLog.
    It won't work for remote servers.
     
  24. Offline

    oliverw92

    Quoted from that error:
    You sure 'dumb' isn't meant to be dump?
     
  25. Offline

    DiddiZ

    It is. Damn typo.
     
  26. Offline

    Infectedd

    @DiddiZ: yea, worked, thanks!!
     
  27. Offline

    Wahrheit

    @DiddiZ LogBlock is still causing about 1-2 minutes of downtime each plugin reload and/or server restart due to it trying to load some queue...
     
  28. Offline

    oliverw92

    I hate it when you go over masses amount of code trying to debug, and all along the problem was a tiny typo lol
     
  29. Offline

    Incendia

    There a way I can set logblock to stop recording changes, and simply act as a history?
     
  30. Offline

    DiddiZ

    Hm, you could experimentally set forceToProcess to 1000 and delay to 10.
    Yeah, disable all loggings, even block brak and place logging.
     
  31. Offline

    rtcabooservb

    :confused: Any eta on spout support rather than bukkitcontrib?
     

Share This Page