Main Configuration
Use config.yml to manage FairPlay alerts, player logs, check controls, model settings, and diagnostics.
What this file controls
config.yml groups Bedrock eligibility, cancellation messages, model updates, player logs, alerts, checks, confirmation handling, and diagnostics. Player logs can contain violations, chat, joins, and leaves; restrict access and redact them before sharing.
Machine-learning optimization settings are for training. The confirmation setting is a synchronization kill switch, not a general check toggle.
Diagnostic switches can produce high-volume output. Enable them for a bounded investigation and review the output before sharing it.
Review main policy one area at a time
- Back up the generated file, then confirm which policy area the change belongs to: Bedrock eligibility (
bedrockCheck=true), cancellation feedback (showCancelMessages=false), model updates (autoUpdateModels=true), player logs, alerts, checks/whitelist, confirmation kill switch, or diagnostics. - Read the comments beside the setting and keep training-only machine-learning options separate from runtime detection controls.
- Limit access to player logs; redact violations, chat, joins, and leaves before sharing them.
- Record which setting changed so staff can diagnose the result later.
Apply and verify changes
After editing a setting, use the reload command when that setting supports reload. If the change does not take effect, check the configuration troubleshooting guide for the setting’s restart requirements.