[State x, VarSet]
trigger1 = NumHelper(x)-1 >= 1
var(0) = ifElse(NumHelper(x)-1 == 1, Parent, Pos X, Parent, Var(0))
[State x, VarSet]
trigger1 = NumHelper(x)-1 >= 2
var(1) = ifElse(NumHelper(x)-1 == 2, Parent, Pos X, Parent, Var(1))
[State x, VarSet]
trigger1 = NumHelper(x)-1 >= 3
var(2) = ifElse(NumHelper(x)-1 == 3, Parent, Pos X, Parent, Var(2))
;... do this for the other 57 variables

[State x, VarSet]
type = VarSet
trigger1 = 1
v = NumHelper(x)-1
value = Parent, Pos X
; ... other similar variables you need to store in the same way to retrieve positions

Lets say theres an invisible helper named ballmaker2000; its created when the match starts and always exists. Whenever the character performs the move that shoots a ball projectile, ballmaker2000 does the actual work: it creates each helper projectile, and the root never has to waste any variables to keep track of anything.

Ballmaker2000 has 7 variables of its own. The first is a count of how many active energy balls are out (max of 3); if this variable is less than 3 then the root can perform the ball summon move. The other six variables are the x and y positions of the three balls. Whenever a new ball is created, ballmaker2000 starts tracking its position using the first available set of position variables. When a ball is destroyed, ballmaker2000 clears out the respective position vars and removes one from the ball count variable.

The actual ball helpers themselves can look at their parent (ballmaker2000) to figure out the other ball's positions. They dont need to store the values themselves, or keep track of how many balls exist. They can just refer back to ballmaker2000 to figure out 1:if any other balls exist, and if so 2:if so, compare own position to the parent variables determining position of the other balls

The order the balls are created in doesnt matter, ballmaker2000 can just find the first set of open position vars

The balls themselves can look at ballmaker2000 and figure out if they need to do any collision detection and what set of position vars to compare against its own position

I guess the ball maker doesnt need a dedicated variable to keep track of how many helpers exist
But im not positive because i foget how numhelpers works in helpers

If it just looks at the total number of helpers the player has or if it correctly narrows it doen depending on what calls numhelper