Skip to main content
Version: 0.3.1

ReadyM.Api.Multiplayer

Namespaces​

ReadyM.Api.Multiplayer.Generators

ReadyM.Api.Multiplayer.Protocol

ReadyM.Api.Multiplayer.RPC

Classes​

ClientToServerAttribute

Client-to-server (request) leg of a contract method: generates a Send on the client and an On(RpcContext, ...) handler on the server. Different-shaped two-way RPCs are two overloads (one per direction); identical-shape two-way is one method with both attributes. Every contract method needs at least one direction attribute.

ServerRpcForAttribute

Binds an RPC class (server ServerRpcHandlersBase, client ServerRpcClient) to the ServerRpcContractsAttribute class it implements, and is required on both. A project may reference several contract sets, directly or transitively; this is what tells the generator which one to emit against. Only the legs declared by the named class are generated, so one contract set per RPC class.

ServerToClientAttribute

Server-to-client (response/push) leg of a contract method: generates a Send(PlayerId, ...) on the server and an On(...) handler on the client. See ClientToServerAttribute.