Properties
The configuration is based on those from Log, the differences are the possibility to enable and disable features of LogEx and to define the language to be used. Also the format is now Yaml instead of Properties. LogEx' settings are stored in the config.yml file in the /plugins/LogEx folder. This is the content of mine (I only changed the language):
items: stick: '280' bone: '352' feather: '288' arrow: '262' filters: commandLogging: commands: [] general: language: en enableMultithreading: true autoUpdateCheck: true enableStatistics: true useAlwaysBuildInLanguage: false permissions: handlerToUse: '0' features: worldEditLogging: true blockLogging: true bucketLogging: true pickupItemLogging: true mobKillLogging: true ipLogging: true chatLogging: true spawnEggLogging: true commandLogging: true deathLogging: true gameModeLogging: true worldSwitchLogging: true do_not_touch: last_vcode: '15' autocleaner: enabled: false interval: '1' hoursToKeep: '168'
The different options of the config.yml file
"items" section
featherItem
- "288" by default
- This option lets you define the item id of the item which can be used to show material datas of a clicked block.
boneItem
- "352" by default
- This option lets you define the item id of the item which can be used to show modification datas of a disappered (no longer contained) block.
stickItem
- "280" by default
- This option lets you define the item id of the item which can be used to show modification datas of a clicked (contained) block.
"features" section
ipLogging
- "true" by default
- This option lets you enable or disable the feature for logging the logins of the players.
- true: Enabled
- false: Disabled
blockLogging
- "true" by default
- This option lets you enable or disable the feature for logging every block modification done by the players such as breaking / placing of blocks.
- true: Enabled
- false: Disabled
pickupItemLogging
- "true" by default
- This option lets you enable or disable the feature for logging every item picked up by a player.
- true: Enabled
- false: Disabled
bucketLogging
- "true" by default
- This option lets you enable or disable the feature for logging every bucket modification done by the players such as emptying / filling water / lava.
- true: Enabled
- false: Disabled
chatLogging
- "true" by default
- This option lets you enable or disable the feature for logging every chat message sent by the players.
- true: Enabled
- false: Disabled
spawnEggLogging
- "true" by default
- This option lets you enable or disable the feature for logging every spawned mob from a spawnegg by the players.
- true: Enabled
- false: Disabled
commandLogging
- "true" by default
- This option lets you enable or disable the feature for logging everycommand used by a player.
- true: Enabled
- false: Disabled
deathLogging
- "true" by default
- This option lets you enable or disable the feature for logging every death of the players.
- true: Enabled
- false: Disabled
gameModeLogging
- "true" by default
- This option lets you enable or disable the feature for logging every gamemode switch made by the players.
- true: Enabled
- false: Disabled
worldSwitchLogging
- "true" by default
- This option lets you enable or disable the feature for logging every world switch made by the players.
- true: Enabled
- false: Disabled
worldEditLogging
- "true" by default
- This option lets you enable or disable the feature for logging WorldEdit modifications. (Very poor support at the moment...)
- true: Enabled
- false: Disabled
mobKillLogging
- "true" by default
- This option lets you enable or disable the feature for logging mob kills.
- true: Enabled
- false: Disabled
"filters" section
commandLogging.commands
Here you can set a list of commands which will be permitted being logged. I added "login" as default and I want you to leave it there, because this command is normally used for players AND admins to login to a server using their password. Without this entry, it can be possible for admins to watch an users password. I'm against that because it hurts the users privacy!!!
"general" section
language
- "en" by default (English)
- This option lets you define the language to be used in LogEx. To change the language in-game, you can also use the /log set-language <language> command (See Commands and Permissions)
- As of RC1.1, german, english and luxembourgish are included (See Multilanguage stuff)
enableMultitasking
- "true" by default
- This option lets you turn the seperate thread for commands off or on. There might be (in some cases) a higher CPU usage while turned on. If you have issues like this in 1.3 or higher so try to turn it off
"autocleaner" section
enabled
- "false" by default
- This option lets you enable or disable the autocleaner
interval
- The interval in hours of each clean process
hoursToKeep
- A limit in hours for each entry in a database to be kept
"do_not_touch" section
- This section contains values to allow LogEx to work properly. If you modify one of this values, there might be errors which may occur...
-
View User Profile
-
Send Message
Posted Aug 7, 2012This looks great, gonna run some tests. I like the in game logging style, like how you see info when interacting with stick/feather etc, but because a lot of the time i'm checking logs from teamviewer, do you think that you could do something like a txt file of some logs, or am I just missing where they are :P Its your mod though, its up to you, Either way, great job! :D
Have a kirby <(^-^)>
-
View User Profile
-
Send Message
Posted Aug 8, 2012Thank you ;)
Logfiles are saved in "LogEx Database" in a not for humans readable format. Maybe I can implement a command to save a txt file with a readable changelog.
-
View User Profile
-
Send Message
Posted Dec 31, 2012This is a great plugin. I couldn't Get WorldEdit to install corectly so i couldn't get logblock, but then i found this and it solved all my problems. One Question, How do i change the config.yml file? Every time i change it, it magically changes back.