Extensions and Best Practices

• Keep mutations on authority and route client intent through an owned project Server RPC.
• Activate components explicitly and avoid activation/reset as a HUD refresh.
• Treat update amounts as per-pulse values; coordinate timer cadence with balance.
• Use component interface queries and replicated tags for UI; read an initial snapshot and rebind after respawn.
• Use exact native tag strings and explicit source maps; a new tag does not implement a simulation rule.
• Avoid overlapping mappings to the same affect until source ownership/reference counting is handled.
• Keep shared settings as configuration and implement SaveGame/state persistence separately.
• Add Oxygen/Radiation or other stats as project components with their own state, interface, replication and scheduling. The current manager has four fixed destination families and does not discover a fifth one automatically.

For Blueprint children, preserve numerical authority checks and lifecycle behavior. An interface alone does not supply server transport, permissions or registration in CrossAffectManager. See Extensibility.

---