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
-
View User Profile
-
Send Message
Posted Oct 19, 2012@Chalkie19
thanks :) also, i did look into the blocking commands with login and registering and its just not practical, nor does it work, if i do find a way to do this that makes sense i will, but for now this feature will not be implemented.
-
View User Profile
-
Send Message
Posted Oct 19, 2012@zack6849
All right thanks, and gratz on 13k Downloads :)
-
View User Profile
-
Send Message
Posted Oct 19, 2012@Chalkie19
Im still looking into blocking the register and login commands, but there is still the one log file that has everything, the otheres were just because somone requested they be added.
-
View User Profile
-
Send Message
Posted Oct 19, 2012@zack6849
Yes please, I like how it is atm 1 log file per day all included :) I'd still love the removing of /login /register commands :)
-
View User Profile
-
Send Message
Posted Oct 19, 2012@Chalkie19
If users wish to keep just one lig file I can code in an option for it.
-
View User Profile
-
Send Message
Posted Oct 18, 2012@zack6849
Thanks, more then likely wont update. Don't like the idea of septate logs that much.
-
View User Profile
-
Send Message
Posted Oct 18, 2012@Chalkie19
Fixed this, also re-enabled the auto updater, had it commented out while testing and forgot to re-enable it.
-
View User Profile
-
Send Message
Posted Oct 18, 2012@456205841sdfsdfs
Tekkit is using 1.2.5 Which uses PlayerChatEvent, which is no longer used in 1.3.2, so some of my plugin will not work on 1.2.5 Specifically the chat logging, as for the logging try deleting the whole superlogger plugin folder and restarting the server, because i just tested the plugin on tekkit and it was still logging a few things.
-
View User Profile
-
Send Message
Posted Oct 18, 2012On my tekkit server, The log file is Empty.
-
View User Profile
-
Send Message
Posted Oct 16, 2012@Chalkie19
I've noticed this too.. no idea why it does that, ill look into it asap :)
-
View User Profile
-
Send Message
Posted Oct 15, 2012Not a massive problem but it updates the plugin every time regardless if it is updated or not.
Also on the command logging can you do if the command contains /login or /register it only logs XXX logged in or XXX registered. Instead of .getMessage()
Thanks :)
-
View User Profile
-
Send Message
Posted Oct 15, 2012it should all be logged in seperate file! As seen in STAB... where ip are logged in the file PlayerIPlog.txt
also would prefer to have logs be in .yml if possible.
This plugin is exactly what i was looking for and i hope the creator takes my suggestions because they would perfect it!
-
View User Profile
-
Send Message
Posted Oct 15, 2012@Chalkie19
Derp, you're right, no idea how that happened. just uploaded the fix, awaiting approval.
-
View User Profile
-
Send Message
Posted Oct 15, 2012@Chalkie19
well i just downloaded the newest one and tested it and it worked. ._. lemme try this again.
-
View User Profile
-
Send Message
Posted Oct 15, 2012@zack6849
No what I mean there is no Config file at all, even in the .jar it's self, so it cant save/load the config.
-
View User Profile
-
Send Message
Posted Oct 14, 2012@Chalkie19
odd, it worked fine for me, try deleting the config.
-
View User Profile
-
Send Message
Posted Oct 14, 2012@zack6849
No config file was with the download not was it part of the .jar file so it does not work :(
-
View User Profile
-
Send Message
Posted Oct 14, 2012@Chalkie19
posting the update now :)
-
View User Profile
-
Send Message
Posted Oct 8, 2012@zack6849
Awsome to hear, 12+ megs now... starting to take a while to open in notepad :)
Edit: Also can you add the option of when someone dies and if possible by who. Thanks!
-
View User Profile
-
Send Message
Posted Oct 8, 2012@Chalkie19
I just finished the new log setting, gotta test it a few days to make sure its stable :)