UltraLogger
Latest build : 2.1 Craftbukkit : 1.5.2
More than 10k downloads !! Thank you !!!
Beta UltraLogger v2.2 available here, you must delete your old configuration file
What is it ?
This is a logger plugin, a logger plugin logs informations to anything related to your servers so you know what was done on your server when ever you want.
Better than Big Brother !
The utlimate logger, nothing can be done without be logged !
A video tutorial on this plugin by never2nv on UltraLogger v1.0 :
The logs are flat files or can be logged into a MySQL database, the flat files are saved in a directory called Log that is in your server directory, you can read them with your prefered text editor, for more information about MySQL logging see this page
Features
- And soon much more !
- Rollback block commands
- Auto save
- In game history of blocks by right clicking an item, the player must be an OP or must have the permission ul.history
- MySQL support for all loggers see the page : here
- You can force saving flat files by reloading your server
- When something is logged the date and the time is specified
- If a player is an op or has the permission ul.admin the [Admin] prefix will be shown in the log
- The gamemode will be displayed like : (CREATIVE) or (SURVIVAL) and the world beetween brackets.
- Update Checker checks if you have the lastest build of this plugin
- Anti command logger ( commands you do NOT want to be logged ) File : silent_commands.txt
- Log Customization, you can configure what your loggers log and create new ones. see this page for futher information
- You can enable or disable MySQL loggers in the config.yml file
Commands
command | information |
---|---|
//ulundo <x> <y> <z> [x] [y] [z] | undo the latest block placement/destruction at the specified x,y,z but if two locations are written that will do the same thing for all blocks beetween these locations ( like in WorldEdit the two locations taht you choose with the wooden axe)(your action can be cancelled by typing the redo command but after disconnection you couldn't cancel) |
//ulredo <x> <y> <z> [x] [y] [z] | the same command as undo but redo what you've canceled with the undo |
Permissions
permission | information |
---|---|
ul.* | allow the player to use all the features of UL ( grants all permissions of UL except the perms to avoid to be logged ) |
ul.history | allow the player to see the history of a location |
ul.admin | players with this permission will be shown with the admin prefix in the logs |
ul.rollback | allow players to use rollback commands |
ul.avoid.X | allow players to avoid to be logged on the event with id=X or on all the events that contains the group X. For further information see here |
Config file
YOU MUST DELETE YOUR OLD CONFIG FILE
The config can only be edited when your server is stopped
#General properties #Check or not if you are using latest build available check_updates=true #Enable or disable ingame use of an item to see what happened at the specified location history_logger=true #The id of the item with you can see the log of a location item_revealer=280 #File logger properties ---------------------------------------------------------------------------------------------------- #Time in seconds beetween each auto-saves of the logs auto_save=3600 #Overwrite or not the last logs overwrite=false #Maximum number of lines of a log file ( 0 for no limit ), it will erase the first 10% lines of the log max_lines=0 #Do NOT modify this value please, it is used to know last time UL created the log folder last_created=1366823381660 #The number of day until UL creates a new log folder folder_duration=7 #For more information on configuration see http://dev.bukkit.org/server-mods/ultralogger/pages/logger-configuration/ log_block=1@11 log_chat=69 log_command=70 log_craft=12@15 log_entity=&entity log_inventory=&inventory log_player=&player log_vehicle=59@62 log_weather=63@65 log_world=66@68 #Event groups ---------------------------------------------------------------------------------------------------------------- group_entity=16@32 group_inventory=33@35 group_player=36@58+71+72 #SQL logger properties ------------------------------------------------------------------------------------------------------- #While host value is equal to "blank" or "null", SQL will be disabled host=blank port=3306 name=root pass=1234 database=blank table_prefix=UL #SQL Loggers couldn't be fully configured so only enable/disable sql_block=true sql_chat=true sql_command=true sql_craft=true sql_enchantment=true sql_entity=true sql_inventory=true sql_player=true sql_plugin=true sql_vehicle=true sql_weather=true sql_world=true
Coming soon
- One log for each player feature ( beta 2.2 )
- LogViewer
- Please post suggestions
Support us !
You can easily support us by using one of the icons below :
Made by supercrew632 :
The BBCode to add is :
The HTML code to add is :
<a href="http://dev.bukitt.org/bukkit-plugins/ultralogger"><img src="http://dev.bukkit.org/media/images/58/242/icon_UL.jpg"></img></a>
Repo
Credits
To @_Justyce_ and @roelmb
@teozfrank
I'm testing it for him.
@_Justyce_
where can i get it?
i've just made the 1.7 DEV build without this issue but it will stay a dev build since you confirm me that it's stable. Thank you
@_Justyce_
I can help you test things out maybe. :P Since I have my own server I can submit bugs and other errors.
@jamcghie
Don't worry i'm not stressed, i just doesn't like when my users can NOT use a stable version of my plugin xD
@_Justyce_
I am sorry if your stressed, I can understand. If there was more I could do to help you I would. I hope you figure something out.
01/08/2013 : Please do NOT download the latest build, it's NOT stable, i'm currently fixing this regrettable error.
Note : this message will be updated when a stable build will be released.
@frdmn
That is one of those errors that I get that floods the console unless I disable it. Based on all the input, I think he will be able to fix our issues fairly easily.
@teozfrank
I have the same problem: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9
@_Justyce_
My log folders and the files in them are being created properly, but no text is recorded in any of them.
small problem in the console with ultralogger can provide some of the errors here: 16:34:59 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:01 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:35:03 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:11 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:35:11 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:17 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:35:17 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:21 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:21 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:35:25 CONSOLE: [SEVERE] Could not pass event PlayerToggleSprintEvent to UltraLogger v1.6.9 16:35:25 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:35:27 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:33 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:35:33 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:35 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:39 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:35:41 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:43 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:35:43 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:53 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:35:53 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:57 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:35:59 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9 16:36:01 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to UltraLogger v1.6.9 16:36:01 CONSOLE: [SEVERE] Could not pass event BlockBreakEvent to UltraLogger v1.6.9
@_Justyce_
The logs do seem to update correctly. As far as I seen... However, due to these errors, that flood the console a LOT still, it causes bad lag. If you want to, I have teamviewer and you can watch my server sometime as it floods with errors. Its up to you. Or if you would like, I can post more errors. I disabled it for now since it caused way too much lag.
It always seems to start this issue after the restart... Isn't there a way to add an "IF THEN loop" to check the date in order to change folders per day? If so wouldn't that be easier? Or do bukkit plugins not have them?
@Banndon All the errors are due to the same thing a null pointer exception in my class logger file ( who writes the logs ) i ll take a look at it to fix this error. Are the logs correctly written ?
@_Justyce_
More log from the server, it works better but still throwing errors.
When plugin restarting: http://pastebin.com/NqYxTmDB
When restarting server: http://pastebin.com/DGHp62J2
Random Error(running I assume): http://pastebin.com/wGnJxX8A
Random Error(Chat?): http://pastebin.com/nwLSDecp
Random Error(Food?): http://pastebin.com/d1Ud1Q4z
Hope this helps :) I am using the UltraLogger v1.6.9 for CB 1.4.6-R0.3
@_Justyce_
Thanks for the credit for the bug fix! :D
Hi, I'm getting this error and it repeats several times per second:
http://pastebin.com/D5P6W8AW
I'm updated to CB 1.4.6-R0.3 and have all other plugins disabled.
@jamcghie
No, there isn't really dev build but it should lol ( i will now make dev build before release ) the dev build step is a bit boring when you think everything is working
@_Justyce_
Is there a release or dev build I could get of this fix? Also, glad to help. Whatever keeps this awesome plugin working helps! I will definitely post any other errors, thank YOU for being so active about things.
@Thurgh
You're right, we forgot the comma, thank you.
@jamcghie
You're right i placed the "timer" at the top of the plugin enablement so it is always fired, but i've fixed this now, thank you
@_Justyce_
It starts just fine but after running for 10 minutes, it disables and re-enables. At that point there is always something that freaks out. At some point the plugin will disable and re-enable several times a second. (Lagging the server, its currently disabled so griefers can have their way atm.)