I was wondering why can’t we chase elements from arrays, it would be so Awesome to have that option, the “technical” amount of variables we could do would go through the roof! I needed this to make a lot of moving effects that behave in a different way without spending a tone of variables. Pls devs add this!
Until they do, if they do, you can use the Modify Player Variable at Index with subtract 0.1, min, max, or whatever from it and loop once a variable != NULL 
Often you can get away without an extra chase variable by using a single global.
Ongoing Global, No condition,
Set T = 0
Chase T to 9999 at rate 1
Say you want to create a ball moving from A to B during 10 seconds.
Set B0 to A
Set B1 to B
Set B2 to global.T “this is start time”
Set B3 to 10 + global.T “this is endtime”
Create ball effect(
…
Position = B0 + (B1 - B0) * (global.T - B2) / (B3 - B2)
)
Set B4 to Last create effect
Wait(B3 - B2)
Destroy effect (B4)
Nice! There’s also a “Time Elapsed” variable for the match that can be used this way, that way you can avoid using up a variable for a chase.
I dont think you can use time elapsed as a ‘dynamic’ value in a position expression though.
Total Time Elapsed is the amount of time the mode has been running for on the map, not the individual match time. It’s always ticking away, unlike Match Time. Why wouldn’t it work?
Because I tried it and it didnt work.
This was like weeks ago though - so should test it again now.
When I say it didnt work I mean it didnt work as the time variable in a position expression for several moving spheres.
When I used a global chase variable for time it did work.
Made a demo that shows Total Time Elapsed does not work as a dynamic position argument.
Code: DHDY4
The balls rotates when using Global.T but not when using Total Time Elapsed.
“Chase variable in array” action is what I (or maybe all we) need.
This makes possible or easy that each of variables in array keeps changing apart.
If not, we have to use variables of different characters and repeat similar scripts with manual input.
Though it’s not clear now, if the action syntax comes,
we will probably have a problem with it.
The problem is caused by that a variable as index is always reevaluated on every value-changing time like formula of effect’s position.
Once index variable is changed in for loop, all index variable in array may change together.
If there’s new value syntax that evaluate a value only once, this problem is solved.