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
Getting a severe error, I noticed you're in there.
Is it possible for you to help me out?
http://pastebin.com/tLu9mbDr
@zack6849
/logs commands joehot200
<Shows the last 10 commands joehot200 executed>
@Lord_Cuddles
I don't know about this one, it seems as if it would be a bit resource intensive. @rudolf323
I'll look into it i suppose, care to elaborate on how it would work?
Can you make option: log players to different files ?
I have a suggestion, is it possible that you could make specific player logs be available from admins in game? For example:
/logcheck zack6849 chat
Would show the last 15 or so things that the player Lord_Cuddles has said, and
/logcheck Notch command me
Would show the time and date of when the player Notch has used the command /me
@joehot200
Glad to hear you find it useful :)
@zack6849
Well, just to tell you how useful the plugin is, today i found 2 hackers who had hacked into admin's accounts, and 1 abuser who used /stop.
Busy day ;)
@RCEKH
Please describe in more detail. he could add the position of a certain player or action - though logging worldedit is a bit harder.
@RCEKH
not quite sure what you mean by this, please be as clear as possible when explaining these things.
hi, can you add the position of the player or action ? as ex. which position was modified by worldedit ... or similar.
thx.
@joehot200
@toxictroop
Thanks for the feedback :D
Useful plugin. Thanks for coding 'tis :3
Very good!
@gvlfm78
permissions nodes are no longer being removed, that poll is old and i should have removed it
@mdp123
good to here its working now, no idea how in the world i managed this.
Don't delete the permission nodes! This is the only logging plugin with them! Keep them please!
Brilliant! That was in Zack! I grabbed the prior to latest version and it shows up as 1.4.2 and immediately goes back to creating discrete folder for 04/25. Good catch!
Zack I didnt catch that but you are right. I just deleted Super logger and grabbed the latest again..and it does show up as v1.2. Interesting.
@mdp123
please check your server.log and tell me if its giving you any errors anywhere, because your config looks fine :/
WOW i just realized i managed to upload version 1.2, no idea how the hell i managed that, updaing ASAP
Thanks Zack It is consistent at least with how it creates the log file but still doing the same thing just making one massive log dump inthe plugin folder and naming it, for example today it named it log-04-25-13.txt. So there is some logic that is driving a consistent behavior at least. On hand I dont actually mind as at least it is still making a log!
Here is the config file: log-commands: true log-chat: true log-join: true log-quit: true log-kick: true log-death: true log-ip: true log-death-location: true log-disallowed-connections: true use-old-logging: false use-permissions: false auto-update: false notify-update: true filters: - 'login' - 'register'
Shoot..in the past it looks all lined up...but when posted it jumbles up the config..sorryabout that.
@mdp123
May i see your config, i cant think of any reasons this would happen though o.o