Content Verification Policy
Verification policy
Practical Basketball can change between tests and releases. Every time-sensitive page should identify the applicable version, the latest check date, and the confidence level of its claims.
Confidence labels
| Label | Meaning |
|---|---|
| Verified | Confirmed through an official source or a reproducible in-game check for the stated version. |
| Source-reported | Reported by an attributable third party but not independently verified by this site. |
| Needs retest | Previously supported information that may have changed in a newer version. |
| Unconfirmed | A community claim or expectation without enough evidence to publish as fact. |
Builds
A build must identify its position, intended mode, core attributes, strengths, weaknesses, source, and applicable version. A popular creator build can be described as source-reported, but it is not called “best” without explaining the criteria and trade-offs.
Controls and mechanics
Controls must be separated by platform. Old test controls cannot be copied into a current guide without a new check. Instructions for self lobs, dunks, alley-oops, dribble moves, and other mechanics should include input conditions and common failure cases.
Game status and release information
Official Roblox listings and developer-controlled community announcements take priority. If no official release date exists, the page must say so. Community estimates cannot be converted into confirmed dates.
Codes
Codes are only marked verified when an official source publishes them or a direct in-game test succeeds. If no redemption system or verified code exists, the page should state that clearly instead of listing examples or guessed rewards.
Corrections
Material corrections should be recorded in the relevant page's update history. Send reports to contact@practicalbasketball.net and include the page URL, applicable game version, supporting source, or reproducible in-game result.