Currently target context is passed to steps at compile time through the StepFunc's target field, which gives a static index. This can't work for clones unless we were to duplicate every step 300 times for each sprite that can be cloned, and then make sure the right step is called for the right clone.
Probably best to store clone index in a step parameter or in the struct parameter? (but only for steps that might be cloned)
Target data can just be stored as normal, but with an extra field to indicate which sprite is occupying a particular clone slot? But also, will need some sort of GC for clones (if only an array keeping track of free slots) so things can't balloon out of control.
Currently target context is passed to steps at compile time through the
StepFunc's target field, which gives a static index. This can't work for clones unless we were to duplicate every step 300 times for each sprite that can be cloned, and then make sure the right step is called for the right clone.Probably best to store clone index in a step parameter or in the struct parameter? (but only for steps that might be cloned)
Target data can just be stored as normal, but with an extra field to indicate which sprite is occupying a particular clone slot? But also, will need some sort of GC for clones (if only an array keeping track of free slots) so things can't balloon out of control.