From d4c4d2db4cfa64f347c70ca62e141678ff365b6c Mon Sep 17 00:00:00 2001 From: Jummit Date: Mon, 1 Jun 2020 10:34:15 +0200 Subject: add root_node as property of MultiplayerAPI --- doc/classes/MultiplayerAPI.xml | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) (limited to 'doc/classes') diff --git a/doc/classes/MultiplayerAPI.xml b/doc/classes/MultiplayerAPI.xml index 9c753818d9..fcc259fb44 100644 --- a/doc/classes/MultiplayerAPI.xml +++ b/doc/classes/MultiplayerAPI.xml @@ -75,16 +75,6 @@ Sends the given raw [code]bytes[/code] to a specific peer identified by [code]id[/code] (see [method NetworkedMultiplayerPeer.set_target_peer]). Default ID is [code]0[/code], i.e. broadcast to all peers. - - - - - - - Sets the base root node to use for RPCs. Instead of an absolute path, a relative path will be used to find the node upon which the RPC should be executed. - This effectively allows to have different branches of the scene tree to be managed by different MultiplayerAPI, allowing for example to run both client and server in the same scene. - - @@ -97,6 +87,10 @@ If [code]true[/code], the MultiplayerAPI's [member network_peer] refuses new incoming connections. + + The root node to use for RPCs. Instead of an absolute path, a relative path will be used to find the node upon which the RPC should be executed. + This effectively allows to have different branches of the scene tree to be managed by different MultiplayerAPI, allowing for example to run both client and server in the same scene. + -- cgit v1.2.3