First establish that Button Lock is the active path
The explorer assumes BUTTON LOCK owns the physical Square / X input and that the shot starts from an idle state. It does not model every in-progress guard, menu state or remapped input. Use the Ozark2K mode checker first if you are unsure which shooting path you activated.
A OneTap stick click uses a different hold field. Changing SET TIME cannot tune a normal OneTap hold simply because both inputs produce a shot animation. The physical action is the first useful evidence.
Read the captured movement context
A settled standing press without L2 / LT uses SET TIME. Moving or recently moving can use MOVE TIME. Holding L2 / LT while stationary also selects the moving context in this source. Movement and L2 / LT captured together select FADE TIME.
A short movement-history window means centring the stick immediately before pressing the button does not necessarily create a settled standing test. Leave time for the input to settle and keep both triggers released when isolating SET TIME.
Separate context selection from the number
The explorer identifies a field; it does not measure your current setting or determine the correct millisecond value. After identifying the field, select the environment you actually use and read that field from the Zen.
Quickstop has its own standing-shot handoff. Its explorer switch shows that specific simplified case. For an ordinary baseline, keep optional movement behavior unchanged and test one context at a time.