Quick answer. A green window is the range of release timings that can produce green shots under specified conditions. It is not the same as the percentage of shots a script greens in one session.
Measure timings, not just success totals
Choose one build, jumpshot, cue, distance and mode. Vary the hold or release timing in controlled steps. At each step, repeat the same number of attempts and record green versus non-green outcomes.
Plot the success rate against timing. State how the edges are defined: a non-zero success rate, a chosen probability threshold and a fitted boundary are different definitions and can produce different widths.
What changes the interpretation?
Keep badges, stamina, contests and relevant game settings controlled. Record the game patch and connection conditions. An offline test does not establish the same curve in every online mode.
A frame or sampling interval limits what the instrument can distinguish. For example, 60 frames per second gives about 16.7 ms between frames; that arithmetic is not itself a measured NBA 2K timing window.
Green rate versus window width
A fixed-count script comparison answers how many attempts were green under that protocol. Without controlled timing offsets, those attempts do not reveal the window's width in milliseconds.
This article contains no original window-width estimate. Earlier center, width and confidence-interval claims were withdrawn because their trial records were unavailable. For instrumentation choices, see how input latency is measured.
A figure looks wrong? Report an error
Further notes
- Reviewing latency claims after firmware and game updates
How to decide what needs a new source check or a new physical test after a software change.
- Input-lag test equipment: what a reproducible report needs
A checklist for documenting press detection, response detection, timing and the full test chain.
- Does a heavier Cronus Zen script add input lag?
How to distinguish script processing load from end-to-end input latency without assuming a fixed penalty.