Skip to content
Anomaly

Troubleshooting and Known Limitations

Intended scope

Section titled “Intended scope”
  • Turning on AuthAndRoleDiag — what extra logging it produces and how to read it.
  • OffThreadLogger behaviour — why messages sometimes appear out of chronological order vs LabAPI’s stock logger.
  • DefaultChunkSize tuning — tradeoffs between head-of-line blocking, late-join catch-up time, and bandwidth.
  • Round-start issues — known sequence-sensitive bugs and the order of events admins can rely on.
  • Message-registry hash collisions — what the startup warning looks like and what to do.
  • Where server logs and crash reports land.

Sources

Section titled “Sources”
  • Anomaly.Server\Diagnostics\AuthAndRoleDiag.cs.
  • Anomaly.Server\FileTransfer\ — chunk tuning.
  • Anomaly.Shared\Networking\AnomalyMessageRegistry.cs — collision detection at startup.