Indie Game, Mod & Engine Release Tracking

Independent games and the tooling underneath them share a dependency that larger studios mostly avoid: the engine is a moving target. An engine major version brings new capability and a migration cost, and a small team choosing when to take that upgrade is making a scheduling decision that affects everything else they have planned.

Modding communities sit on the same fault line, one layer further out. A game patch can invalidate an entire mod ecosystem overnight, and framework maintainers then have to catch up before anything downstream works again. The sequence — game patch, framework update, individual mod updates — is a predictable cascade, and knowing where in it you are explains most compatibility problems.

What this category tracks

Independent game releases

Launches, early access transitions and post-launch updates from independent developers.

Game engine releases

Major, minor and patch versions of open source and commercial game engines.

Modding framework updates

Loader and framework releases, and the game versions they support.

Compatibility breaks

Game or engine updates that invalidate existing mods or projects, with migration notes where published.

What matters most here

The useful thing about tracking engine and framework versions together with the games built on them is that it makes the cascade visible. When a mod stops working the question is always the same — did the game update, or did the loader, or neither — and a chronological record of all three in one place answers it in seconds rather than through a forum search.

Where this data comes from

• Engine project release tags and official changelogs
• Storefront release and update listings for independent titles
• Modding framework repository releases
• Developer devlogs and official community announcements

Every indexed entry links to its primary source. See our editorial and sourcing policy for what we verify and what we do not.

Common questions