Editorial policy
Our standard is simple: make the evidence as easy to find as the advice. This policy applies to every guide, including content drafted with software or AI assistance.
Three evidence labels
- Official information: a statement supported by a linked developer, publisher or service-provider source. It is not automatically a live status report.
- General troubleshooting: a reversible PC troubleshooting step that has not been independently validated against the WARDOGS problem discussed.
- Untested settings guide: a method for evaluating settings, not a measured best preset or a guarantee that a particular menu option exists.
Checked is not tested
A source-review date records when the cited material was reviewed. It does not mean the game was launched that day. “Last tested” stays “Not independently tested” until an actual test has been documented. A missing Build stays unknown; a Steam app ID is not a game Build number.
A future tested result should record the game Build, Windows version, CPU, GPU, RAM, driver, display resolution, settings, test scene, measurement method and repeat runs. Before-and-after claims must compare equivalent conditions.
Screenshots and original work
Official game media is credited and labeled as promotional. It must not stand in for an original error capture or benchmark. We do not fabricate gameplay screenshots, error codes, player reports, test dates, quotes or frame-rate results.
Our interface and editorial text are independently written. Familiar reference-site patterns, such as a game hub and an article contents list, do not authorize copying another site's articles, branding, assets or source code.
Safe, proportionate advice
Start by locating the failure stage. Prefer low-risk checks before changes to a system. Explain uncertainty and reversibility. Do not recommend disabling security protections, circumventing anti-cheat, downloading unknown repair tools or deleting shared service components.
Sources and changing information
Prioritize first-party sources and link directly to them. Release schedules and beta windows are snapshots, not permanent guarantees. An unavailable official status feed stays unverified. We do not turn the absence of an outage notice into an “all systems operational” badge.
Edits that change advice should update the source-review date only after the relevant sources are actually rechecked. A rebuild or deployment alone does not refresh it. Significant corrections should be explained in the affected article, not quietly disguised as new testing.
Commercial independence
The initial site has no advertising placements, sponsored articles or affiliate links. If that changes, we will label those relationships and update the disclosure and privacy pages before activating them.