WAZAAAAA
Well-Known Member
Choryo is displayed as [3]P in the move list, but the real input is a bit more complex.
This is a combo with many Choryo's in it:
If you want to use it in combos, you need to Crouch Dash. It's the fastest way to crouch in DOA, and a normal Crouch Dash input would be 33, but you can't use that one because 33P exists, you need the alternative 663 or 623. So, in a nutshell:
Buffer 663 or 623, *WAIT* for the Crouch Dash to start, add P.
But truth to be told, it's not that simple. Since the developers had the bright idea of giving Eliot 3 different inputs that end in 3P, weird unexpected conflicts can arise, especially if you're too fast with the input.
Here's the relevant dumped code for the move:
After testing some DOA5LR Choryo's in the neutral in a tool-assisted way I reached these outcomes:
This means that:
- it has a Full Crouch requirement (can't be Standing)
- you need to "Charge" the input to bypass the conflicts with 3P or 33P because they have higher priority
- if you're doing the 663 method the 2nd 6 must be held for 7F or more, with the 623 method the charge is also 7F but it can be "shared" between the 2&3
This is a combo with many Choryo's in it:
If you want to use it in combos, you need to Crouch Dash. It's the fastest way to crouch in DOA, and a normal Crouch Dash input would be 33, but you can't use that one because 33P exists, you need the alternative 663 or 623. So, in a nutshell:
Buffer 663 or 623, *WAIT* for the Crouch Dash to start, add P.
But truth to be told, it's not that simple. Since the developers had the bright idea of giving Eliot 3 different inputs that end in 3P, weird unexpected conflicts can arise, especially if you're too fast with the input.
Here's the relevant dumped code for the move:
Java:
// eliot i=21 j=15
CMD_BO_CHORYO
ACT_NAME(AC_BO_CHORYO)
SIT_CHK
CMD_ONLY(HOLD|LV_RD)
CMD_KEY(BT_P)After testing some DOA5LR Choryo's in the neutral in a tool-assisted way I reached these outcomes:
Code:
(663P version)
6 for 1F
5 for 1F
6 for 7F
3 for 1F
3+P for anyF
= successful Choryo
6 for 1F
5 for 1F
6 for 6F
3 for 1F
3+P for anyF
= fail, 3P executed
(623P version)
6 for 1F
2 for 6F
3 for 1F
3+P for anyF
= successful Choryo
6 for 1F
2 for 5F
3 for 1F
3+P for anyF
= fail, 33P executed- it has a Full Crouch requirement (can't be Standing)
- you need to "Charge" the input to bypass the conflicts with 3P or 33P because they have higher priority
- if you're doing the 663 method the 2nd 6 must be held for 7F or more, with the 623 method the charge is also 7F but it can be "shared" between the 2&3
It's actually a "Full Crouch" move.
so the "Switch Frame" speed affects its execution (skill info page 3)
so you're supposed to crouch dash (which is the fastest way to crouch in DOA, 1 frame) if you want to do many Choryos fast
but you can't crouch dash by doing 33 because Eliot has a 33P move which takes priority
so you do 623 or 663 instead which are still acceptable crouch dash inputs
soo you can't really buffer the P, you have to wait until you're crouching every time. You can buffer it if you're already crouching though. Remember that every Choryo puts you standing
TL;DR
buffer 623/663 to crouch ASAP, press P (not buffered) once you're actually crouching
so the "Switch Frame" speed affects its execution (skill info page 3)
so you're supposed to crouch dash (which is the fastest way to crouch in DOA, 1 frame) if you want to do many Choryos fast
but you can't crouch dash by doing 33 because Eliot has a 33P move which takes priority
so you do 623 or 663 instead which are still acceptable crouch dash inputs
soo you can't really buffer the P, you have to wait until you're crouching every time. You can buffer it if you're already crouching though. Remember that every Choryo puts you standing
proof of all of this: try doing free step 3 (press 963_ to do it). It doesn't matter how long you're pressing 3, when you press P the Choryo will never happen because you were never crouching
buffer 623/663 to crouch ASAP, press P (not buffered) once you're actually crouching
Last edited:
