Player Drops: investigate disconnects
Use txAdmin's player-disconnect timeline and drilldowns to diagnose crashes, kicks and recent changes.
The Player Drops page categorizes disconnects observed by txAdmin. It combines a timeline with drilldowns for crashes, resource kicks, and changes to versions or resources. These categories are diagnostic hints, not definitive root causes.
1. Select the affected period
Open Player Drops in your authenticated txAdmin panel. The upstream implementation shows a 14-day summary timeline. The detail window defaults to the last seven days in hourly mode and 14 days in daily mode. You can select a specific time range.
Record the date, timezone, approximate player count and whether the incident began suddenly.
2. Compare the breakdowns
Look at Overview, Crashes, Changes, and Resource Kicks, where applicable.
| Pattern | Investigation |
|---|---|
| A spike after a resource update | Inspect that resource's first console error and its dependencies |
| Many resource kicks | Identify the kicking resource and its server-side logic |
| Crash category concentrated around one period | Compare client crash reports and FXServer version |
| Drops around a scheduled restart | Compare the restart schedule and shutdown warning log |
| Only a subset of players affected | Collect client version, network symptoms and exact error |
3. Verify a suspected cause
Cross-reference Live Console and logs for the same period. Change one variable at a time in staging, preferably with a known-good comparison. A falling drop count under a different player load is not conclusive evidence of a fix.
4. Record the outcome
Save the precise time, versions, resource changes, test steps and whether the same drop category recurs under comparable conditions.
Related: Dashboard, Diagnostics, Crash loops.
Sources: Player Drops panel, data endpoint.