NetSpawning Bullets

[croxis]

I've got relatively slow paced and long life bullets (plasma bolts to be specific -- pew pew!) for my game, so I'm using the network addon for it.
Just to make sure I'm designing this somewhat sane -- I should have only one spawner for each type of bullets; not a unique spawner on each gun.

The problem I am running into is the following error on the client:
W 0:00:22.948 call: Could not retrieve spawner for entity SnapBolt with unique ID 3419678593.
<C++ Source> modules/gdscript/gdscript_functions.cpp:817 @ call()
entityinfo.gd:456 @ spawn_node()
snapshotdata.gd:561 @ client_check_snapshot()
network.gd:905 @ _handle_snapshot()
network.gd:935 @ _client_receive_delta_snapshot()

However I am following the same patterns as the player spawning (which does work), other than using a a chash.

[Kehom]

Just to make sure about things, did you disable the class hash within the SnapBolt script, In its _init()?
Something like this:

func _init(uit: int, h: int).(uid, h) -> void:
   set_meta("class_hash", 0)

Another thing, when you registered the spawner for type of entity, which value did you set for the class hash? When it's not in use usually it's a good idea to pass in 0.

Those are the two possible sources that I can think of. If both are correct then it's possible there is some bug within the system.

[croxis]

Part of my problem is that I am still unsure what the class_hash is for and the contexts to use it in. I've read over this a few times now but class_hashes are not clicking for me yet. It allows different scenes to be used with the same SnapClass?

[Kehom]

Well, class_hash is actually a poor name I have chosen. "class_id" or something like that would have been a lot better. Nevertheless, yes, it is a way to allow the exact same SnapClass to handle multiple different scenes. When you are sure your snap class will handle just one single type of object then you can completely go away with the class hash.
I have named it like that because I normally take the resource path of the scene and hash it (String.hash()). Again, it's a poor name but when I realized that it was a bit too late to change!

[Kehom]

I have no idea how I didn't see that property! Anyway, one thing you can do is update the warning message within the entityinfo.gd script so it also shows the class hash number (I will do it soon anyways because it will greatly help debug things). Compare if the number it is requesting matches the actual hash value. If it does not then there is a bug with the addon and I will have to investigate it.

[croxis]

the chash parameter in spawn_node is = 0!

[Kehom]

Ohhh my! I think I have found the problem. I completely forgot to ask/check how you were generating the SnapBolt object. In your code (bolt.gd) you are creating it with a zeroed class hash:

var snap: SnapBolt = SnapBolt.new(_uid, 0)

However you registered the spawner for this bolt with a class hash. So instead you have to generate it like this:

var snap: SnapBolt = SnapBolt.new(_uid, hashcache.bolt)

The thing is, you are using the class hash for this kind of entity!

I'm 90% sure this will fix the problem.

[croxis]

That fixed it! Thank you again for the help!

[Kehom]

Glad to help!