Add support for synchronizing custom resources with MultiplayerSynchronizer

[ywmaa]

Describe the project you are working on

a TPS Multiplayer Hero Shooter

Describe the problem or limitation you are having in your project

custom resources can't be added to MultiplayerSynchronizer to be synced automatically

Describe the feature / enhancement and how it helps to overcome the problem or limitation

MultiplayerSynchronizer allows syncing custom resources or resources in general

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

I think the MultiplayerSynchronizer will just convert the resource into Dictionary and vice versa when receiving values.

If this enhancement will not be used often, can it be worked around with a few lines of script?

I need to handle resources sync manually by RPC Calls.

Is there a reason why this should be core and not an add-on in the asset library?

MultiplayerSynchronizer is a core node.

[Calinou]

• Related to Implement sending custom structs as RPC parameters #6216.

[nlupugla]

One issue with sending custom resources (or in fact any Object derived class) is that there is a security risk due to the fact that they can run arbitrary (and potentially malicious) code.

It's not apparent from the PropertySelector UI, but it is possible to sync resource properties by manually typing in their property path, eg: my_resource:my_property. It would be great if the PropertySelector showed these available properties in its UI. Even better, if the dialog supported multi-select or allowed regular expressions to be entered into the text box, it would be quite quick to synch all the relevant properties in a resource.

[ywmaa]

Lol, all I wanted was this

it is possible to sync resource properties by manually typing in their property path, eg: my_resource:my_property

this needs a proper documentation, and needs this :

It would be great if the PropertySelector showed these available properties in its UI.

[ywmaa]

but my proposal may allow using the resource system as Structs (Just like the proposal linked by Calinou)

[puremj]

We need annotations to mark that "this type is simple a simple value struct".

[m21-cerutti]

For me serialisation/deserialisation option would be a good enough solution for this use case. For now, without that solution we can't use MultiplayerSynchronizer for more complex sync.
In order to do that, I suppose it would mean reimplement a custom RPC with timer implementation or send on update mechanism, and that clearly the core principle of MultiplayerSynchronizer.

Maybe we could give an object as option, like a parser into a Dictionnary or PackedBytesArray, or whatever, and that we can set optionally in the UI.

Even adding custom send/receive API in code could do the trick, and at least give one simple possibility to exchange more complex data (even if for performance a custom low level solution could be more appropriate).

Related to
#7435,
#7329,
#7653,
#9510.