This guide focuses on practical setup and safe operations. Keep changes small, test often, and roll out in steps.
- Main settings:
plugins/ServerFeatures/config.yml - Feature-local files:
plugins/ServerFeatures/local/*.yml - Localization files:
plugins/ServerFeatures/lang/*.yml
config.yml is generated at runtime and primarily controls feature enablement and feature-level settings.
Most features follow the same pattern:
enabledtoggle- feature-specific settings under that feature section
Use these commands during operations:
/serverfeatures list/serverfeatures info <feature>/serverfeatures enable <feature>/serverfeatures disable <feature>/serverfeatures reload <feature>/serverfeatures softreload <feature>/serverfeatures reloadlocal
- Enable only the features you currently need.
- Roll out one feature (or one related group) at a time.
- Validate logs and in-game behavior.
- Move to the next feature only after verification.
This keeps incidents small and rollback simple.
Treat production tokens, webhooks, and credentials as environment-specific values:
- keep secrets out of committed files;
- use your secret-management workflow;
- document expected variables for your team.
You can override messages without copying all language keys.
Use partial language files with only the entries you want to customize. Missing keys fall back to defaults.
- If a feature does not enable, verify plugin dependencies and feature dependencies first.
- If a setting seems ignored, check path names and indentation.
- Apply one change at a time when diagnosing configuration behavior.