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
@DiverseCraft
I see no reason to, the main reason i made this plugin was to have human readable, categorized logs, not to throw them into a database
Could you add mySQL?
@Aliqux
Not a problem, glad to hear you found it useful
I would like to thank you for this plugin. I have been looking for something that would log the connections to my server without a lot of extra logging that I didn't need. This was exactly what I was looking for. Now I can keep track of when my children's friends log ins when I am not there and actually read the log easily. Once again thank you so much.
@iPedro2
Are there any errors?
I can't get deaths to be logged in the deaths.txt file, only in log.txt. I have log-death: true
@DardoTheMaster
Try setting check-commands to false in config.
It doesn't Log worldedit commands....
@HeroCC
...just get a Flatfile vote listener... He's not going to make a .txt file for everything!
Can you make a feature where if you do /sl log votes 'JimBob Joe Just Voted!'
Then It will make a new file called votes.txt and then it will log JimBob Joe Just Voted!
Thanks!
@mdp123
Glad to hear :D Thanks for all the feedback guys ^_^
Zack I have had the beta going for 24hrs now and it seems to be parse out the data now. Thank you !
@brsserveradmin
Sweet! Thanks to Everyone who tested this and sent feedback, it helps me more than you can imagine, uploading this release as a reccomended build now :)
Update on installation of beta… The beta appears to have fixed the problem. All logging functions are working. Thanks Zack!
@mdp123
I'm not quite sure what the issue is and or was, but i did re-write alot of the logic in the beta and it may have fixed it, so i suggest trying the beta, and if it works, then good!
Zack I just grabbed the beta and will try it out
@zack6849
Hey Zack
I just downloaded the rewritten beta and logging of server activity seems to be working well so far. I'll check in later this afternoon with more info.
Thanks for working this out.
Just now checking the page but looks like I am having same problem as others. I am on Super Loger version 1.4.9 and Bukkit 2771. I get random success with logs. Some days it seems to capture them all and break them out properly, some days i get one log file with everything and no break outs, some days i get the breakouts all with 0kb file size accept for one of the break outs. For example June 13 i have one big log files, but june 12 it created all of the categories but only populated commands.txt and the others .txt break outs were all 0kb, June 7 only shows log.tx, june 8 all .txt list break outs listed but entries in only chat and command. It seems to be very random in what it tracks. I have removed and reloaded a couple of times with no difference. I have not gone back to 1.4.7 but can if needed. Lastly there are no error logs showing up. Is this what the beta is supposed to address?
Since the person i sent the beta to hasn't replied in about three days, I'm going to post the beta publicly
THIS BUILD HAS NOT been approved by bukkit! use at your own risk!
So basically, I have a re-write of superlogger that I've wanted to release but it needs beta testing, for those of you who want to help, download the jar from hereand just use as normally, file a ticket if you get any errors,
@honeychook
i see no way that would work, i'll send you a PM