Configuration

Last modified: 26 April 2026

Safe baseline

Most servers should run the default generated config with a production profile and private alerts. Do not publish your full config publicly if it contains webhook URLs, support endpoints, private notes, or tuned enforcement values.

profile: balanced

alerts:
  enabled: true

packetLogger:
  enabled: false

Public sections

Area	What admins should know
Profiles	Controls rollout, production, and temporary high-response posture.
Alerts	Controls staff visibility and optional Discord notifications.
Evidence	Controls how incidents are kept for local review and private support.
Logging	Should stay off unless debugging. Logs can become sensitive and noisy.
Integrations	Only enable support for integrations you actually use.

Alerts

Use alerts for staff visibility. A webhook URL is private infrastructure; do not paste it in public channels or screenshots.

Logging

Packet or debug logging is not a normal operating mode. Enable it only for a short support session, reproduce the issue, then disable it again.

Safe tuning

Switch to observe.
Reproduce the normal player action.
Review the incident summary and affected integration.
Change the smallest relevant public setting.
Return to balanced and watch live traffic.

Do not disable broad protection areas just to silence one report. That hides useful signal and makes support harder.

Reloads

/eps reload

Use a full proxy restart after dependency updates, platform updates, or anything that changes plugin load order.