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
@_Justyce_
Wow man, you are amazing! So when will i be able to download the new updated version?
@Povax
Hm, right away this is a minor error, i will update the 1.7.2 file with the fix of this error ;)
EDIT : Done
these are all the errors that im getting on the console right now http://pastebin.com/S7KwRmK0
@Povax
Yay it means an error has occured when a player typed a command. To help us to fix this error can you show us your console log ?
I have been getting this does anyone know what this mean?
@Gamerkd
Yes and approved ;)
Holy crap. Are you telling me after a day a half you have implemented and are testing a feature request? +100 internets to you my good sir.
@Gamerkd
Thank you (the 1.7.2 is under test )
Wow, responsiveness. That's a good quality with a developer. I haven't seen many of those in a while. Thanks man. I'll be watching for the update.
@Gamerkd
Right, in fact that's the objective : to log everything but i agree with you, i will make a way to prevent some aliases to be logged ;)
You need to add the ability to BLOCK certain command usage from the logs. I have the xAuth command which authenticates a password set by the users and it's being shown in plaintext. I need to show these logs to my mods but I can't show them the passwords so I need to parse it through PHP first which isn't helpful. And this has nothing to do with the xAuth command. The passwords are hidden in the server.log. But not your logs.
@vindicator209
Thank you to relate this error and it will not appear again ( next update ) and the event exception are mostly due to other plugins that does not make a "correct" event so some values miss, that's the error but in fact you just will not see the event on wich the error occurs
Thanks for your help.
Another issue I ran into was that somehow something in my Logs folder was probably corrupted, and bukkit hung when it enabled UltraLogger. The problem was resolved when I renamed the Logs folder. I didn't touch anything in that folder.
On yet another note, using a netherportal with Multiverse pulls this error (may or may not be related):
@Redx94 No you do NOT need an other plugin and it's working but you may not configure or understand correctly this feature
@Redx94
nvm i found it but the plugin isnt working do i need to install another plugin?
how do i find the history of a block?
@vindicator209
log entries are stored in a buffer of 20 entries and after the buffer is full we write it, on disablement the buffers are emptied after their contents have been written even if they are not full. Are you using MacOS ?
Hi, are log entries being directly written to the flat files or are they held until reload? I'm getting OutOfMemory errors after recently installing UltraLogger, I'm trying to determine the cause.
There isn't console log
Please add it
@jamcghie
Thanks to you :D and the new build has been uploaded ;)