@rpc function saying the input variable is the incorrect type, when it is correct . | Godot Engine | Page 1

tidal sorrel Apr 3, 2026, 3:44 AM

#

I have a script that is supposed to load a weapon scene as a child for the player. The function load_weapon() takes a resource containing the weapon scene and position information and uses it to create the child node containing the weapon. The resource class is pweaponres, which is forced by the function input.

When load_weapon() is called to swap weapons in game (loading during _ready() is fine), the peer swapping weapons works fine, but their opponent gets the error "cannot convert function from object to object" and the new weapon does not load. Both the function input and variable declaration are forced to have the class pweaponres, so I'm not sure what the problem is.

Also, when I change load_weapon() to accept any variable type, the client crashes when they connect. The client's error is (Error: E 0:00:07:317 pweaponrig.load_weapon: Invalid access to property or key 'SCENE' on a base object of type 'EncodedObjectAsID'.<GDScript Source>pweaponrig.gd:26 @ pweaponrig.load_weapon() <Stack Trace> pweaponrig.gd:26 @ load_weapon())

Does anyone know what the problem is?

script is attached below

#

📎 pweaponrig.gd

#

📎 pweaponrig.txt

unique night Apr 3, 2026, 4:00 AM

#

I don't think passing resources as arguments over RPC really works (or at least not the way you expect it to). Hence the error you are seeing ( Invalid access to property or key 'SCENE' on a base object of type 'EncodedObjectAsID'.). You aren't getting a resource on your receiver, you're getting EncodedObjectAsID. It seems like maybe you could load the resource from this, but there are better ways.

Instead, you should send an ID or Enum of some sort to designate which weapon you are switching to, and then just load the weapon on the client (rather than expecting the full resource). Does that make sense?

limpid sorrel Apr 3, 2026, 1:03 PM

#

tidal sorrel I have a script that is supposed to load a weapon scene as a child for the playe...

You can't send objects through rpc, only data that can be serialized.
Easiest way imo is to send the resource_path of your resource, assuming it's the same on all clients and not created dynamically. Then load the resource from that path on the other side to get the object.

tidal sorrel Apr 3, 2026, 10:14 PM

#

Thank you guys!

#

I'll try sending the resource path instead, and set up a weapon id system at a later date

tidal sorrel Apr 3, 2026, 11:26 PM

#

HOLY SHIT IT WORKS

#@rpc function saying the input variable is the incorrect type, when it is correct .