put hit_ja: in the same frame as the hit_a: 268 (you're using frame 267).
and I would personally make 267 go to a different frame after wait: 2 (otherwise you can cancel the "forced DJA") actually if you know how you can still get past the "lock" (I figured out how accidentally)
(08-26-2009, 08:10 AM)Azriel Wrote: put hit_ja: in the same frame as the hit_a: 268 (you're using frame 267).
and I would personally make 267 go to a different frame after wait: 2 (otherwise you can cancel the "forced DJA") actually if you know how you can still get past the "lock" (I figured out how accidentally)
Azriel~
Azriel i still have a problem. It wont goes to the transformation(273 +) frames from some reason.
oh and about that thing. with that frame its just that i wont be able to press at all . how can you possiblely press a button in a such short time. not even 3rd of a seocnd.
Anyway i cant figure why it dosnt go to frame 273 when i press a in frame 267 or cause of the next. it will obey the dja. i will make it so that you have to press fast enogh to force the dja.
the priority of the inputs is hit_ja > hit_a:, so when they press A, both sequences DJA and A are detected. it first checks if it can go to the DJA frame, otherwise it goes to the hit_a: frame.
and in between, there's lots of little "filler" and/or "filter" stuff that reduces the number of ways around the lock, but it can't stop the final one (I know how it works coz I programmed the sequence detection in HQ and it has the same "bug").
Chat
Discord
![[Image: ZucdcMY.png]](https://i.imgur.com/ZucdcMY.png)
