Could be a number of situations that are causing it:

1.) Does the command use ~x? If not, it could be that the command is too strict
2.) What value does the command have for its command time? If the time is too short, that could be why the command is not working (or you're not doingit fast enough)
3.) Does the command have any alternate inputs (ex: D,DF,F+x AND D,F+x)? If not, the command might be too strict
4.) Are there any other requirements for using the move? ex: does the move require a certain amount of life or power? Check the triggers for the changestate controller that corresponds to the command (usually found in the cmd file).

Quote

20 seconds

20 ticks, you mean. That's 1/3 of a second, but it should be enough.
Are you sure the character has that special and it is working? Might be a coding problem that makes it unusable,too.

0. Did you get that command from the character readme files? If it's in the cmd but the character readme doesn't mention the attack, it might be a command not used by the character for anything (a leftover from a template or similar)
1. Check if the move actually is coded in the character and works. Easiest is to use a character that can force a state change into that state number in training mode, like my Aura in debug mode, but I think there are others with this feature, too. Sometimes people release incomplete characters where some specials or supers aren't coded yet.
2. If the move does exist, then look for conflicting commands. Any command that is a part of the special's command must have the changestate for it below the special, otherwise they'll take priority. For example, if the changestate for command "x" is first, then that attack will happen instead of the special.
3. Make sure the coding of the move does include ctrl=0 in the statedef. Otherwise you'll cancel the attack into walking immedietly (unless you release the F fast enough)
4. Try replacing the command with an easier version. D,$F,x should work.

change your keys. You have an options menu.

I'm sure you're aware that D F means down forward. Open options, change keys to suit, then try.

X does not mean the key X on your keyboard, it means the key you have defined as the X button.

Just in case, as your last post has made me doubt things

D = Down
F = Forward
U = Up
B = Back

a = a button]
b = b button] Kicks
c = c button]
x = x button}
y = y button} Punches
z = z button}

As defined in options, most people use qweasd or asdzxc for them.

RicePigeon said, August 01, 2012, 07:38:01 pm

4.) Are there any other requirements for using the move? ex: does the move require a certain amount of life or power? Check the triggers for the changestate controller that corresponds to the command (usually found in the cmd file).

My gut feeling is that this is whats causing the problem. Do you mind posting the code of the changestate controller that ues the command (ie: if the command for D,DF,F+x is "QCF_x", then look in the cmd file for a changestate which contains a trigger for command = "QCF_x"). Something tells me the author may have coded it improperly.

[Command]
name = "TripleKFPalm"
command = ~D, DF, F, D, DF, F, x
time = 20

;Triple Kung Fu Palm (uses one super bar)
[State -1, Triple Kung Fu Palm]
type = ChangeState
value = 3000
triggerall = command = "TripleKFPalm"
triggerall = power >= 1000
trigger1 = statetype = S
trigger1 = ctrl
trigger2 = statetype != A
trigger2 = hitdefattr = SC, NA, SA, HA
trigger2 = stateno != [3000,3050)
trigger2 = movecontact
trigger3 = stateno = 1310 || stateno = 1330 ;From blocking

You mentioned in the first post you were trying to do D,DF,F+x when the command you showed is D,DF,F,D,DF,F+x?

Probably the issue here, and common with keyboards, is that you're unintentionally skipping the DF command, which MUGEN reads as holding both the D anf F keys simultaneously. This isn't an issue for stick or pad users, but try omitting the DFs and see if that works (in other words, it should be ~D,F,D,F+x)

thread bump when topic is still on page 1