Separate release date from playable status
- Step 1: Open the official release announcement and update archive, record the announcement date and version, and keep that source beside the page claim.
- Step 2: Open the installed client or current update screen and check whether the feature is actually playable in the current version.
- Step 3: Compare any video by upload date and stated version, then record the official date and installed-client status separately; update the page claim and related link together when the official status changes.

A release announcement can establish a date without proving that the feature is active in the installed client. Keep official wording, client version, and older video footage as separate evidence lines.
When a date changes, update the headline, first paragraph, and related source together. Then launch the client and check the version shown before telling players to travel to a new biome or use a new item. A date is an announcement signal; the installed game is the final check for what can actually be played.
- Record the announcement date and version from the official update page.
- Open the installed client or update screen before turning the announcement into a gameplay instruction.
- Label older footage by upload date and version so it explains context without proving current availability.
Refresh the status before sharing it
- Replace a stale date with the latest official update context.
- Do not treat a thumbnail or old test-branch video as release proof.
- Recheck the client version before describing a feature as playable.