Yes, it indeed does. The position of functions in the code determines their order in the scheduler list. From your description I would also expect a dependence of this kind. Something sets the player pointer back, but this has only an effect if it either happens after the pointer is set, or before it is evaluated.

So the critical function that resets the player pointer is either somewhere within the code part that you moved. Or it is immediately before or behind the position where the inserted code just worked again.