Keep a history when a game's information changes
A changed help screen should create a new observation, not erase the earlier one.
The distinction that matters
Record the title, version, environment, percentage and observation date together. If any identifier changes, keep both records and explain the difference. A new percentage on an otherwise similar screen may reflect a different configuration, a documentation correction or another change; the observation alone does not identify the cause.
A worked example
Your October note contains one version label and your November note another. Replacing the old percentage without retaining the label makes it impossible to know which record supported an earlier article. A versioned note preserves that trail and lets you ask a precise question about the change.
Your next steps
- Keep dated observations immutable.
- Compare identifiers before comparing figures.
- Mark the current record as unresolved if evidence conflicts.
- Update public explanations only after the applicable scope is established.
Where this answer stops
Northline does not infer misconduct or retroactive effects from a changed screen. This method supports a factual history. It cannot establish what software ran during a past account session without the relevant provider records.
Sources & reading
Original Northline explanation. Worked examples use stated assumptions; they do not establish an operator’s policy or predict personal results. Read how we handle evidence.
An editorial review date is not a new policy effective date. Always check the current source for operator-specific conditions.
Suggest a correction