coherence-rpc-routing

Pick MessageTarget based on who must run the command: StateAuthorityOnly when a client asks the authority to act, Other when the authority broadcasts to remote viewers, All when everyone including the sender runs it, and InputAuthorityOnly for the controlling player.

Use SendOrderedCommand for race-sensitive events and paired commands that mutate the same state, such as apply/remove or lock/unlock, so they arrive in send order. Use plain SendCommand for droppable visual effects like footstep dust or muzzle flashes.

Use SendCommandOverChannel with Channel.Fragmented for one-shot payloads above the ~1200 byte MTU, or Channel.FragmentedOrdered when multiple fragmented sends must arrive in send order. Reassembly of each payload is handled automatically.

Coherence infers the wire type from the runtime type of each argument, and a bare null carries no type. Pass nullable string, byte[], or entity-reference arguments as (typeof(T), value) tuples, and wrap every argument in the call once one uses the tuple form.

MessageTarget.All includes the sender, so local code runs twice if you also apply the effect before sending. Use MessageTarget.Other for broadcasts and invoke the local effect explicitly, or make the command idempotent.

Use a [Sync] bool or enum whenever the state is just a value, because state replication self-heals on reconnect and converges by construction. Reserve paired ordered commands for transitions where receivers mutate derived state, such as reference counts or lifecycle locks.