Super Logger
Project Moved!
This project has been moved to GitHub!
You can obtain the newest releases by clicking the "releases" button on the repo
Please note these builds have not been approved by bukkit staff!
SuperLogger
Current Version: 1.6
Description
SuperLogger is an advanced, highly configurable logging plugin for Minecraft!
SuperLogger categorizes and organizes log files by date and event type
Things SuperLogger Logs:
- Joins
- Quits
- Kicks
- Commands
- Disallowed Logins (Server Full, Not on Whitelist, Outdated Client)
Configuration
#If the plugin should automatically download updates
auto-update: true
#if we should notify ops when there is an update available and updating is disabled
update-notify
#if we should output extra debug information to the console
debug: false
#standard logging settings
log:
#if we should log commands entered
commands: true
#if we should make sure a command is real before logging it
check-command-exists: false
#if we should log chat messages
chat: true
#if we should log player joins
join: true
#if we should log player quits
quit: true
#if we should log player kicks
kick: true
#if we should log player deaths
death: true
#if we should log failed logins
failed-connections: true
#if we should log player IP addresses for events
player-ip: true
#if we should log player UUIDs (note this disables itself on versions lower than 1.7 due to UUIDS not working properly) player-uuid: true
#if we should log the co-ordinates (if applicable) to an event coordinates: true
# a list of commands to ignore when entered
blacklist:
- 'login'
- 'register'
Permissions
All permissions here are given to nobody by default unless otherwise noted
superlogger.bypass.connection: permission to bypass connection logging superlogger.bypass.chat: permission to bypass chat logging superlogger.bypass.death: permission to bypass death logging superlogger.bypass1.command: permission to bypass command logging superlogger.update.notify: permission to receive notification of updates, defaults to op
superlogger.bypass.*: permission to bypass all logging (the same as giving someone all bypass permissions as above)
superlogger.: all permissions, the same as superlogger.bypass. and superlogger.update.notify
Commands
There aren't many commands, but i may as well document them
- sl reload reloads superlogger's configuration file
- sl debug prints debug information to console, useful for getting help!
- sl version shows superlogger version information
Need help with anything?
Have a problem with SuperLogger? Maybe you have a Feature Request? Maybe you just want to talk? Join us on IRC in #zack6849 at irc.esper.net or click here!
Feeling generous?
If you appreciated this plugin and feel like throwing a little bit of money my way, there's a donate button on the top of the page, don't have money to donate? maybe ask me about helping test the plugin! you can also download the plugin through curse, downloads through there give me reward points exchangeable for real money :D
Hello again Zack, Can you think of any reason since the last update all of a sudden my logs have changed. I am running 2760 Bukkit as well. Instead of getting the subfolders like apr/22/ then various files (commands, chat, etc). Now for the last two days I am just getting one main log file titled per day like log-04-24-13.txt. Each day resides directly under the Super Logger folder not going into the APR folder and being parsed out.
@mdp123
Not a problem!
Excellent 1.4.4 fixed it! Thanks!
I see 1.4.4 just dropped...great I will try that. I was grabbing 1.4.3 but it alwasy shows up with errors like i posted, saying it is actually 1.4.2. I grabbed it again right before posting the error message.
@mdp123
You're using an outdated plugin, it's likely you need to update.
Update it seems like it is still recording the overall LOG but not any of the sub files like "chat" "commands" etc
Hello I am getting the follower error every time a player logs on: (i am using Bukkit 2758)
08:05 PM [SEVERE] Could not pass event PlayerJoinEvent to SuperLogger v1.4.2 Caused by: java.lang.NullPointerException at me.zack6849.logger.EventsHandler.onJoin(EventsHandler.java:66) at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:425) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462) at net.minecraft.server.v1_5_R2.PlayerList.c(PlayerList.java:204) at net.minecraft.server.v1_5_R2.PlayerList.a(PlayerList.java:100) at net.minecraft.server.v1_5_R2.PendingConnection.d(PendingConnection.java:129) at net.minecraft.server.v1_5_R2.PendingConnection.c(PendingConnection.java:44) at net.minecraft.server.v1_5_R2.DedicatedServerConnectionThread.a(DedicatedServerConnectionThread.java:41) at net.minecraft.server.v1_5_R2.DedicatedServerConnection.b(SourceFile:29) at net.minecraft.server.v1_5_R2.MinecraftServer.r(MinecraftServer.java:580) at net.minecraft.server.v1_5_R2.DedicatedServer.r(DedicatedServer.java:225) at net.minecraft.server.v1_5_R2.MinecraftServer.q(MinecraftServer.java:476) at net.minecraft.server.v1_5_R2.MinecraftServer.run(MinecraftServer.java:409) at net.minecraft.server.v1_5_R2.ThreadServerApplication.run(SourceFile:573)
@Rat_Cat12
Good, thank you VERY much for reporting bugs so often, nobody else seems to do it.
@zack6849
1.4.4 is working fine :)
@Rat_Cat12
eh, i guess its just my update check code, im deleting it now, sorry for all the errors everyone!
@LegndPowerdNube
I could see the use for this, i dont know when i'll get around to it though
@zack6849
Hasn't fixed it. I have to delete my config and redownload the jar every time I run my server to stop the error appearing.
What about a .zip function? For every day and it is optional?
@zack6849
I know how to get the file anyway :P
Btw, if you aren't busy it would by nice to have an option to log with DD/MM/YY date format.
@Rat_Cat12
i dont know if this will fix it for sure, but it should, while you wait for the dbo staff to approve it feel free to get it from no where (note these files are not yet approved by bukkitdev staff, use at your own risk.)
@zack6849
I think so.
Edit:Confirmed
@Rat_Cat12
Very odd indeed... was it the same error?
@zack6849
Very strange: Deleted the jar and downloaded it again and it works fine now. Very confusing as it was running 1.4.2 before and it is running 1.4.2 now (with the same config too).
Edit: Turned on old logging and the error started appearing again and kept appearing even when it was turned off.
@zack6849
Error Log:
http://pastebin.com/rtLPdZiw
Config:
http://pastebin.com/11qLUHj6
@iBlueBossa
Depends upon what you mean, do you just want a file or something that tells you how long a player has played the game?
Do you know if it will ever be added or anything?
just wondering.