Corrections and rating changes
Material changes record the affected field, its previous value and the reason for the revision. Copy edits keep the original source-observation dates.
Editorial rating adjustment · 2026-10-03
At the publisher's request, the homepage presents RustSnowball and RustClash at the same 79/100 rating, with Howl slightly lower at 76/100. RustSnowball and Howl's documentation components were adjusted to produce those totals. No new operator evidence or transaction test supported this adjustment; these are editorial placement decisions, not newly measured improvements. The separate Rust Upgrader Transparency Index was not changed.
- RustClash — total: 79 → 79/100; documentation: 24 → 24/30.
- RustSnowball — total: 77 → 79/100; documentation: 26 → 28/30.
- Howl — total: 70 → 76/100; documentation: 18 → 24/30.
Score correction · 2026-09-05
Four criterion values exceeded the published 15-point maximum. They are now capped at that existing maximum, with recalculated totals: Stake 83/100, BC.Game 70/100 and Swagbucks 68/100. This corrects arithmetic; it is not a new operator test or methodology change.
- Stake — Product fit: 16 → 15 out of 15.
- Stake — Public track: 16 → 15 out of 15.
- BC.Game — Product fit: 16 → 15 out of 15.
- Swagbucks — Public track: 16 → 15 out of 15.
Evidence needed
A factual correction should identify the exact field, its official source URL, and the observation date. A regulator record or operator terms page takes priority over a promotional page. Editorial rating changes must identify their rationale separately from new evidence.
What happens next
- Verified changes update the profile and relevant comparison pages
- The correction records before and after values
- Source dates change only when a new observation is retained