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
@KillerKretscheLP
Hi, You got this error because the new event when a player chat didn't exist in 1.2.5 so it couldn't listen to it else the chatlogger will not work for Minercaft 1.2.5. I change the compatibility with versions to remove 1.2.5, because it was a bit mistakke by me.
Hi again :D Nice to hear about the prefix permissions ^^
So i have a Tekkit Server with MC 1.2.5 and ultralogger seems to incompatible to 1.2.5, but at bottom it says: Latest build : 1.6.1 Craftbukkit : 1.3.2 & 1.3.1 & 1.2.5 Error (same error at other new plugin versions [1.3.*] that arenĀ“t compatible to 1.2.5)
Please Help!!! Thanks :D
@_Justyce_
ok that should still work :)
@roelmb
I didn't change any thing i only changed the player.isOp() into MainLogger.isOp(player) :P
@_Justyce_
you can't just change table columns from boolean to something else :P and it isn't recommended either to add a new column every update
@roelmb
Lol i've already done it in SQL logger and flat files :p
@KillerKretscheLP @_Justyce_ I'll check on it but we might need to seperate Op and admin in some sort off way because right now I save it as a boolean in sql what makes it impossible to change at this very moment without adding loads off stuff
File logger on the other hand shouldn't have that much off a trouble in changing that
@KillerKretscheLP
That's a good idea ;) I think i'll make that player that are ops and players that will have the permissions ultralogger.admin will be shown as Admin
Or maybe better a custom Permission for showing that user as an [Admin] in Logfiles with an option to make this on/off
Is it possible to make the shown [Admin] in the log files ready for Permissions? So the [Admin] shows when a User has the given Permission ultralogger.history ... I Hate the standalone op i want to dont use ops ^^
@Stuntweed
Their is a chest logger already just check your inventorylogger :)
@_Justyce_
Possible to add a chest logger? Log all activity in and out of chests?
@odv1983
As roelmb said it couldn't be due to this plugin because we just log so we don't change anything... But you may look for others plugins issues or may due to the latency on your server.
@XXO2 Did you mean for the latest development build ?
@Szajkop
We'll check into it if its even possible Are you meaning Tekkit or only buildcraft and industrialcraft?
@XXO2
This plugin is compatible with the latest version of craftbukkit You could have just tested it yourself ...
@odv1983
We don't change anything to inventory handeling we only log the even so this can't ever happen
PLEASE put update of plugin for next version of craftbukkit!
When the inventory logger is enabled, do a fast clicking in your items on inventory to duplicate items.
I disabled the inventory logger and no more this issue.
Hi thanks for this awesome plugin! Just one idea: Build Craft and IndustrialCraft 2 support! coz theese mods +this plugin are filling up my server with BlockBreakEvents and BlockPlaceEvents!
@allpeg
Any UTF-8 character should be saved as their normal character no matter what so if russian characters are included into UTF-8 (i thought they where) then they should be saved :)
And its not a big deal on rewriting that as only the loggers for chat and commands should be rechecked. I'll start on it right away. I'm just not used to using sql inside java. Sorry for the table names they are kinda crap right now because i didn't have enough time to check into everything before it was released. Optimization is key in next big update
The max line thingy and changing on the fly is something for justyce thats not my part :D
EDIT : I just uploaded a hotfix thats waiting for approval its using Mysql_Real_Escape_String as a hotfix for the problems that occured. Its temporary though as prepared statements are ofcourse a better way to handle this.