Troubleshoot Configuration Changes

The reload command refreshes shared configuration, check runtime configurations, menus, hooks, and optional services. Some settings may require a restart.

When to use this guide

Use these steps when a saved configuration change does not appear to affect the server.

What reload refreshes

The /fairplay reload command requires fairplay.command.reload. It refreshes shared configuration, per-check runtime configurations, menus, hooks, and optional services. It also starts or stops webhook handling based on the updated setting; reload does not confirm Discord delivery.

Per-check settings apply on reload only when that check reads them through its runtime configuration reload path.

Diagnostic sequence

  1. Confirm the operator has fairplay.command.reload and the root fairplay.command permission, then run /fairplay reload.
  2. Confirm the edited file is the one the server reads. Use the generated YAML and its comments to check key spelling.
  3. Check the setting’s guide to learn whether it applies on reload or needs a restart.
  4. Re-test in a controlled session and record the changed setting and result.

Restart boundary

Some settings require a restart. If the setting guide does not specify when it applies, restart the server after backing up the configuration and check the startup output. See the [configuration reload guide](/articles/fairplay-configuration-reload-behavior) for more detail.

Browse all documentation