What’s in the card
Game & platform
The game’s name and icon, plus a badge naming the platform or publisher
the strongest evidence came from — for example
STEAM or RIOT.Status badge
A second badge describing how confirmed the release is. See the table
below.
Version & build
The version and/or build number, shown as
old → new once both are
known, or just the new value the first time it’s seen.Timing
When the release actually went out (if the source says) and when Updater
detected it — these are often different, and both matter.
Summary
A short description of what changed, when the source provides one.
Patch notes link
A Read Patch Notes button pointing at the official source, when
Updater has a canonical URL for the release.
Status badges
How it updates over time
A release rarely announces itself all at once. A build number often shows up before official notes do; a maintenance window is often confirmed before anyone says what’s in it. Updater treats these as the same underlying release rather than separate events, and updates the one message as better information arrives — a card that started asBUILD ONLY can become
OFFICIAL VERIFIED once the developer publishes notes, with the version,
summary, and patch-notes link all filling in on that same message.
If two independent sources both report on the same release — say, an
official publisher article and a separately detected build ID — Updater
combines what each one proves into that single message instead of letting
one overwrite the other, or posting twice.
The first time you enable a game
The first check after you turn a game on in/games
establishes a starting point silently — it will not post updates for things
that already happened before you enabled it. Notifications start from the
next new release after that.