Worker
AuthorityCallOutcome
Where an AuthorityRpc call ended up.
generated from the sources
Enum in namespace
Nebula · Packages/com.1by3.nebula/Runtime/Worker/AuthorityCallContract.cspublic enum AuthorityCallOutcome : byteWhere an AuthorityRpc call ended up. A caller that asked for a reply (NetworkBehaviour.AuthorityRpcWithReply) receives exactly one of these; a fire-and-forget call is decided by the same rules and only logs a rejection on the worker that made it. See the design in docs/cross-worker-calls.md.
Members
| Name | Value | Description |
|---|---|---|
Pending | 0 | Not decided yet. Never sent on the wire. |
Accepted | 1 | The worker with authority ran the method once. The handler may still have thrown or refused the claim. |
RejectedStaleEpoch | 2 | The call's entity epoch was more than NebulaConfig.AuthorityCallMaxHops authority changes behind the entity, or ahead of it: the caller's copy was not the entity the authority holds. |
RejectedUnknownEntity | 3 | No worker on the call's path holds the entity: it was despawned, or never existed there. |
RejectedHopLimit | 4 | The call was forwarded NebulaConfig.AuthorityCallMaxHops times without reaching the authority. |
RejectedDuplicate | 5 | A call with this id was already applied on this worker. At-most-once held; nothing ran a second time. |
RejectedUnreachable | 6 | The worker that should apply or forward the call has no connection to the entity's owner. |
TimedOut | 7 | No reply arrived before the caller's deadline. The call may or may not have been applied. |