OUR EDITORIAL STANDARD

Show the source.
Explain the limits.

Useful advice needs more than a confident headline.

1. Start with primary evidence

We use official patch notes and developer documentation for rule changes. Community observations can provide context, but are not automatically treated as universal rules.

2. Keep versions visible

A guide identifies the version behind its key claim. A sources-checked date is an editorial review date, not the release date of an update. We do not label an old patch as the latest release.

3. Separate facts from judgment

Our take explains the practical implications of the documented facts. We do not invent first-hand playtime or test results. Numeric comparisons must state their source and assumptions.

4. Label visuals honestly

AI-assisted illustrations explain concepts. They are not gameplay screenshots, controlled tests, or evidence of actual in-game outcomes. Data tables carry the comparison; illustrations help readers follow it.

5. Use AI with source checks

AI tools assist drafting, layout, and illustration. Generated claims are not sources. Factual statements need support from the linked evidence before publication.

6. Update when the evidence changes

When a correction or update is made, the affected claim and its sources should be reviewed together. Cosmetic changes do not constitute new gameplay testing.