Tempo Lock & RS Tempo

Tempo Lock: hold, then let go

With SHOT MODES → TEMPO LOCK ON and BTN SHOOTING → BUTTON LOCK OFF, hold Square on PlayStation or X on Xbox. Release the button at the visual cue of your equipped jumper.

Your hand chooses the physical release moment. The script shapes the following right-stick release. RHYTHM TIME controls that transition; it does not decide how long you hold the button.

RS Tempo: movement is not a click

With SHOT MODES → RS TEMPO ON, move a right-stick axis past the activation threshold, keep it deflected for more than 300 ms, then return it to centre. In the checked source, activation is beyond 30% on an axis and return requires both axes back within that band.

Clicking R3 / RS does not perform this gesture. It tests the click binding, which can start OneTap or a remapped button input instead.

Start from an idle shot path. Avoid holding the shoot button or running a OneTap sequence at the same time, because a shot already in progress has its own input protections.

Both manual paths share RHYTHM TIME

Tempo Lock and RS Tempo share this release-transition value in the reference build. It is not a separate per-method or per-environment personal timing bank.

Changing it can affect both manual paths. Keep that relationship in mind if one input feels correct and the other does not. Changing the environment does not create a different OneTap or rhythm value in this source snapshot.

Read release and tempo separately

Early / Late release feedback: for these manual paths, first change when you physically release the button or return the stick. Do not try to fix a manually early release by assuming RHYTHM TIME chooses your hold.

Fast / Slow tempo feedback: this is a different observation about the release transition. Establish a repeatable physical release before making a small, isolated test of RHYTHM TIME.

If a test mixes moving shots, fades and standing shots, the combined results do not isolate one setting. Use the timing diagnosis to narrow the cause before editing.