How should a game catalog organize years of updates for one title?

Games that have been updated for many years create an interesting information-design problem. A single “latest version” page is simple, but it can hide the events, compatibility changes, and features associated with earlier releases.

Shadow Fight 2 is a good example. Its core fighting and RPG systems have remained recognizable, while different releases have introduced seasonal events, raid content, characters, and technical changes. Someone researching the game may want the newest release, but another user may be looking for information about a particular event or an older Android device.

I’m working on Play Mod Game, an Android game and version discovery catalog. For our Shadow Fight 2, we use a central game page supported by separate articles about notable versions and game content.

I’m currently considering how to make this structure easier to navigate. A chronological timeline would make the update history clear, while filters could help users narrow releases by year, event, or Android compatibility. Another option is to show only a few important releases by default and keep the complete archive available separately.

The challenge is providing enough context without turning the page into a long list of nearly identical version numbers.

For makers who have built documentation, software archives, or content directories: would you prioritize a timeline, filters, or a comparison table? At what point does preserving older version information become more confusing than useful?