help with cmd file

hello, im trying to code alittle character here for myself, but i encountered a problem
similar shorter special commands preventing hyper command to be executed for some reason

for example if i have hyper with command: ~D, DF, F, x+y and special with command ~D, DF, F, x, and try to execute hyper in the game it just does special

putting hyper on a different command helps, but i want to use regular layout, since character has 4 specials and 4 hypers

what could be the reason behind this issue, does somebody knows?

I have ran into similar issues before, and reorganizing the commands usually got everything working for some reason. What I mean is, have your hyper commands at the very top of the cmd file, then followed by your specials commands, then followed by your basic commands such as "hold down" or "Super Jump", etc. No guarantee that will work, but it has for me many times in the past, and I have done it like that for years because I read somewhere that is what you are supposed to do with your cmd file, because it assigns command priority, meaning that the commands at the top of the cmd file will have priority over the commands below it such as a special command, also meaning that a D,DF,F, x+y command would have higher priority and thus would be what initiates when doing that command, as opposed to doing a D,DF,F, x+y command, and having a D,DF,F, x special command happen instead. Also, try adjusting the command timings. If a command has a timing set, but is set too low (fast), it will prevent the move from being able to execute.
Last thing I will say, is that I recommend setting command timings for all your commands, even if it doesn't fix your issue. If you don't have them, it leads to specials and hypers activating unintentionally, because when you don't have them, a move does not have to have inputs inputted within a given amount of time. So if you at some point hit forward, then a couple seconds later hit down to crouch, then a few seconds later hit forward again to move forward, then do a punch, a darn special will activate because you over the course of like 5 seconds inputted D,F, then an attack button. When you have timings set, specials and hypers will only activate when you intentionally do them, or are just mashing buttons, just like an actual fighting game. I've yet to see an actual AAA made fighting game that does not use command timings, yet 1 out of 5 mugen authors never actually assign their characters any for some reason. It's like having negative edge on standby if that makes any sense. Enough ranting, but yes, reorganize your cmd file, and set timings to all commands. I may get lashed for not mentioning the command.buffer timing, but that stupid setting never seems to do squat for me. Anyways, good luck man.

thanks for advice
i think i have hypers on top of specials already and time is set 30 for hypers and 20 for specials too?
i will try to tinker something with it maybe it will help

yes, it worked!
i got command inputs for hypers on the top, but not the commands codes themselves
it helped putting them higher than specials, thanks again

No problem man, glad it worked for you.

One extra MUGEN note:

In the CMD MUGEN file, not only the command definitions follow the top-down order pattern, but also the ChangeState MUGEN Controller does so too.

For example, the normal throw command ChangeState code piece:

Code:

;Normal Throw
[State -1, ChangeState]
type = ChangeState
value = 800
...............
triggerall = Command = "y" || Command = "z"
...............
trigger1 = Command = "holdfwd"
...............
trigger2 = Command = "holdback"
...............

If this Normal Throw ChangeState is placed ABOVE some other ChangeState code pieces like one that makes use of some commands like "QCF_x" => "D,DF,F,x", then the Normal Throw ChangeState CAN prevent you from executing the said "QCF_x" move:

Code:

;QCF_x move
[State -1, ChangeState]
type = ChangeState
value = 1000
...............
trigger1 = Command = "QCF_x"
...............

So, if ChangeState value = 800 is above ChangeState value = 1000 then when you try to execute Statedef 1000 command then the Statedef 800 will happen instead!

@Borewood2013
That, I did not know. Thanks a lot for sharing that with us. There have been a few times when I have failed to fix a command issue, and that is probably the exact reason why. Good tip, thanks again. I'm gonna go try it right now so I don't forget.