Skip to content
Anomaly

Runtime Paths and User Data Locations

Intended scope

Section titled “Intended scope”
  • Top-level root:
    • Windows: %APPDATA%\Anomaly\
    • Linux: ~/.config/Anomaly/ (exact path pending confirmation in code)
  • Subdirectories:
    • <root>/identity/ — ECDSA keypair and derived public @anomaly id.
    • <root>/FileCache/ — manifest + content-hash-keyed chunk store shared across servers.
    • <root>/<modId>/config.json — per-mod ClientConfig.
    • <root>/<modId>/data.json — per-mod ClientPersistence.
    • <root>/bindings.json — user input rebinds via InputRegistry.
    • <root>/logs/ — Launcher and session logs.
  • Safe-to-delete vs not-safe-to-delete table.

Sources

Section titled “Sources”
  • Anomaly.Client.Api\Config\ClientConfig.cs, Persistence\ClientPersistence.cs.
  • Anomaly.Client.Api\FileTransfer\FileCache.cs.
  • Anomaly.Client.Api\Input\InputRegistry.cs.
  • Anomaly.Launcher\Services\PathService.cs.