YesNoOk
avatar

DP Input Inconsistency  (Read 220 times)

Started by Master0fFaster, February 23, 2025, 10:31:09 pm
Email this topic
View printable version
Share this topic:
« previous next »
Page 1 of 11   Go Down

Master0fFaster

DP Input Inconsistency
#1  February 23, 2025, 10:31:09 pm
  • avatar
Been playing around with inputs lately, and for some reason, 623a is making my 236a come out. This doesn't happen with 236B and 623b, and 236a cancels into 623a without any problem.
I heard somewhere that this was caused by the order in which the moves are indexed, but i changed that and it still doesn't work. I've tried doing this, too, but to no avail

[Command]
name = "623a"
command = F, D, DF, a
time = 25
[Command]
name = "623a"
command = F, D, DF, F, a
time = 25

This is my first time, and I don't have much experience working on MUGEN stuff, so I am genuinely lost

Odb718

Re: DP Input Inconsistency
#2  February 24, 2025, 01:34:40 am
  • *****
  • Shame on you!
    • USA
so the order of the statedef -1 matters, like you mentioned.
Make sure the more complex move is above the easier move. Like your 2nd "623a" would probably never be triggered.

You also need to look at your buffer times. 623 and 236, idk what moves those would be. is one backwards and one's forwards?

if you think a move should come out, but a different move is interrupting it, make sure the input is above the bad one. Then focus on the location of the changestate, then look at the triggers.
vVv N00bSaibot & Muramasa RoofTop vVv
Page 1 of 11   Go Up
« previous next »