Alt-account detection: RPT evidence and limits
An experimental detector using DayZ's login-mitigation waits, not behavioral profiling.
The implemented signal
Alt Account Detection uses prolonged DBWaitLoginTimeLoginState waits in the DayZ RPT log. It requires usable RPT evidence and DayZ multi-account mitigation to be active. It does not infer shared devices from base proximity, loadouts, play schedules, economy transfers, or Discord voice-channel co-presence.
- The account released from the prolonged login wait is the detection target
- DayZ mitigation records or a unique recent stable-ID disconnect can provide suspected account associations
- Associations are server-scoped investigation context, not proof of a shared physical device
How to act on a flag
The experimental detector defaults off and uses alert-only behavior unless an owner explicitly enables enforcement. Review the wait evidence, prerequisites, and suspected associations before acting. Automatic enforcement requires a qualifying direct DayZ mitigation pair as well as the configured enforcement rules; a timer-only or sequential-disconnect signal is not enough. Enforcement targets the delayed account rather than automatically banning associated accounts. A prerequisite repair can require a server restart before it takes effect; there is no promised investigation time.