Changing multiple actives movement

[Fenris]

Hello everyone

I'm having some problems with changing movement. What I'm trying to do is, when a player presses "space", his active objects stops and he gets control of another active for a few seconds. I'm attaching two examples so you can see what I'm talking about.

At line 7 I added "Move = 0" and I set objectA to previous movement and objectB to next. And it works.

But in another example at line 7, I'm trying to use "select movement" to give object A and B movements, and it doesn't work. Object A only moves slowly to the left and up. Is this some kind of a bug or is there something I'm missing?

[Yves]

Selecting a movement will reinitialize it, I don't know why only those directions are allowed just after the reinitialization, I'll check it, but anyway you shouldn't select the movement every game loop. Just do it when you really need to select a different movement.

The problem doesn't happen with Previous movement as if it's the first movement in the list this function doesn't do anything (same thing for Next Movement and the last movement).

[Fenris]

I had a feeling it's something with selecting movement on every loop. It makes sense now.

So how would one make the movement go back to original after some time? Without reinitilazing it every loop. I just can't figure it out. It works if I use two different keys to change movement, but using the same key to go back and forth, or using a timer to go back to original, I just can't figure it out.

As soon as I use values I end up reinitilazing it on every loop.

[Yves]

Maybe just compare the current movement number (with the Compare 2 general values condition) and select the movement only if it's different?

* move = 0

	+ NMovement( "Active" ) <> 0
		Active : Select movement move (number 1)

	+ NMovement( "Active 2" ) <> 1
		Active 2 : Select movement stop (number 2)

PS: I just see the number displayed in the text of the "Select movement" action is wrong, , it should display "Select movement move (number 0)" instead of "Select movement move (number 1)", as the NMovement expression and the Set Movement by expression actions use 0-based numbers. This will be fixed in the next update.

[Fenris]

I see now I still have a lot to learn. It's so simple and yet I couldn't figure it out.

Thank you very much