01 / Timing diagnosis

Write down the baseline first

Record the installed ERA version, active Zen slot, environment, shooting input, current timing fields and Human settings. Use the same equipped jumper and comparable open standing shots.

A useful baseline records both Early / Excellent / Late release feedback and Fast / Excellent / Slow tempo feedback where shown. Those are different observations.

Keep the same mode and shot context for five attempts. If some are moving shots or fades, repeat with one shot type before changing a field.

02 / Timing diagnosis

Example 1: changing SET TIME does nothing

Observation: you lower SET TIME, but the shot feels unchanged.

  1. Is BUTTON LOCK ON? If not, this may be a different shot path.
  2. Are you clicking the OneTap stick? That uses RELEASE PT instead.
  3. Are you moving or holding L2 / LT? Button Shooting may select MOVE TIME or FADE TIME.
  4. Are you editing the same environment that is active on the Zen?
  5. Does the value on the active Zen slot match the saved configuration?

This is an input/bank verification problem until those questions are answered. Increasing the adjustment size does not identify the active timer.

03 / Timing diagnosis

Example 2: manual Tempo Lock is early

Observation: holding Square / X and letting go produces repeated Early release feedback.

Confirm TEMPO LOCK is ON and BUTTON LOCK is OFF. Then test releasing your hand a little later at the same cue. RHYTHM TIME does not select your physical hold, so leave it fixed while making this comparison.

Once release feedback is consistent, inspect separate Fast / Slow feedback before testing the transition field. A manually early release and a fast transition need different evidence.

04 / Timing diagnosis

Example 3: a consistent OneTap hold comparison

Observation: five comparable OneTap standing shots are consistently early, and the active click, slot and saved values have been confirmed.

A small test could increase RELEASE PT from 680 to 685 ms. Keep INSTA TEMPO, Human settings and all shot conditions unchanged, then compare another five attempts. For a consistently late hold, the comparison direction is a small decrease.

The numbers illustrate a single bounded test. They are not a calibrated recommendation for every jumper. If results alternate early and late, keep the baseline and investigate inconsistent conditions first.

05 / Timing diagnosis

Offline and online are different observations

A good offline result does not establish that the same timing works in every online game. Record the environment and actual feedback rather than assuming a script setting measures network latency.

SERVER OC is not an internet-speed test. A jumper, animation, changing shot context and the active mode can all make a comparison less consistent. Separate those checks from a cable or controller fault.

For a broader explanation and existing demonstration, see Zen Court's ERA guides. For connection faults, use Zen Guide's hardware troubleshooting.