How we test, and how to check our work
Everything on this site is written by people who run these builds on their own hardware. That is worth stating plainly, because most content in this market is written by people who have never launched the product they are describing.
What testing means here
A build is installed on real hardware, run through a full setup on a current Windows install, and played across several sessions before anything is written about it. What we report is what happened on that machine — including when it failed.
Each game guide carries a last-tested date for exactly this reason. Anti-cheat moves constantly, and a guide without a date is a guide you cannot evaluate. If a date looks stale relative to a recent patch, treat the specifics as provisional and check the status page for the build's current state.
What we will not write
We do not describe any product as undetectable. No such product exists, the claim is unfalsifiable, and every anti-cheat vendor eventually disproves it. What we can say is whether a build is currently detected, how quickly its provider has historically responded to patches, and what usage patterns have actually got people banned.
We also do not present a ban as impossible if you follow instructions. Reducing risk is achievable; eliminating it is not, and pretending otherwise would make everything else here less trustworthy.
Commercial relationships, stated plainly
This is a storefront. We sell the products we write about, and we earn when you buy them. That is an obvious conflict of interest and the right response is disclosure rather than pretending it is absent.
In practice it cuts the other way more often than people expect: recommending a build that gets someone banned produces a refund request, a support ticket and a customer who never returns. Accurate risk assessment is the commercially better choice, which is a large part of why the status board reports confirmed detections rather than guesses.
Corrections
When something here is wrong, we change it and the last-tested date moves with it. Guidance that turns out to have been unsafe is corrected as a priority rather than quietly edited.
If you have found something inaccurate — a step that no longer applies, a requirement that changed with a Windows update, a status that does not match what you are seeing — tell support or raise it in Discord. Reports from people running these builds daily are the main reason the guides stay current.
Common questions
Who writes these guides?
Staff who run the products on their own hardware, drawing on what is reported across the customer base and what providers tell us about their own builds.
Are the reviews independent?
No, and we say so. We sell what we write about. What we can offer instead of false independence is disclosure, dated testing, and a status board that reports confirmed detections rather than guesses.
How current is the information?
Each game guide carries its own last-tested date. For anything time-sensitive — whether a build is safe right now — the status page is authoritative and the guides are not.
How do I report an error?
Through support or the Discord server. Specifics help: which page, which step, and what happened instead.
