Structs
Configuration for a chunk channel, used for sending big and reliable messages,
that are not so frequent, level initialization as an example.
The message is sliced in multiple chunks so it can be sent in multiple frames,
instead of sending all of it in one packet. One message in flight at a time.
A public connect token that the client receives to start connecting to the server.
How the client receives ConnectToken is up to you, could be from a matchmaking
system or from a call to a REST API as an example.
Network informations about a connection.
Configuration for a reliable and ordered channel.
Messages will be received in the order they were sent.
If a message is lost it’ll be resent.
A client that establishes an authenticated connection with a server.
Can send/receive encrypted messages from/to the server.
Configuration for a renet connection and its channels.
A server that can establish authenticated connections with multiple clients.
Can send/receive encrypted messages from/to them.
Configuration options for the renet server.
Configuration for a unreliable and unordered channel.
Messages sent in this channel can be lost and arrive in an different order that they were sent.
Enums
Configuration for the different types of channels.
Possibles errors that can occur in a channel.
Configuration to establishe an secure ou unsecure connection with the server.
Default channels used when using the default configuration.
Use this enum only when using the default channels configuration.
Possibles reasons for a disconnection.
Errors from the renetcode crate.
Enum with possibles errors that can occur.
Configuration to establish a secure or unsecure connection with the server.
Events that can occur in the server.
Constants
The number of bytes in a private key;
The number of bytes that an user data can contain in the ConnectToken.
Functions
Generate a buffer with random bytes using randomness from the operating system.