I never used it, but I think the “MoveComponentTo”-node does like the timeline-node not create a new instance of itself when called again. It initializes in the first round of the loop, then deletes the settings and reinitializes in the second round with the other component, then reinitializes in the third round etc. This is why it only works with the last component. I see two solutions at the moment: a) move the “MoveComponentTo”-node in the newly spawned actor. Then you’ll have a copy of it for each of the actors. b) Make your own “MoveComponentTo”-actor component which creates timers for each added component or so. Or an array with starting- and end-positions and an array with the components and in the tick-event somehow move them all in a loop. But this may be a bit more complicated.