Fix MultiplayerAPI initialization, clear, set_network_peer. #25010
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
rpc_sender_id
is now correctly initialized to 0 soget_rpc_sender_id()
work reliably even if called before receiving any RPC.root_node
is initialized to NULL (fix crashes when incorrectly using the MultiplayerAPI).clear
function now resets the packet cache size to free more memory when not running.The call to
set_network_peer
is now ignored if the peer that's beeing set is the same as the currently set one:A GDScript call to
multiplayer.network_peer.some_prop = true
seems to transalte to:(@vnen @reduz is that expected?)
Which caused the MultiplayerAPI to be resetted.