Configuration Options
Return to main page
Default config.yml
# LDLogger configuration file # Request new features on GitHub general: log-staff: false xray: enabled: true options: inform-players: false diamond: true iron: true emerald: true shouting: enabled: true options: min-chars: 10 min-ratio: 0.7 ignored: - LDLogger kick-player: false kick-message: Shouting. Don't use CAPS. kick-cancel-chat: true
Node descriptions
Node | Default | Description |
---|---|---|
NEW general.log-staff | false | Setting this to true means people with LDLogger.staff will be logged. |
xray.enabled | true | Enable/disable the entire ore logging feature at once |
NEW xray.options.inform-players | false | By default only staff are told about ores being discovered. Setting to true informs all players. |
xray.options.diamond | true | Configure whether diamond mining is logged |
xray.options.iron | true | Configure whether iron mining is logged |
xray.options.emerald | true | Configure whether emerald mining is logged |
shouting.enabled | true | Enable/disable the entire shouting feature at once |
shouting.options.min-chars | 10 | The minimum length of a message before it can be considered to be shouting |
shouting.options.min-ratio | 0.5 | The minimum lowercase-to-caps ratio before a message is considered shouting |
shouting.options.ignored | LDLogger | Provide a list of words that are not counted as part of shouting detection (e.g. your server's name) |
NEW shouting.options.kick-player | false | By default this is false, which means that CAPS messages are automatically converted to lower-case. Set to true to revert to old behaviour, where the player is kicked instead. |
shouting.options.kick-message | Shouting. Don't use CAPS. | Customise the message displayed to users when kicked for shouting |
NEW shouting.options.kick-cancel-chat | true | Setting to false means that chat message still appears, even if player is kicked. May conflict with some chat plugins if set to false, e.g. Herochat. |
Remember!
Always run
/ldlogger reloadafter modifying the configuration file, instead of restarting the entire server. It's better for everyone.