Skip to content
Anomaly

Asset Distribution and Late-Join Behaviour

Intended scope

Section titled “Intended scope”
  • What goes in AssetDirectory — textures, bundles, overrides; filename-to-hash mapping.
  • Manifest generation — ServerAssetManager walks the directory at startup, hashes each file, publishes to FileManifestMessage.
  • Delivery — FileTransferSession streams FileChunkMessage payloads; client ACKs with FileTransferCompleteMessage.
  • Late joiners — manifest is pushed on connect regardless of round phase; in-flight chunks resume mid-round without interrupting gameplay.
  • Override workflow — per-round or per-player asset swaps via AssetOverrides.
  • Hot reloading — AssetFileWatcher picks up file changes; what clients see mid-session.

Sources

Section titled “Sources”
  • Anomaly.Server\FileTransfer\ServerAssetManager.cs — manifest build.
  • Anomaly.Server\FileTransfer\FileTransferSession.cs — chunk loop.
  • Anomaly.Server\Assets\AssetOverrides.cs and AssetFileWatcher.cs.
  • Reference → Asset Lifecycle.