features/Configuration

Configuration

The configuration is done as usual with the config.yml in the plugin-Directory. The configuration-file is well documented and contains a explanation for every available option. The syntax of list-entries aren't easy for YAML-beginners, so better use ingame configuration.

The latest full documented configuration can be downloaded from the CI-Server: default_config.yml

In-Game-Configuration

You can use the /lc config command to modify the whole configuration via console or ingame (op/permission required). The options are grouped by module. When you just type /lc config you get a list of all available options/groups. Just add them to the end of the command, and you get the description of the option and the current value or available sub options.
This is especially useful for list-entries, that allow you to add or removed entries without struggling with the yaml syntax.

Changes to the configuration via commands are only changed in memory until you use /lc config save. Only then, the configuration is written to disk and used on server restart.
This allows you to change the enabled-settings of modules to temporary enable/disable those modules. But without save, on restart the original settings are restored.

Configuration-Upgrade

The config.yml on filesystem isn't updated automatically, if plugin updates brings new settings (or removes outdated). But the ingame configuration is always up-to-date and provides you the list of all available setting with the current description. Also you just can use /lc config save once, so that the latest configuration is written to disk, without loosing your defined settings.

Reload

While LC provides a reload command (/lc reload) that should work fine, always consider, that if you have any problems, it is always better to do a full server restart (not a server-reload). This applies to _all_ plugins.