problem with changestate using Command

[Jessy]

I created states numbered as 2000, 2001,2002,2003,2004,2005,2010
then I added the
type=changestate
trigger1=command= "x·
value=2001

at 2000 in cns

then changed into 2001, the problem is when I added the same command changed only the value for the next that means: in 2001 value=2002,2002 value=2003,2003 value=2004.,
2004 value=2005,2005 value=2010  ...,
but only works with the last in that I put the command "x",it is in 2000 goes into 2010 ignoring and skip the previous, I changed the name for the command and put in cmd like "attack1" but still using x, but still have the same problem, that only works changing the button,for y,or adding more than one x command like x,x,x..
is there a way to mantain the command= "x" and work? I want that work with all states but that not happen...help..

[Demented Fortune Cookie]

it is in 2000 goes into 2010 ignoring and skip the previous

The way I see it, your character actually goes through states 2000, 2001, ... 2010 in a single tick.

So I guess adding a time trigger should do the trick.

Code Select Expand

type=changestate
trigger1=command= "x"
trigger1=time
value=2001

[Cyanide]

Your command is buffered. Add more triggers. I'm sure you don't want to change out of the first state until something specific has actually occured yes?

Time > 30 for example. Just to make sure that whatever is supposed to happen has done so before X is pressed again.

[Jessy]

it is in 2000 goes into 2010 ignoring and skip the previous

The way I see it, your character actually goes through states 2000, 2001, ... 2010 in a single tick.

So I guess adding a time trigger should do the trick.

Code Select Expand

type=changestate
trigger1=command= "x"
trigger1=time
value=2001

no the states 2001 and the others next are skipped-ignored,
anyway I decided delete it because do not work, so I decided use varset for it, and seems work, just the thing different than I expected..well..thanks..

[Cyanide]

You don't need a bloody varset. Told you how to fix it. What you have done is the equivalent of

changestate
time = 0

changestate
time = 0

changestate
time = 0

changestate
time = 0

a few times. Add in another trigger requirement for when you need the change to occur. Obviously it shouldn't be INSTANTLY or you wouldn't be complaining so ADD ANOTHER TRIGGER