AntiPattern
Context-Specific Runtime Behavior
wrong-context-side-effects
RPC and stateful systems behave differently depending on execution context (host vs client), causing calls like host-only logic or broadcast replication to no-op or desync when invoked from the wrong side. Related components (input routing, Razor updates, save diffs) break when the stored data isn’t owned/resolved for the active context.