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
@Superfly1021
It does work. if you hava an error submit a ticket saying so.
@zack6849
Sounds great. Not to worried about deleting the logs rather then have to download a giant one just to check something. It's about 3 MB's a day atm and since I am using FTP I have to Re download it every time I want to view it :)
Thanks for the support.
@Superfly1021
This plugins is working fine, maybe something your end is conflicting with it.
This would be great... IF it worked.
@Chalkie19
Im looking into the method for making the log files per-day, however i wont be able to make a method to delete the logs after a certain amount of time in the near future
12 hours with the logger on, all working great but at 1MB already :)
@zack6849
Ok that sounds awesome (the 4 days 17k6KB), unfortunately I have not been able to test it yet since ill need a restart on the server. But it's there ready to go on the next restart.
As for the login and register command if you can that would be great, I just see it as a little bit of a security issue if registers and logins are stored. (I think most auth plugins use /register and /login) I appreciate the fast reply.
Chalkie
@Chalkie19
Well, as for the files, my current log that i've been using for about 4 days is 176kb. When it comes to the matter of making the files by day, i could look into this but i dont know if it would be possible.
And as for the login and register being ignored, the only way i could go about this is seeing if the command contains the word login or register, and if so don't log it. which could be a tad buggy. If you'd like this i could try and implement it.
Looks nice, how big do the log files get? I know just a couple of days my server log (Console) can be come 10+ megs easy.
Could you add an option to make the logs only daily, this would be easier to check something and not have to open a 1 massive file.
Another option to Ignore the /login and /register command (If that isn't already an option)
I do like the prefix of what it was (kick/ban/ect).