A high-level network interface to simplify multiplayer interactions.
Manages the connection to network peers. Assigns unique IDs to each client connected to the server. See also [MultiplayerAPI]. [b]Note:[/b] The high-level multiplayer API protocol is an implementation detail and isn't meant to be used by non-Godot servers. It may change without notice.
$DOCS_URL/tutorials/networking/high_level_multiplayer.md https://godotengine.org/asset-library/asset/537
Returns the current state of the connection. See [enum ConnectionStatus].
Returns the ID of the [NetworkedMultiplayerPeer] who sent the most recent packet.
Returns the ID of this [NetworkedMultiplayerPeer].
Waits up to 1 second to receive a new network event.
Sets the peer to which packets will be sent. The [code]id[/code] can be one of: [constant TARGET_PEER_BROADCAST] to send to all connected peers, [constant TARGET_PEER_SERVER] to send to the peer acting as server, a valid peer ID to send to that specific peer, a negative peer ID to send to all peers except that one. By default, the target peer is [constant TARGET_PEER_BROADCAST].
- If [code]true[/code], this [NetworkedMultiplayerPeer] refuses new connections.
- The manner in which to send packets to the [code]target_peer[/code]. See [enum TransferMode].
Emitted when a connection attempt fails.
Emitted when a connection attempt succeeds.
Emitted when a remote peer connects.
Emitted when a remote peer has disconnected.
Emitted by clients when the server disconnects.
Packets are not acknowledged, no resend attempts are made for lost packets. Packets may arrive in any order. Potentially faster than [constant TRANSFER_MODE_UNRELIABLE_ORDERED]. Use for non-critical data, and always consider whether the order matters.
Packets are not acknowledged, no resend attempts are made for lost packets. Packets are received in the order they were sent in. Potentially faster than [constant TRANSFER_MODE_RELIABLE]. Use for non-critical data or data that would be outdated if received late due to resend attempt(s) anyway, for example movement and positional data.
Packets must be received and resend attempts should be made until the packets are acknowledged. Packets must be received in the order they were sent in. Most reliable transfer mode, but potentially the slowest due to the overhead. Use for critical data that must be transmitted and arrive in order, for example an ability being triggered or a chat message. Consider carefully if the information really is critical, and use sparingly.
The ongoing connection disconnected.
A connection attempt is ongoing.
The connection attempt succeeded.
Packets are sent to the server and then redistributed to other peers.
Packets are sent to the server alone.