Source review and gameplay testing
Source review checks a claim against an attributable reference. Gameplay testing records an observation under stated conditions. Our articles identify which evidence supports them; a documentation review doesn't become a performance result.
Jump shots
Record the base, both upper releases, blend, speed, cue, build height and eligibility requirements. Keep stationary, moving and free-throw attempts separate, and separate online play from offline practice.
Retain all attempts and explain exclusions. Define the measurement before collecting results. A recommendation must identify the comparison, its conditions and its limitations.
Controller settings
Save the baseline and change one setting at a time. Keep the build, jumper, input method, controller, platform and game mode fixed for the comparison. Check passing, recovery and rebounding as separate tasks.
Report the conditions you evaluated. One player's preferred setting doesn't establish a universal preset.
Animation requirements
Check the current in-game requirement or a primary record. Capture height limits, attribute thresholds and whether alternative attributes are accepted. Keep eligibility separate from performance, and retain the platform and game version with each record.
Controller automation
Record the device and script versions, controller, connection method, game version and configured inputs. Distinguish a working connection from a changed input and from a game result. A product claim should be evaluated under the conditions it names.
Compare complete sessions under matching conditions. Keep misses and interruptions visible. Apply the same evidence requirements to affiliated and unrelated products.
Practice-tool calculations
The timing tracker calculates average, median, minimum, maximum and range from your entries. It doesn't capture the game or identify a hidden shooting window. A smaller spread describes the entered timings, not a guaranteed improvement in made shots.
Keeping evidence current
Record the source date separately from the game version. After a relevant update, revisit the claims that depend on it. Keep earlier records so an editor can see why advice changed.