Sara/behaviour-tree-test
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions

Add restrictions to MultiplayerSynchronizer editor and documentation

Browse source
This commit is contained in:
Ninni Pipping 2023-03-04 11:37:02 +01:00
parent dc625bcbfc
commit f69fba0d65
3 changed files with 71 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
modules/multiplayer/doc_classes/MultiplayerSynchronizer.xml
View file

@ -8,6 +8,7 @@
Visibility can be handled directly with [method set_visibility_for] or as-needed with [method add_visibility_filter] and [method update_visibility].
[MultiplayerSpawner]s will handle nodes according to visibility of synchronizers as long as the node at [member root_path] was spawned by one.
Internally, [MultiplayerSynchronizer] uses [method MultiplayerAPI.object_configuration_add] to notify synchronization start passing the [Node] at [member root_path] as the [code]object[/code] and itself as the [code]configuration[/code], and uses [method MultiplayerAPI.object_configuration_remove] to notify synchronization end in a similar way.
[b]Note:[/b] Synchronization is not supported for [Object] type properties, like [Resource]. Properties that are unique to each peer, like the instance IDs of [Object]s (see [method Object.get_instance_id]) or [RID]s, will also not work in synchronization.
</description>
<tutorials>
</tutorials>