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
So Superlogger isn't logging anything anymore. I've tried deleting it and installing it but it wont log anything. And There's no errors.
I could help with beta testing of you want. One question though, is there a way to run both the beta and the stable version at the same time as I need the plugin to keep a log of the chat and if the beta somehow fails to record data, that could be a problem for me.
Thanks for your response.
@zack6849
I'd be willing to test your beta update. Shoot me a PM if you like.
@honeychook
I have a beta update that MAY fix this but i also have newer logic and i needed pople to test, i havent released it yet because i need people to TEST it before i release something that im not sure works >_<
@zack6849
I had already tried those steps (except for deleting the update folder) Still on 1.4.7 and it is working great. (this is a amazing plug in btw ;) )
@brsserveradmin
Not that i know of.
@zack6849:
Is there significant difference between JDK/JRE 1.7.0_17 and JDK/JRE 1.7.0_04?
The 1.7.0_17 info is from SuperLogger 1.4.9 MANIFEST.MF file, and Java 1.7.0_04 is what I'm running on my machine. Could this be a possible source of the problem?
@zack6849:
I followed your instructions re deleting and reinstalling, but no joy; Console says SuperLogger is loaded and metrics are running but no log entries are written to the log files.
I switched back to 1.4.7 and logs get updated appropriately.
@Chalkie19
Thanks for the info chalkie!
To all who seem to be experiencing issues with logging
Try the following
@zack6849 Sorry to take long to get back to you.
Just as @honeychook said, no errors in console.
I'm running CraftBukkit beta release 1.5.2-R0.1 (Build #02771) on Mac OSX 10.8.4 (build 12E55).
@zack6849
Server Version: Spigot 1.5.2 (866)
Plugin Version: v1.4.9
Current Problems: None. All logs are writing correctly.
@honeychook
That's extremely strange, it seems to work for me, anybody else who can confirm this issue?
@brsserveradmin
Thanks! I had the same problem (just found out today). Followed what you did and it fixed the problem.
@zack6849
No errors that I could find in the console. The last log file that had something in it was the 27'th of May 28'th onwards are all blank.
Hope this helps fix the problem.
Server is running craftbukkit v1_5_R3 Beta build
@brsserveradmin
Odd, are there any errors in the console?
zack6849 -
I found that my logs were empty from about mid-May.
I set auto updating to false and did a little testing of the various releases since April. The testing demonstrated that releases 1.4.8 and 1.4.9 will generate the SuperLogger folder, the Month and Day folders, and the actual log files, but will not write data to the files themselves.
The last working release for me was 1.4.7; once installed all logging was back to normal.
Do you want a formal ticket on this, or is this info good enough?
@joehot200
No problem, glad to worked
Tried the new version, it works :)
Ty ;)
@joehot200
@joehot200
@Grave9912
sorry guys! i'll try my best to fix this ASAP!
edit: the newest build i uploaded should fix it, we have to wait on dbo staff to approve it though
I have a slightly different error, it seems.
http://pastebin.com/nY76CZ32
@Grave9912
Confirned, i am getting this too. Immediate disabling of the plugin stopped the errors.