You’re welcome in advance everyone .
If you need any help with the code feel free to ask and I’ll help
(The Random behavior can be replaced with a thing that gets the numbers in your Object Name, but the problem with that is that you can’t name your objects)
When I say you can't name your objects for the second method this is what I mean
Sure you could do that, also happy to help.
Another thing, the random behavior could probably be replaced with some sort of global so it guarantees a new value each time but I didn’t have the time to bother figuring it out.
This doesn’t help for sending messages from multiple of the same type to spawned objects of multiple of the same type. I tried this before with another system and had messages miss mailboxes for sending thousands of messages each frame.
Just only one spawner, having more than one spawner will be sending to several objects with the same ID. And this doesn’t seperate different spawn objects types.
So it won’t register the value being sent because it’s receiving multiple at once. That makes sense, but it should be fine for around 30 objects (An object can output around 30 times a frame I think), right?
What do you mean by this? Each object has a unique object ID.
I’m great at coding, but I’m not sure what you’re saying. Can you phrase it differently?
But the purpose is to message to ALL spawned objects. That’s mostly an excuse for my mind blanking. I’ll make a version for the last spawn object as well.
To send data to the object just send a second message with the data. (In the screenshot on the top there is a Number behavior in the spawned object, set it to the data you wanted you send to the object at the time)
Overall, an ID message system is not a bad idea and can work in many cases.
Just a complex structure with many different spawn types and spawners may get difficult.
And having too many messages being sent in a single frame may lose messages.
It’s a great method, just not the end all solutions for messaging spawned objects.