PC Releases Move to “IBM PC Compatible”, and Compatibility Gets a Proper Form

What changed

Two related changes went live this week, both about how PC games are catalogued on Omni Games.

1. PC releases now use one platform: IBM PC Compatible.
Until now, PC titles were split across several Windows platform entries. A game that shipped for Windows 95 and also ran on XP could land under different platforms depending on how it was imported. That split one piece of hardware into several "platforms" and made it harder to see everything released for the PC in one place.

Those entries are now consolidated under a single platform, IBM PC Compatible. Linux and Macintosh stay as their own platforms.

2. OS compatibility is now structured data.
Which versions of Windows, Linux or Mac OS a title works on is no longer typed in as free text. Editors now tick from a fixed list:

  • Windows: 3.1, 95, 98, 98 SE, ME, 2000, XP, Vista, 7, 8, 8.1, 10, 11
  • Linux: Ubuntu LTS releases, Debian, Fedora, Arch, Mint, openSUSE, SteamOS
  • Mac: System 7 and Mac OS 8/9 through to macOS 26 Tahoe

The result shows on each release's game card, directly under the Product Code:

Compatible with Windows: 98 SE, XP, 7

You can see it in action on this example title.

Why "IBM PC Compatible"?

The platform is the hardware, not the operating system. A console release is catalogued against the console, and PC releases should work the same way: against the machine they run on.

Windows isn't a machine. It's software that has changed many times over the same family of hardware. A disc from 1997 and a download from 2024 both target an IBM PC compatible, but they'll run on very different versions of Windows. Treating each Windows version as a separate platform mixes up two different things: what the game is for and what it runs on.

So the hardware becomes the platform, and the OS becomes compatibility metadata attached to each release. This also leaves room for DOS-era titles, which belong on the same platform without needing Windows at all.

Why a fixed list instead of free text?

Free text drifts. "Win XP", "XP", "Windows XP SP2" and "XP+" all mean roughly the same thing, but a database can't treat them as equal. A fixed list means:

  • every title records versions the same way,
  • the data can be filtered and compared later,
  • it's quicker for editors to fill in.

Any free-text values saved before the change aren't lost. They show on the edit form marked as legacy and stay saved until an editor unticks them.

Share: Reddit X Bluesky Facebook

← All posts