Merge pull request #60711 from nathanfranke/rpc-server
network - finish renaming AUTH to AUTHORITY
This commit is contained in:
commit
70c2b4bebd
|
@ -645,7 +645,7 @@ void register_global_constants() {
|
|||
// rpc
|
||||
BIND_CORE_ENUM_CONSTANT_CUSTOM("RPC_MODE_DISABLED", Multiplayer::RPC_MODE_DISABLED);
|
||||
BIND_CORE_ENUM_CONSTANT_CUSTOM("RPC_MODE_ANY_PEER", Multiplayer::RPC_MODE_ANY_PEER);
|
||||
BIND_CORE_ENUM_CONSTANT_CUSTOM("RPC_MODE_AUTH", Multiplayer::RPC_MODE_AUTHORITY);
|
||||
BIND_CORE_ENUM_CONSTANT_CUSTOM("RPC_MODE_AUTHORITY", Multiplayer::RPC_MODE_AUTHORITY);
|
||||
|
||||
BIND_CORE_ENUM_CONSTANT_CUSTOM("TRANSFER_MODE_UNRELIABLE", Multiplayer::TRANSFER_MODE_UNRELIABLE);
|
||||
BIND_CORE_ENUM_CONSTANT_CUSTOM("TRANSFER_MODE_UNRELIABLE_ORDERED", Multiplayer::TRANSFER_MODE_UNRELIABLE_ORDERED);
|
||||
|
|
|
@ -46,7 +46,7 @@ enum TransferMode {
|
|||
enum RPCMode {
|
||||
RPC_MODE_DISABLED, // No rpc for this method, calls to this will be blocked (default)
|
||||
RPC_MODE_ANY_PEER, // Any peer can call this RPC
|
||||
RPC_MODE_AUTHORITY, // / Only the node's multiplayer authority (server by default) can call this RPC
|
||||
RPC_MODE_AUTHORITY, // Only the node's multiplayer authority (server by default) can call this RPC
|
||||
};
|
||||
|
||||
struct RPCConfig {
|
||||
|
|
|
@ -2640,8 +2640,8 @@
|
|||
<constant name="RPC_MODE_ANY_PEER" value="1" enum="RPCMode">
|
||||
Used with [method Node.rpc_config] to set a method to be callable remotely by any peer. Analogous to the [code]@rpc(any)[/code] annotation. Calls are accepted from all remote peers, no matter if they are node's authority or not.
|
||||
</constant>
|
||||
<constant name="RPC_MODE_AUTH" value="2" enum="RPCMode">
|
||||
Used with [method Node.rpc_config] to set a method to be callable remotely only by the current multiplayer authority (which is the server by default). Analogous to the [code]@rpc(auth)[/code] annotation. See [method Node.set_multiplayer_authority].
|
||||
<constant name="RPC_MODE_AUTHORITY" value="2" enum="RPCMode">
|
||||
Used with [method Node.rpc_config] to set a method to be callable remotely only by the current multiplayer authority (which is the server by default). Analogous to the [code]@rpc(authority)[/code] annotation. See [method Node.set_multiplayer_authority].
|
||||
</constant>
|
||||
<constant name="TRANSFER_MODE_UNRELIABLE" value="0" enum="TransferMode">
|
||||
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.
|
||||
|
|
|
@ -637,7 +637,7 @@
|
|||
<argument index="3" name="transfer_mode" type="int" enum="TransferMode" default="2" />
|
||||
<argument index="4" name="channel" type="int" default="0" />
|
||||
<description>
|
||||
Changes the RPC mode for the given [code]method[/code] to the given [code]rpc_mode[/code], optionally specifying the [code]transfer_mode[/code] and [code]channel[/code] (on supported peers). See [enum RPCMode] and [enum TransferMode]. An alternative is annotating methods and properties with the corresponding annotation ([code]@rpc(any)[/code], [code]@rpc(auth)[/code]). By default, methods are not exposed to networking (and RPCs).
|
||||
Changes the RPC mode for the given [code]method[/code] to the given [code]rpc_mode[/code], optionally specifying the [code]transfer_mode[/code] and [code]channel[/code] (on supported peers). See [enum RPCMode] and [enum TransferMode]. An alternative is annotating methods and properties with the corresponding annotation ([code]@rpc(any)[/code], [code]@rpc(authority)[/code]). By default, methods are not exposed to networking (and RPCs).
|
||||
</description>
|
||||
</method>
|
||||
<method name="rpc_id" qualifiers="vararg">
|
||||
|
|
Loading…
Reference in New Issue