This guide focuses on practical setup and safe operations. Keep changes small, test often, and roll out in steps.
- Main settings:
config.yml - Optional feature-local files:
local/*.yml - Language overrides:
lang/*.ymlin the runtime plugin directory
Most features follow the same pattern:
enabledtoggle- feature-specific settings under that feature section
- Start with only the features you actively need.
- Enable one feature (or one group) at a time.
- Restart or reload based on your normal operations process.
- Confirm behavior in logs and in-game.
- Move to the next feature only after validation.
This keeps incidents small and rollback simple.
Treat production endpoints, tokens, and credentials as environment-specific values:
- keep secrets out of committed files;
- prefer environment variables or your secret-management workflow;
- document expected variables for your team.
You can override messages without copying every key.
Use partial language files with only the entries you want to customize. Missing entries automatically fall back to the default message set.
- If a feature is not active, verify it is enabled and dependencies are available.
- If a setting seems ignored, check key names/indentation first.
- Apply one change at a time when debugging configuration issues.