RpcManifest

class

csharp

public sealed class RpcManifest

Every remote call this build knows how to make, and nothing else.

No guide page documents this yet — the page shows what the code says about itself.

Remarks

The same closed set ReplicationRegistry is, for the same reason: a packet names a position in this manifest, and a position that is not here is a packet that is refused. Nothing is ever dispatched to a method a packet named.

Types are ordered by their hashed id rather than by when they registered, so two builds of the same game agree on the ordering without having to agree on start-up order — which generated registration across several assemblies cannot promise. Methods within a type are ordered the same way, by the generator, before they get here.

Fields and properties (3)

public int TypeCount
How many types declare calls.
public int MethodCount
How many calls there are, across every type.
public uint ManifestHash
A hash over every id in the manifest, in order: one number that says whether two peers have the same set of calls.

Methods (3)

public void Register(RpcMethod[] methods)
Adds a type's calls.
public int IndexOf(uint typeId)
The position a type has on the wire.
public bool TryGet(uint typeIndex, uint methodIndex, out RpcMethod? method)
Finds the call a pair of wire indices names.

Used by (9)

GameClientMultiplayer
GameServerMultiplayer
RpcMethodsMultiplayer
AwaitableRpcTestsVixen.Net.Tests
RpcGeneratorTestsVixen.Net.Generators.Tests
RpcOverSessionTestsVixen.Net.Tests
RpcRouterVixen.Net
RpcRouterTargetVixen.Net.Fuzz
RpcTestsVixen.Net.Tests