Button Shooting: Set, Move & Fade

The saved timer owns the button

With BTN SHOOTING → BUTTON LOCK ON, pressing Square on PlayStation or X on Xbox starts a timed shoot-button hold. The script releases that output according to the selected Button Shooting context.

This is not manual Tempo Lock. Even if the Tempo Lock switch is also ON, Button Lock takes priority for the physical shoot button. OneTap remains a separate stick-click path.

Open the menu with L2 + Options or LT + Menu, choose BTN SHOOTING, then find BUTTON LOCK and the three timing fields. The heading on the small Zen display is abbreviated.

Choose the timer your input actually uses

All three fields allow 100–1,000 ms. Movement context is captured at the accepted button press. A short movement-history window can still select MOVE TIME immediately after the stick centres. For a standing test, let the stick settle and release both triggers before pressing the shoot button.

Quickstop has its own handoff into a standing shot. Leave that optional behavior off while you are learning the timing contexts, so the test has fewer changing inputs.

The three timers are stored per environment

SHOOTING → ENVIRONMENT selects MYCOURT, CITY, REC or CREW HQ. This V6 reference keeps separate Button Set, Move and Fade values for all four environments.

If you adjusted REC SET TIME but are using MYCOURT on the Zen, that is a different timing bank. Check the environment before concluding that an edit did not save.

Do not transfer this rule to every number in the menu: RELEASE PT, INSTA TEMPO and RHYTHM TIME are shared values in this source snapshot.

HUMAN LOGIC is the Button setting

BTN SHOOTING → HUMAN LOGIC is the optional centered Button Lock hold variation in this reference. Its stored default is OFF. When enabled here, a bounded −5 to +5 ms cycle is added to the chosen hold.

SHOT MODES → HUMAN MODE is the separate scripted stick-motion feature. The two switches are not synonyms. Keep HUMAN LOGIC OFF for a fixed-hold Button Shooting baseline.