Capture the useful context
- Record the game, server type and exact version.
- Note what changed immediately before the failure.
- Open the latest console/crash log and find the first relevant error around the failure.
- Check whether memory, disk or CPU pressure was visible near the incident.
- Record the latest successful backup before attempting a destructive repair.
Common patterns
Version mismatch errors often point to an incompatible plugin, mod, loader or runtime. Missing dependency errors usually identify another package the failing component expects. Out-of-memory failures should be separated from CPU stalls or infinite restart loops.
A later stack trace can be a symptom of the first error, so start near the beginning of the failure rather than copying thousands of unrelated log lines.
When opening support
Attach only the relevant excerpt and describe what changed. Runic’s diagnostic-bundle design adds game/version, allocation, recent resource context, package information, recent changes and backup status after customer authorization, with secrets removed before analysis.