A better freshness model for game wikis than one global updated badge

A small product lesson from reviewing a game reference site: freshness belongs to each dataset, not to the domain.

Scrap Mechanic is currently on 1.0.5, but recipes, trades, unlocks, raids, and quest data may have different evidence and checked dates. Relabeling everything when one patch note is added creates false confidence.

A better model stores the live game version globally, then keeps checked version, source, date, and limitations beside each dataset. That makes the maintenance queue explicit and lets readers judge whether a value is safe to use.

The Scrap Mechanic Field Guide shows the idea in a live interface: https://scrapmechanic.org/

This pattern should work for price trackers, regulations, API references, and any product where one surface contains data with different refresh cycles.