How would you organize a game-mod directory so users can judge compatibility quickly?

I’m working on a game-mod discovery website, and one product-design question keeps coming up: how much information should users see before opening an individual game page?

A mod listing can become confusing surprisingly quickly. A game may have several versions, different Android requirements, multiple modified features, and updates that no longer work with older save files. Showing everything in the listing makes the interface crowded, but hiding too much forces users to open several pages before finding a compatible version.

The information hierarchy I’m currently considering is:

• Game and mod version

• Last updated date

• Required operating-system version

• Main modified features

• File size

• A short compatibility or installation note

I’m also considering clearer labels for outdated versions and a visible update history. The goal is to help users understand what a listing contains without presenting safety or compatibility claims that cannot be guaranteed.

The current project is Play Mod, which provides the practical context for this design problem. I’m sharing it so people can see the type of catalog and content structure being discussed, rather than as a general promotion.

For people who have built directories, marketplaces, or download-oriented products: which details would you prioritize on the listing card, and which would you reserve for the individual page? Have filters or comparison tools worked better than adding more metadata directly to each card?