Inactive [ADMN/SEC] SuperLog v2.4 - A very simple and effective logging plugin [1597]

Discussion in 'Inactive/Unsupported Plugins' started by thescreem, Aug 4, 2011.

  1. Offline

    thescreem

    Now on BukkitDev!
    [​IMG]

    [​IMG]

    <font color="rgb(51, 102, 255)">SuperLog - Make logging better and easier.</font>

    Current Version: 2.4
    Craftbukkit version: RB 1597 [Minecraft version 1.0]

    SuperLog is a very easy to set up logging plugin that can effectively catch greifers without the hassle of setting up any database.

    Features:
    * Easy to set up, no need to go through the hassle of setting up MySQL or any other database.
    * You may choose what you would like to log in a config file.
    * Ability to log block breaking, block placement, chest openings, and commands used by who, at what time, and at what coordinates.
    * If chosen in the config file, you can receive a message when Flint and Steel is used, TNT is placed, or TNT is ignited.
    * SuperPerms support!

    Future Features:
    * Lookup players.
    * Edit the config file in-game.
    * Setting for configurable date format.
    * Rollback.
    * Suggest!

    [​IMG]
    How to set up SuperLog:

    Show Spoiler
    In the config file, you will see something like this:
    Code:
    log-block-placement: true
    log-block-breaking: true
    log-chest-openings: true
    log-bucket-emptying-and-filling: true
    log-commands: true
    send-message-when-TNT-is-placed: false
    send-message-when-TNT-is-ignited: false
    send-message-when-Flint_and_Steel-is-used: false
    create-individual-player-logs: false
    memory-in-MB-until-new-block-logs-file-is-created: 50
    memory-in-MB-until-new-chest-logs-file-is-created: 50
    memory-in-MB-until-new-command-logs-file-is-created: 50
    memory-in-MB-until-new-[player]-logs-file-is-created: 50
    
    Most of it is self-explanatory, but I will go through it anyways.

    Code:
    log-block-placement: true
    
    True by default. If set to true, then this will log when a user places down a block.

    Code:
    log-block-breaking: true
    
    True by default. If set to true, then this will log when a user breaks a block.

    Code:
    log-chest-openings: true
    
    True by default. If set to true, then this will log when a user opens a chest.

    Code:
    log-commands: true
    
    True by default. If set to true, then this will log whenever someone types a command.

    Code:
    log-bucket-emptying-and-filling: true
    
    True by default. If set to true, then this will log when a user spills or fills a bucket of lava or water.

    Code:
    send-message-when-TNT-is-placed: false
    
    False by default. If set to true then whoever has the permission node stated under this spoiler will receive a message when a player placed down TNT.

    Code:
    send-message-when-TNT-is-ignited: false
    
    False by default. If set to true then whoever has the permission node stated under this spoiler will receive a message when a player sets off TNT with Flint and Steel. Currently, it doesn't work when TNT is set off with redstone.

    Code:
    send-message-when-Flint_and_Steel-is-used: false
    
    False by default. If set to true then whoever has the permission node stated under this spoiler will receive a message when a player uses Flint and Steel.

    Code:
    create-individual-player-logs: false
    
    False by default. If true, a log file will be created for every player.

    Code:
    memory-in-MB-until-new-block-logs-file-is-created: 50
    
    How big the block.logs file can reach until automatically creating a new block.logs file. (The old one is still kept)

    Code:
    memory-in-MB-until-new-chest-logs-file-is-created: 50
    
    How big the chest.logs file can reach until automatically creating a new chest.logs file. (The old one is still kept)

    Code:
    memory-in-MB-until-new-command-logs-file-is-created: 50
    
    How big the command.logs file can reach until automatically creating a new command.logs file. (The old one is still kept)

    Code:
    memory-in-MB-until-new-[player]-logs-file-is-created: 50
    
    How big a [player].logs file can reach until automatically creating a new [player].logs file. (The old one is still kept)




    Show Spoiler
    CommandWhat it does
    /sw or /superwandActivates/deactivates the SuperWand. To use the SuperWand, place a web block (item ID #30) where you would like to see block changes. To see chest changes, left-click a chest with a stick.
    /sl config or /superlog configShows you your config file options.




    Show Spoiler
    Permission nodeWhat it does
    superlog.notify.tnt.placementNotify's you when a player places TNT.
    superlog.notify.tnt.ignitionNotify's you when TNT is ignited by a player (Currently doesn't work when TNT is ignited with redstone).
    superlog.notify.flintandsteelNotify's you when a player uses Flint and Steel
    superlog.superwandLets you use the SuperWand
    superlog.configLets you see the config in-game


    [​IMG]
    <Edit by Moderator: Redacted mediafire url>
    [​IMG]
    [​IMG]
    Changelog:

    * v2.4 - Updated to MC version 1.0 and fixed a permissions bug.

    * v2.3 - Changed the MagicStick around.


    Show Spoiler
    * The MagicStick is now called the SuperWand.
    * The new command is /sw or /superwand.
    * The new permission node is superlog.superwand.
    * To see block changes, place a web block (item ID# 30). To see chest changes, left-click a block with a stick.




    Show Spoiler
    Show Spoiler
    v2.2.1 - Fixed the MagicStick permissions nodes.




    Show Spoiler
    * Fixed the MagicStick from causing lots of lag.




    Show Spoiler
    Fixed two bugs;
    * MagicStick not reading from all the split log files.
    * Player logs not being created for everyone when the plugin first runs. (Causes errors spamming the console until the player logs out and back in)




    Show Spoiler
    * Added the MagicStick
    * Optional command logging
    * Optional individual player logs
    * Log files split when reach a certain size set in the config file (Big thanks to @oz_revulsion for help with this!)
    * Ability to see your config options in-game. (Editing the config file in-game will come in the next version)
    * Added SuperPerms support? Not sure on this, don't have time to test if it works, so I'm not 100% sure it works.

    Bugs fixed:
    * Fixed air getting logged. (WTF?!)
    * Fixed paintings so they log.




    Show Spoiler
    * Fixed a bug with the dates.




    Show Spoiler
    * Fixed a few bugs with TNT/F&S notifications
    * Fixed a spelling error in the config file. (The "s" in "steel" in the option 'send-message-when-Flint_and_steel-is-used' needs to be capitalized)




    Show Spoiler
    * Initial Release
     
    Last edited by a moderator: Nov 13, 2016
    Olivki, Karlkorv, MrMag518 and 4 others like this.
  2. Offline

    oz_revulsion

    Amazing I loved the old version and this one is gonna be just as good I'm sure! I'll be installing as soon as I get home. Your awesome screem!
     
  3. Offline

    RazorFlint

  4. Offline

    thescreem

  5. Offline

    jtlcr777

    Does it show the coordinates of everything, including block placing and breaking?
     
  6. Offline

    thescreem

    Yes, it shows the coordinates for everything that gets logged, as well as the exact time.
     
  7. Offline

    jtlcr777

    good, because I needed a replacement for SimpleLog. Thanks!
     
  8. Offline

    thescreem

    New version, please read below and download version 1.1.

    v1.1 - Fixed a few bugs with the notifications and... *sigh* fixed a spelling error in the config file. If you have version 1.0, you will need to delete your current config.yml file and have version 1.1 create a new one without the spelling error. Or you can just fix the spelling error yourself, the "s" in "steel" in the option 'send-message-when-Flint_and_steel-is-used' needs to be capitalized.
     
  9. Offline

    Daniel Heppner

    Why do people keep making these? There are SO MANY LOGGING plugins already.
     
    Kohle likes this.
  10. Offline

    oz_revulsion

    IMO this one is by far the best.
     
  11. Offline

    thescreem

    I have originally created SimpleLog back in the beginning of May, this is just a re-done, revived version of it. Plus, I don't think there are many logging plugins that don't use MySQL.
     
  12. Offline

    Daniel Heppner

  13. Offline

    h0us3cat

  14. Offline

    thescreem

    All three of those log to a MySQL database.
     
    Olivki and jtlcr777 like this.
  15. Offline

    jtlcr777

    This, and some logging plugins either dont have a log file (your right click the block with an item to see who changed it) or the plugin doesnt show coordinates. Thats why I liked SimpleLog, and thats why I like this too.
     
    thescreem likes this.
  16. Offline

    Plague

    Sorry for the delay in submission approvals, I've been away for a while.
     
  17. Offline

    thescreem

    No worries. :) Hasn't been THAT long of a wait... :p
     
  18. Offline

    kwigle

    can't seem to download - I'm having trouble with drop box in general it seems............
     
  19. Offline

    oz_revulsion

    So I finally got around to installing and I am getting a log with weird dates?! I am in England so the dates here are dd/mm/yyyy instead of your yanky mm/dd/yyyy do you think this could be the problem? because it looks like the day is in the middle but the first set is all messed up. Any chance you could tell me if there is anything I can do (other than change my datetime format on my server, which wont be happening) or if you could possible put an option in the config?

    Code:
    [33/9/2011 11:53.43] LOG destroyed by: megaturtell at [X: -454 Y: 71 Z: 4]
    [33/9/2011 11:53.44] LOG destroyed by: megaturtell at [X: -454 Y: 72 Z: 4]
    [33/9/2011 11:55.27] SAND destroyed by: megaturtell at [X: -425 Y: 69 Z: 2]
    Cheers
    Oz
     
  20. Offline

    thescreem

    Oh, wow, that's... strange. I'll add an option in the config file of how you want the date to be set, and try to fix that strange date problem. (It's supposed to say [8/9/2011 11:53.43] DIRT placed by....) It seems I've been having problems with getting the dates right, as in SimpleLog the months were one digit backwards, now it's just a mess of numbers. :confused:

    Ah, sorry. I'll add a secondary download link to MediaFire.


    EDIT: Okay, I added a download link to MediaFire and fixed the bug with the dates. I'll release an update with an option in the config file to be able to change the date format soon.
     
  21. Offline

    ceastick

    I just thought of idea that would be helpful for me. Maybe each play could have their own log file, like for example, their will still be the general block.log, but their might also be a <name>.log for each player with the blocks they place and destroy. Helpful for catching greifers and not having to sift through the files to find the one player that did something.
     
  22. Offline

    thescreem

    Hm, good idea. I'll add this as an option in the config file, as not everyone might want it. ;)
     
  23. Offline

    oz_revulsion

    Just installed the latest version and its working a treat. Thanks again for the hard work, love it. May I suggest one thing further so that I can be lazy and not have to write a script myself for it? Can you make it so that the log file splits itself at a specified size. E.g. I set in the config 50,000Kb (50Mb). Then when the log gets to 50Mb in size SuperLog starts a new logfile like block1.log or something. Just because at the moment I have to FTP the file down so I have to write a bash script that copies the file when it gets to the that size and starts a new one. Not desperate but that would be a cool feature.

    Cheers
    Oz
     
  24. Offline

    thescreem

    Hm, I had that idea when I was making SuperLog, but I couldn't figure out how to get the size of the log file. :( I can try again, hopefully it can work this time.

    So for version 2.0 I have this so far:
    • Individual player log files. (You can enable/disable this in the config file)
    • Once the logs reach a certain size set in the config file they would split into multiple log files.
    • If you have a stick and right the permission node, you will be able to see what changes were made to the block you left-clicked with the stick.
     
  25. Offline

    oz_revulsion

    Code:
    import java.util.Calendar;
    import java.text.SimpleDateFormat;
    
    public String GetDateNow() {
              Calendar currentDate = Calendar.getInstance();
              SimpleDateFormat formatter=
              new SimpleDateFormat("yyyy/MMM/dd HH:mm:ss");
              return formatter.format(currentDate.getTime());
    }
    
    File file = new File("block.log");
    
    // If log is bigger than 50Mb (it's in bytes)
    if (file.length() > 50000000) {
         // File with new name
         File file2 = new File("block" + GetDateNow() + ".log");
    
        // Rename file (or directory)
        file.renameTo(file2);
    
        // Run whatever code you use to reload Superlog to create a new file
    }
    
    Drop 'er in and enjoy!
     
  26. Offline

    moe121

    I love this. <3

    I love you!

    I can't wait for v2, really it is much easier to use this than to go through the trouble of setting up MySQL. Thanks! :)
     
  27. Offline

    thescreem

    Oh, wow, I thought the .length() method did... something else... return how many characters are in the file.
    Thanks for this! :D
     
  28. Offline

    Weznezz

    I'm currently using this and i'm loving it!
    Very useful but I've noticed it doesn't log placement or destruction of paintings. That's my only request which would make this absolutely perfect for me :D <3
     
  29. Offline

    thescreem

    Oh, wow, I didn't notice that! I'll release a fix ASAP with logging paintings. ;)
     
  30. Offline

    todd422

    Can I check who has placed a block in-game? for example right clicking with a stick or other item.
    If so can I check who broke a block as well?
     

Share This Page