the inputs for fatal rush, break hold, and breakblow are disabled in the moveset data and removing that stuff is the point of all this. If you're trying to use the hitbox viewer with the vanilla gameplay most people are probably better off running 6-- (uninstall 6++).bat and downloading the hitbox viewer from alex's thread.
getting ahead of ourselves a bit because somebody couldn't wait to tweet about it, I'll post about the interpretation of critical burst i've managed to cobble together. this is something i had thought about in a "what if" sort of way years ago but some recent public discourse about 6 being worse than 5 may have motivated taking another look into it.
This is barely a prototype and has some details and baggage that need to be worked out before it's ready for a playtest. I want to do some stage stuff and clean up the bt hits a bit before this would make public, and a change like this is the kind of thing i'd have in mind for arbitrarily changing the number to 6.0.
The idea is to have an exactly full stun (26/26 normal hit, 32/32 counter hit, 39/39 hi counter, and you're on your own with the extra 75% revision on environment stuns or whatever goes on if you find a way to do multiple fatal stuns) make the opponent unable to hold. this is not directly possible because i'm not able to program game logic like that, so instead it hijacks the system that overrides stuns into something else when you do a critical reversal. strive-style source leak when?
by setting a strike to do 2 damage and apply the CB stun it does 1 damage when scaled by the damage revision and thus only triggers a critical reversal if stun is already exactly full. unused animations are hard to come by but manipulating the breakblow attack anims seems to give reasonable frames.
the purpose of this new move is to make a manual version of the logic check i can't program I think it makes sense to have it only be a "i think the stun is full and i'm plus enough" button and minimally interact with the rest of gameplay. if it could do 0 damage and not count against the combo limit that would be better, but that's the minimum requirement i can find.
to that end it can't be held, it won't hit (or be guarded) at all unless they're stunned, and if you're bad and try to do it without perfectly filling the critical threshold you are punished for your hubris. -13 on hit is negotiable, although that number is tied to the recovery frames and making it -30 like i wanted starts interfering with your ability to convert on the perfect stun. The "time up" anim on whiff might be a bit much but if you mess up on the stun route this badly it means you didn't lab and you can eat a free hit for it. 16 startup could also be changed but i don't want it to work from jabs or shallow stuns like pp6k or 2h+k and on the other end it shouldn't be so restricted that you have to always do a +27 gut stun.
[i'm not reuploading, it's a non-critical mid hit and unsafe on-hit if you're wrong about the stun amount]
note also here that the jabs are only +15 or so, i had made a list of stun routes for ayane years ago and all the ones that ended in jab or pp feel like they'd be bad gameplay patterns. this is from dimensions, which had some progressive stuns like the more familiar progressive launch heights with the critical levels. I'm interested in these short jabs regardless of whether perfect criticals pan out so those might sneak into a 5.x update so we can try it without getting distracted by the PC.
and finally a moment to mourn the opportunity for an excellent april fools joke next year about putting breakblow back in.
Discord no longer allows hotlinking on external sites like that, for example your URL has its expiration timestamp set to 682476af which translates to 14 May 2025 10:55:43
burst is dead in the water, the four moves that have the magic to do different things in neutral and stun induce a bug where strings can skip moves and the buffer is much tighter sometimes for no discernable reason.
can't really make the burst move playable or not ugly in neutral and if there was a known way to make an input limited to "opponent stunned" i would've been trying this mechanic two years ago. (there are checks for on-hit, airborne, and downed but not stun afaik)
the faint hope for this would involve finding every possible stun route and coding on-hit followups for each move that could be last in a route, and that sounds miserable.
in a "call an amulance... but not for me" moment, the buffer bug is turning out to be not difficult to avoid dead input and some of the buffer skips (BS) are beneficial. it's not nearly as flexible as FSDC (search the 5lr forum if you don't know what that is) but it's way easier to do, at the cost of having to be more judicious with some string inputs. This does not appear to occur if you memory edit 5LR into the conditions that cause it in 6.
the downside to the bug is that if you mash out e.g. honoka 3ppp too fast it can just give you 3pp and stop dead, but it's also possible to do it so you skip 3pp and get 3p -> 3ppp. if you wait until 3pp is started to press the third p the string behaves normally.
as far as I can tell so far the "rules" are:
bug doesn't happen unless you've pressed h+p+k (S) and gotten one of the vestigial tag moves that are the hacked up way the perfect threshold works.
the bug is reset by rounds ending but not by resetting training mode without leaving
you have to start the string by buffering the first move of it out of something else. launcher, 6ph, whiffing a throw/hold, etc.
you have to buffer the input of the move you skip and the move after it before the skipped move starts, generally the frame after the active frames (see frame timings spoiler).
in 5-input strings we've seen skips of move 2,3, or 4 but i don't think we've seen a double skip either in a row or 2 and 4, unsure if those are possible. dunno what eliot is like.
i have a UI mod that delets the break hold text, didn't realize it was the same opcode as the lights down. suppose "optional extras" just got more important to finish
i'm using () for noting skipped moves here, i know some people use that for charging but they should use _ instead anyway.
pp(p)k means pppk skipped the third punch, and so on.
if you hate yourself several of these are in the twitter embed and you can verify the frame-by frame.
------
hayabusa pp(k)kk
220 - recovery frame 18/25 - P press
227 - null frame
229 - jab startup frame 1 - 2nd P press
240 - jab 2nd active frame but ID says PP - 1st K press
250 - pp 2nd active frame (ID still says PP) -2nd K
252 - id changes to ppkk
----
ayane bt pp6(k)kk
075 - recovery frame 1/25 - P press, likely extraneous
095 - recovery frame 21/25 - 2nd P press
099 - null frame
103 - jab startup frame 3 - 3rd P press
107 - jab startup frame 7 - 6 i assume held
114 - jab recovery frame 1 (ID says pp) - first K
121 - PP startup frame 8 - second K press
124 - bt pp6kk starts instead of bt pp6k
144 - recovery frame 5 third K press but that's just for the vanilla string
------
ayane p(p)pk
051 - recovery frame 2/25 first P
059 - recovery frame 10/25 second P
068 - recovery frame 19/25 3rd P (probably the real one)
075 - null frame
076 - move details still for previous move, ID says jab - 4th P
084 - jab startup frame 8, 5th P
089 - ppp starts instead of pp
if you're interested in labbing nonsense that might get scrapped because it ruins neutral, DM me here or on discord. i have to clean up some stuff not related to the buffer skips that should be ready early next week.
Group for people to get games in the community-made gameplay mod, DOA6++!
steamcommunity.com
BeeLy1011 was kind enough to make a steam group, i figure that's probably a convenient way to find matches if a bunch of us join rather than being scattered in a bunch of discords and whatnot.
