Scratch

I'm not sure what you want to happen, but would suggest separating the costume changes (stances) from the movement.  This may be simpler in the long run, I think that the costume changes in the movement (jump) are over-riding the kick. 

You can put together a script that cycles the character thru the kick costumes and make sure the timing is right to make it look good.  Then you need to decide when a kick should be allowed.  Think of what information the kick script needs to have about what the character is doing, and make variables to track that info. 

Here is my thought:

I think that you probably want the "kick" to only occur if the character is in a jump and is high enough.  So the jump script, when it gets the jump input, could cycle thru some costumes to represent the jump and then give the character upward velocity (as your script does now).  Once the character has left the ground, the script could set two variables:

Jumping = 1
HighEnoughToKick = 1

If the user gives the kick input, the script that cycles thru the kick costumes can test these variables to see if it should run.  If Jumping = 1 AND HighEnoughToKick = 1 then run the kick script, if either isn't true, ignore the input.

The motion (jump) script, would keep testing how high the character is, and when he is on the way down and too low to Kick, set HighEnoughToKick = 0.  When he is back on the ground, set Jumping = 0.  You could also use the Jumping variable in the motion script to prevent jumping again while you are already jumping.

There are lots of way to do things in programs, I always try to imagine what the program really needs and make variables to keep track of that info.  Hope this helps.

Last edited by EdnaC (2011-06-08 10:49:11)