Editorial & correction standards

Rift Atlas distinguishes official rules, derived calculations and practical planning advice. A guide revision date describes our page, not a new live-server verification.

What counts as evidence?

Numerical game rules should link to an official notice or guide that identifies the applicable service. Historical patch notes establish what changed on their publication date; they do not prove that a cooldown or capacity is unchanged today. A community reference is labelled separately and does not become official because multiple sites repeat it.

What is calculated here?

Expanding a stated three-hour cycle into eight daily rows and converting UTC offsets are calculations. Worked examples show the inputs so you can reproduce the result. The rift timer is not a live portal feed, and the boss calculator uses your own kill time and interval. We do not invent current regional values to fill a table.

How are articles maintained?

Changed articles receive their own modification date. Source notes retain the date a source was read and any date displayed by that source. Original diagrams are labelled as workflows when they are not geographic maps. We do not claim hands-on testing of a game rule without a documented observation.

What belongs in a correction?

Include the page URL, disputed statement, service, date and a public official source where possible. For a timing mismatch, include the server clock, your time zone and observed next start. Do not include passwords, access tokens or private account details. Game account issues belong with official support.

Scope of this edition

The current content concentrates on ordinary rift planning, Taiwan guide references and a separately labelled Korea community clock. Global timing is manually calibrated. Content without sufficient numerical evidence is presented as a workflow, not a complete regional database. No live game connection is implied.