How an update entry is verified
An update entry should answer four questions: when was it published, where did the information come from, what system changed, and what should a player do differently? A copied list of bullet points is not enough when the practical consequence is unclear.
The tracker prioritizes official announcements and platform notices. Community reports can explain an edge case, but they are labelled as observations and are not presented as a confirmed patch change without a supporting source.
- Publication date and source URL
- Version or update label when the source provides one
- Affected platform or system
- Practical consequence for players
What this page will not do
The tracker will not invent a patch number, claim a rumor is official or keep an old version at the top without a visible date. When the public source is unavailable, the page says that the item needs verification.
This approach is slower than scraping every headline, but it keeps an update hub useful after the first week and makes corrections possible.
- No fabricated version numbers
- No unlabelled rumor presented as fact
- No silent replacement of old sources