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

    DiddiZ

    Not until WE uses the LogBlock api, which will come with next update.
     
  3. Offline

    rmb938

    Alright thanks
     
  4. Offline

    Ahfaichucky

    the default config will removed old logs from the mysql db? i had it set at -1..
     
  5. Offline

    DiddiZ

    Not the default, but any value larger than 27, so -1 is ok. Bisides, -1 means disabled, what's anyway the best protection :D.
     
  6. Offline

    Ahfaichucky

    so if i set it to remove every 3 weeks i just put it as 21?
     
  7. Offline

    DiddiZ

    yup
     
  8. Offline

    tha d0ctor

    if I could request something there is one feature I would love to see.

    Variable Logging:

    You are able to configure a more complex logging system where each individual table/category/flag has its own time variable stating how long entires are stored in the database. This whay you could set block placement time to 9999 or something, fire to 5 days and less important stuff to only a day or two for example.

    This would open up the possibility to create mods in the future based off your logblock databases like:

    Block protection for every block a user has place
    Stats / Achievements
    Automatic griefer protection if someone tried to destroy X blocks from X differet players with X minutes etc...
     
  9. Offline

    DiddiZ

    Hm, good idea. Will that.

    Besides that the advanced ClearLog isn't neccesary for that, I also thought about such plugins, in particular for griefer detection.
     
  10. Offline

    tha d0ctor

    Great to hear, can't wait. Thank you!
     
  11. Offline

    TheRec

    I have the same issue with the toolblock staying in place. I thought it might be caused by EssentialsProtect ? Do you use this pluing ? Anyways I tried to remove all restriction for this block id (7) in Essentials and the problem is still present.
     
  12. Offline

    DiddiZ

    Hm, tested and found it working with EssentialsProtect. Maybe another plugin. The history showed properly? Does other block types work?
     
  13. Offline

    Kresnik002

    Im getting one problem here, one griefer attacked the server with fire and a lot of signs and doors destroyed by fire (doe to lack of support), the lb rollback fire dont fix it. Looking at they old spot there is no block destroyed event.
     
  14. Offline

    DiddiZ

    Well, objects adjected to destroyed blocks aren't logged. Will add that when I find a simple way to to this, without checking each block for torches, signs, paintings, etc.
     
  15. Offline

    TheRec

    It does display the history correctly. And with other toolblock-id (I used 87, for netherrack) the behavior is the same.
    Also, when you break the block that was placed, it doesn't drop (there is nothing to pick up, as if it never existed).


    My other plugins are :
     
  16. Offline

    DiddiZ

    Hm, another idea: Is it maybe a cleint bug or can other players see the blocks too?
     
  17. Offline

    Luckz

    How close is the 1.5_02 update? :p (Don't wanna be whiny, just wondered if you saw that there's a bukkit update)
     
  18. Offline

    DiddiZ

    I saw it and am waiting for a rb. Should be take long then.

    EDIT: But by now it looks like v0.13 would work.
     
  19. Addon appears to work, but doesnt take lightning damage into account. Had a giant 100 metre pirate flag up in the sky that burned for no apparant reason..
     
  20. Offline

    DiddiZ

    Well, hadn't yet test such things. Need a rb and a plugin to spawn lightnings. But when it burns, or explodes, it should be logged.
     
  21. Offline

    TheRec

    Other users see the block. And it does exist, I can pass through it. I use no texture pack and original client (no mod or hack).
     
  22. Offline

    DiddiZ

    Very strange. Could also be a bukkit lag. Maybe it's fixed with 1.5 :D.
     
  23. LogBlock giving me trouble on CB709. Refuses to restore portions even though its clearly logged when created.
     
  24. Offline

    DiddiZ

    LogBlock isn't yet stable for MC 1.5. There were some bukkit changes.
     
  25. Fully awakre, just giving feedback.
     
  26. Offline

    DiddiZ

    Ah, ok, thanks then :D
     
  27. Offline

    _Zw_

    so when updating to 0.13 i lost all logg? great

    edit, or just some il see :p
     
  28. Offline

    DiddiZ

    No, only when you set keepLogDays to a value higer than 24.
    Odd bug, I know.
     
  29. Offline

    TheRec

    Hmm I don't see how "lag" could cause that... anyways, I guess we'll have to wait until CB and your plugins gets updated to know if this bug is still in.
     
  30. Offline

    Milhouz

    any body have an english tutorial to set this up i used group manager and also permissions but it just kept not letting me use the commands even though they are listed in the nodes.
     
  31. Offline

    DiddiZ

    The tutorial is called Installation guide and mentioned in the main post.
    What does LB says at startuo about permissions? There should be a message either enables permissions, or using defaulzt permissions.
     

Share This Page