SupportContent pending
Debugging
Gathering the information needed to diagnose a problem.
Diagnosing a problem is mostly about narrowing down where it happens: which server, which player, and what the server logged at that moment.
Narrow the scope
- Identify which map or maps show the problem, and which do not.
- Note whether it affects one player, one tribe, or everyone.
- Note when it started, and what changed around then.
Collect the evidence
- Server logs from the affected map, covering the time of the problem.
- On a cluster, logs from both the source and destination map.
- Your plugin configuration, with credentials removed.
- The plugin version each server is running.
Diagnostic tooling not documented yet
Log locations, verbose logging options and any built-in diagnostic commands have not been documented yet.
This page will cover
- Where server and plugin logs are written
- Enabling more detailed logging temporarily
- Any in-game or console diagnostic commands
- Producing a support bundle for a report
Remove credentials first
Configuration files can contain database credentials. Strip them before sharing anything.