Editorial policy

Source Policy

This page explains how the site separates official facts, search-demand research, community leads, and in-game verification.

SourceConfidenceUse
Official store pages High Platforms, PC requirements, account notes, official system wording, and launch availability.
37GAMES event page High Launch-week dates, pre-download notes, official calls to action, and event announcements.
Apple App Store listing High Mobile version, iOS compatibility, app size, supported languages, age rating, in-app purchase disclosure, and regional review signals.
Steam community review summary High for sentiment, lead only for causes PC launch sentiment, account requirement, anti-cheat disclosure, and why troubleshooting content matters.
Local Trends Valid report High for demand, not for game mechanics Keyword demand, video count estimates, domain checks, and priority decision.
Community videos and comments Lead only Guide leads, possible code strings, class topics, and pain points that still need verification.
Competitor guide scan Architecture lead only Page ideas such as reroll, Spirit roster, spirit-ring system, and download/troubleshooting pages. Do not copy unverified claims as facts.
In-game checks Highest Working codes, exact rewards, drop locations, build math, and tier-list rankings.
What this means in practice

A possible code from a video can be tracked as a lead, but it does not become a working code until stronger evidence appears. A tier-list claim needs patch, mode, cost, and repeated results before it becomes ranking guidance.