From 44c1531f6e5618bc4cf1e9f321a29050a3087eb4 Mon Sep 17 00:00:00 2001 From: Martin Capitanio Date: Thu, 30 Nov 2017 12:39:48 +0100 Subject: [PATCH] Clean up 93d3009 References do not work in the code blocks, a simple paragraph is much easier to read anyway. --- .../features/networking/high_level_multiplayer.rst | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/learning/features/networking/high_level_multiplayer.rst b/learning/features/networking/high_level_multiplayer.rst index f900cc291..8d5002120 100644 --- a/learning/features/networking/high_level_multiplayer.rst +++ b/learning/features/networking/high_level_multiplayer.rst @@ -4,7 +4,7 @@ High level multiplayer ====================== High level vs low level API ----------------- +--------------------------- Godot always supported standard low-level networking via UDP, TCP and some higher level protocols such as SSL and HTTP. These protocols are flexible and can be used for (almost) anything. However for games (unless you are working @@ -290,7 +290,7 @@ every peer and RPC will work great! Here is an example: to be deferred via ``call_deferred()`` as the SceneTree is locked while the scene is being created (e.g. when ``_ready()`` is being called). Synchronizing game start -^^^^^^^^^^^^^^^^^^^^^^^ +^^^^^^^^^^^^^^^^^^^^^^^^ Setting up players might take different amount of time on every peer due to lag, different hardware, or other reasons. To make sure the game will actually start when everyone is ready, pausing the game until all players are ready can be very useful: @@ -337,13 +337,7 @@ When not explicitly set the network master is inherited from the parent node, wh The network master can be set with the function :ref:`Node.set_network_master(id, recursive) ` (recursive is true by default and means the network master is recursively set on all child nodes of the node as well). -Checking that a specific node instance on a peer is the network master for this node for all connected peers is done by calling: - -:: - - :ref:`Node.is_network_master() ` - -This will by default return true when executed on the server and false on all client peers. +Checking that a specific node instance on a peer is the network master for this node for all connected peers is done by calling :ref:`Node.is_network_master() `. This will return true when executed on the server and false on all client peers. If you have paid attention to the previous example, it's possible you noticed that the local peer is set to have network master authority for their own player instead of the server: @@ -416,4 +410,4 @@ This may not make much sense for an area-of-effect case like the bomb but in oth :: - rpc_id(TARGET_PEER_ID, "stun") # Only stun the target peer \ No newline at end of file + rpc_id(TARGET_PEER_ID, "stun") # Only stun the target peer