Reload FairPlay Configuration

Reload is a lifecycle operation

FairPlay provides a /fp reload subcommand for reloading configuration. Some changes, such as replacing installed machine-learning models, are handled during startup and may require a server restart.

Per-check runtime configuration also has check-specific reload behavior. The relevant owner is FairCheck.reloadRuntimeConfig, not a generic assumption that editing YAML immediately changes every running component. The command implementation calls the configuration manager for all registered configs; after a successful reload it reloads check runtime configs, menus, external hooks, and reconciles optional services. A reload failure returns before those success-path steps.

/fp reload

Separate configuration reload from model updates

The MainConfig.auto-update-models setting controls replacing installed machine-learning models with bundled models on startup. Reloading configuration does not train a model.

Before applying a change, inspect the exact class and lifecycle path that owns the field. If a subsystem only reads configuration during initialization, follow the release’s documented restart requirements rather than guessing.

Operational boundary

Back up the files you change and check the server console after reloading. If the new values do not take effect, restart the server and review the first startup error.