Elite Dangerous Field Manual:Updating Game Statistics
How to update an article after a game change, and how to record what changed.
Update the fact, then the metadata
Change the actual figure/behaviour in the article body first. Then update {{Article status}}'s version and reviewed fields to reflect when and against what version you checked — never leave stale defaults after making a substantive change, even a small one.
When Live and Legacy diverge
If a change only applies to Live and Legacy keeps the old behaviour, don't just overwrite the old figure — state both explicitly in the prose ("On Live, X; Legacy retains Y") and fill in the legacy_differences field on {{Article status}}. See Elite Dangerous Field Manual:Content Style Guide for how to phrase this.
Recording the change: Patch history
For anything more than a one-line note, add a row to that article's {{Patch history}} table (create the section near the bottom, in the same position as {{Engineering nav}}, if the article doesn't have one yet):
{{Patch history|
! Update !! Date !! Change
|-
| [[Trailblazers]] (Update 3) || 2025-04-30 || Colonisation economy reworked.
}}
Link the Update name to its own Game Update article where one exists ({{Game update infobox}}) — that link is what lets Special:WhatLinksHere on the Update's own page answer "which articles did this update affect," with no separate per-update category needed. If the article's own version field also names that update, link it the same way — see Trailblazers and Colonisation for a worked example of both sides of this connection.
Use recent_changes for a one-line pointer
If a change is genuinely minor and doesn't need a full Patch history entry, the optional recent_changes field on {{Article status}} is enough — a short sentence, not a table.