Editorial policy

Sources come first

Every published page lists the sources behind it with the date we read them. Where a fact comes from a publisher post, the page says so. Where it comes from an editor playing the game, the page says that instead. A link returning a normal response is not treated as verification of anything.

How code status is labelled

• Official — the game or publisher posted it. We have not redeemed it ourselves.
• Editor-tested — an editor redeemed it and it worked, with a hands-on source on file.
• Unverified — it circulates in the community, with nothing official or hands-on behind it.
• Reported expired — a source reports it stopped working, and the report date is shown.

Nothing moves to Editor-tested automatically, and no code expires just because time passed. A code only becomes “reported expired” when there is a dated report behind it.

Review schedule

Code pages aim for a re-check every 24 to 48 hours, guides and patch write-ups every 30 days or whenever the game version moves on, and event pages more often as their dates approach. Those are targets for our own queue, not a promise that someone just played through the whole guide. Each page shows two separate dates: when the content last changed, and when it was last re-checked.

When we stop maintaining a page

Pages that are no longer being re-checked say so at the top and keep their dates. We would rather leave a dated historical page than silently present old facts as current.

Mistakes

If something here is wrong, tell us and we will fix it and record what changed. The process is on thecorrections page.

How these pages are written

Pages are written and reviewed by the Rulevio editorial team. Research notes and drafts may be organised with software assistance, but a person decides what gets published, and we do not publish bulk pages that have no answer in them.