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
@iBlueBossa
I'm afraid not.
Does this log how long they have been online?
@Rat_Cat12
Paste the error for me please.
@zack6849
Deleted config several times, still has error.
Just a note, for anybody getting a NullPointerExcepton when a player joins, delete your old config, i recommend doing this most updates that mention having new config options, i'll probably get around to having a better config option soon. if you guys have anything you need to talk about, leave a comment or chat irchowever don't join irc then leave within like 5 minutes, im not always there, i'm not a robot, give me some time to get back to you.
@Chalkie19
Care to elaborate? From what i understand you want a config option to allow it to "save" where a player dies, so you want a config option that, if enabled, adds coordinates of where a player died?
Also if you wish to discuss something of this nature with me, i prefer if you use IRC because im bad at checking this sometimes :)
@zack6849
Co-ords would be nice as well.
@Chalkie19
ie just say where in the world the player died?
@PhoenixOfWar
I have a 70-100 player server, and it feels very light weight (Timings wise).
@zack6849 Any chance of a minor addon of and option to save co-ords of someone who died?
How intensive is this on the server? Does it hurt performance?
@pkminer
I havent heard of any problems with 1.5 as of yet, test it yourself and if thers' a problem let me know!
Does it all work fine with 1.5?
/orgasm. Ill will be checking this out this weekend.
@Chalkie19
i have this working! look for it in the new update ^_^
@zack6849
Thanks.
@Remi_Scarlet
do you want it in a single file for all info? or all of the log files that are there for an entire server usually
@Chalkie19
i will give this a try soon :)
Hi! Was wondering if you have the functionality of also logging users separately in their own file. I don't seem to see it as a listed feature and if you don't have it, if you could add it. The log could go under /super-logger/players/<player>.log/txt or the like.
Me again :)
Any progress on finding out a way to disable certain commands being logged? Example /login /register ect?
Thanks.
@xakiru
it saves them as .txt, but i suppose i can change it to log if you like.
@poiNt3D
it already logs them per-day if the old logging option is disabled or did you mean one single log file for every event per-day?
Why not write all events in one (per day) file?
Maybe you could add this option...