AboutJudgment - cwtickle/danoniplus-docs GitHub Wiki

English | Japanese

| < Velocity change & Motions | Judgment specification || Custom key types template > |

Judgment specification

Basic judging conditions

  • Basically, the contents defined in g_judgObj are reflected.
  • If the timing when the target arrow or the starting point of freeze arrow is on the step zone is set to ±0 frames, the judgment is determined by how far off (early or late) the timing when the key is pressed is.
  • If the key is pressed too late or not pressed at all, it will be judged out of frame, and the judgment target will be shifted to the next arrow or the starting point of freeze arrow.

Arrow

Judgment character(Ja) Judgment character(En) Judgment conditions (allowable discrepancies) Fast, Slow count conditions
(・∀・)ｲｲ!! :D Perfect!! 0～±2 Frames ±2 Frames
(`・ω・)ｼｬｷﾝ :) Great! ±3～±4 Frames ±3～±4 Frames
( ´∀`)ﾏﾀｰﾘ :| Good ±5～±6 Frames ±5～±6 Frames
(´・ω・`)ｼｮﾎﾞｰﾝ :( Bad ±7～±8 Frames ±7～±8 Frames
( `Д´)ｳﾜｧﾝ!! :_( Miss... Out of frame(+9 Frames or higher) (Nothing)

Freeze arrow

Judgment character(Ja) Judgment character(En) Judgment conditions (allowable discrepancies) Fast, Slow count conditions
(ﾟ∀ﾟ)ｷﾀ-!! :) O.K. - 0 to ±4 Frames (starting point) and press Freeze Arrow to the end ±2 to ±4 Frames (starting point)
(・A・)ｲｸﾅｲ :( N.G. Match any of the following- ±5～±8 Frames (starting point)- +9 Frames or higher (out of frame)- Release the freeze arrow midway- The next freeze arrow (starting point) arrives before the decision is made ±5～±8 Frames (starting point)

Excessive miss judgment

  • Excessive miss judgment executes when the arrow is pressed faster than it flows. This is only applicable when the "Excessive" setting is turned on.
Judgment name Judgment conditions
Excessive -16～-9 Frames

Judgment flow

  • The arrow and freeze arrow names to be judged are defined for each lane to prevent duplicate judgments.
  • After judgment is completed, the next arrow or freeze arrow name is designated as the judgment target.

Key press action

  • To avoid overlapping judgment of the arrow and freeze arrow (starting point), the one that is closer (shorter remaining time) from the respective step zone is judged as the target.
  • If neither of the two is in the judgment area, the step zone is only illuminated and no judgment is made.
flowchart TD
A([start])-->judgeArrow-->Z([end])

subgraph judgeArrow
    B1["Get the arrow name of the next judged target"]-->B2["Obtains the name of the next judged Freeze Arrow"];
    B2-->B3{"Comparing the remaining time of the next arrow <br>with the remaining time of the next freeze arrow"};
    B3-->|"Arrow residual time is less"| B4["judgeTargetArrow<br>Judging arrow"];
    B3-->|"Freeze-arrow residual time is less"| B5["judgeTargetFrzArrow<br>Judging freeze arrow starting point"];
end;

Released key in the middle of the freeze-arrow (freeze-arrow only)

  • If the key is released in the middle of the freeze-arrow operation after pressing the start point of the freeze-arrow, processing will continue as long as the released time is within the number of frames indicated by frzAttempt. If the number of frames exceeds the number of frames, failure is assumed.

In case of flow out of the screen frame without pressing a key

  • If an arrow or freeze arrow goes outside the frame without being pressed, a decision is made for outside the frame.
  • When the previous arrow or the starting point of freeze arrow enters the judgment area (within the recovery judgment), the previous arrow or freeze arrow is forcibly deleted. This is to solve the problem that the judgment of the next arrow or freeze arrow cannot be made because the judgment of the previous arrow or freeze arrow has not been completed. However, if the timing of the press is within ±2 frames of the previous arrow or the starting point of freeze arrow, priority is given to the previous arrow or the starting point of freeze arrow.

Related pages

Changelog

Version Change details
v35.4.3 - Fixed an issue in judging when the end point of a freeze arrow and the beginning point of the next freeze arrow are close to each other.
v33.1.2 - Fixed an issue in judging when the end point of a freeze arrow and the beginning point of the next freeze arrow are close to each other.
v32.5.0 - Implemented excessive miss judgment.
v29.3.3 - Fixed an issue where the starting point judgment of Freeze Arrow was sometimes double judged when the starting point judgment was valid and a late :( Bad was issued.
v29.3.2 - Fixed an issue in which the arrow-side judgment was double-counted when the starting point judgment of Freeze Arrow was enabled and NG was issued for the starting point judgment.
v29.0.1 - Changed to count Fast and Slow for the starting point of Freeze Arrow, regardless of the starting point determination.- Extended the judgment range of the starting point of the freeze arrow to the front of the frame.
v28.5.0 - Added an exceptional process to transfer judgment from the previous arrow if the later arrow reaches the step zone before the judgment of the previous arrow is completed.
v18.9.1 - Fixed an issue in which the judgment of the normal arrow took precedence over the freeze arrow when a normal arrow and a freeze arrow existed in the same lane with a short interval between them.
v5.12.1 - Added exceptionally transferring judgment from the previous freeze arrow if the later freeze arrow reaches the step zone before the judgment of the previous Freeze Arrow is completed.
v1.0.0 - Initial implemantaion

| < Velocity change & Motions | Judgment specification || Custom key types template > |