A review on Script Ranking passes three stages, each with its own rules, and every rule can be checked against the published pages.
Before writing
- The reviewer buys the script at retail.
- The seller's product, refund and update pages are read, and the reading date is kept.
- An NBA 2K27 script completes the 150-shot drill set on how we test before it receives a score.
During writing
- Prices, feature counts and version details carry the day they were checked.
- A measured figure states its sample size and its session. A judgment is labelled as the reviewer's.
- A seller's claim is attributed to the seller. Undetectable, safe and ban-proof are words no review uses for a script.
- Settings are described by what they do to the controller input. A number in a seller's headline does not count as a feature; a setting the buyer can switch on does.
- Where a repeat session could reverse the gap between two scripts, the page says so.
- Anything that could not be checked is marked unchecked, with a pointer to the seller's page.
After publishing
- An error is fixed on the page that carries it, and the updated date moves with the fix. A fix that changes a score notes the date and what changed.
- Any reader can open a correction through the corrections form.
- A patch that changes shot timing calls for a new session, published separately from the old one.
Money questions are answered on the disclosure page.