When you spawn an object in godot, it assigns it a name in a reasonably predictable fashion, meaning that if you spawn a bunch of objects on a server and a client, randomise their positions, then tell them to sync, you will end up with the expected amount of objects for the code running once.
Next trick is to only run the spawn code on the server and use a multiplayerspawner to guarantee this, instead of having it one day blow up in my face when it happened to allocate names differently.
Zergling_man /
npub140…vsu0k
2024-09-17 10:33:34
Author Public Key
npub140w8qr2g3ycwf5chj4y5g26j7k2df476pvm9c080cm8anz2uyc6savsu0kSeen on
wss://relay.mostr.pubPublished at
2024-09-17 10:33:34Event JSON
{
"id": "65fe676a308cc8ab25fe02c5797ac3b618cdbc38f1985c206ef37e91cf96b4db",
"pubkey": "abdc700d488930e4d3179549442b52f594d4d7da0b365c3cefc6cfd9895c2635",
"created_at": 1726569214,
"kind": 1,
"tags": [
[
"proxy",
"https://sacred.harpy.faith/objects/053535ef-3ac2-47d8-914b-cbbcd65ecc9a",
"activitypub"
]
],
"content": "When you spawn an object in godot, it assigns it a name in a reasonably predictable fashion, meaning that if you spawn a bunch of objects on a server and a client, randomise their positions, then tell them to sync, you will end up with the expected amount of objects for the code running once.\nNext trick is to only run the spawn code on the server and use a multiplayerspawner to guarantee this, instead of having it one day blow up in my face when it happened to allocate names differently.",
"sig": "0235d0928c490bec7e76dbc347f516daf2a00227e968a4619d506c765527a31f44882483c3f379110f49bcb46efae924c57fac089e946dc471f966f440555694"
}