Credit: Nexus Mods/Steam DB
featureEditorials
SteamDB could help Nexus Mods make game updates less painful
September 3, 2026·6 min read
You probably use SteamDB for tracking Steam prices, player counts and game updates. Under its new owner, that same data could soon help check whether a mod collection matches your game version.
On September 2, Chosen announced that it now owns both SteamDB and Nexus Mods. Nexus wants to connect SteamDB's historical game data with its modding tools, giving mod managers a better way to check which version of a game is installed and which version a collection was made for.
If you use large mod collections for games like Skyrim or Fallout 4, you probably know how quickly an update can cause problems. A patch can break plugins or script extenders, leaving you to work through dozens of mods to find what went wrong.
The SteamDB integration is still only a plan. Chosen also needs to find a way to fund the service without putting the features people already use behind a paywall.
Installing the right mod is only part of the job. It also has to match the version of the game you are running.
Skyrim Script Extender, for example, has separate downloads for Steam, GOG, VR and older versions of Skyrim. Its developers also warn that plugins may stop working after Bethesda updates the game.
Fallout 4 is even more specific. F4SE 0.7.2 supports game version 1.10.984, while 0.6.23 supports 1.10.163. The latest Steam and GOG versions do not always match either.
This becomes a problem with older mod collections. The author may have built and tested the collection on a game version you no longer have installed.
Right now, finding that mismatch can mean checking documentation, reinstalling files and disabling mods one by one. Nexus wants its tools to catch it before you start installing.
The good part is that most of the data Nexus needs already exists.
Steam keeps manifests for different versions of a game's content. These show which files belong to a build, including their sizes and hashes. SteamDB records that information as games are updated.
Nexus says it had already started collecting Steam data itself, but older version information becomes harder to access once a new update replaces it. SteamDB has spent years keeping that history.
Connecting the two services could allow a mod manager to compare the game files on your PC with the version used by a mod collection. If the collection was tested on an older build, the manager could warn you before installing it.
That would be much more useful than discovering the problem after launching the game.
Nexus also wants to look at warnings for future game updates. A modded setup could then flag that an incoming patch may affect the mods you already have installed.
Those warnings will need to be specific. Telling someone with 300 Skyrim mods that "the game has updated" does not help much. Naming the affected version or component would give them something they can actually check before pressing update.
But knowing the game version solves only part of the compatibility problem.
A manifest can tell Nexus which game files are installed. It cannot tell the mod manager whether every plugin, texture pack or script still works with them.
That information still has to come from mod authors, collection curators and testing. The Skyrim Script Extender developers can confirm which version of Skyrim their own tool supports, for example, but that does not automatically confirm every SKSE plugin installed alongside it.
Nexus will also have to distinguish between something that is broken and something that simply has not been tested yet.
A collection built for one version of Fallout 4 may continue to work after a small update. Marking it as incompatible without evidence would create a different problem, especially if the warning causes players to remove mods that still work.
Going back to an older game version is separate again. Some developers provide previous builds through Steam's beta branches, while others do not. SteamDB can record that an older version existed, but Nexus cannot make that build available if the developer no longer offers it.
The most useful part of the integration is therefore the early warning. It can tell you that your installation does not match what the collection expects before you spend an evening trying to work out why the game keeps crashing.
The other challenge is paying for SteamDB without changing what people already use for free.
You could worry about price history, player counts and other existing features that end up behind a subscription. But hosting is only part of the cost. SteamDB also needs people to maintain its tools, keep up with changes to Steam and fix problems when something breaks.
xPaw started SteamDB with Marlamin in 2013. After Marlamin stepped back, more of that work fell to xPaw. He has described maintaining the site as comparable to a full-time job and started looking for a partner in January after experiencing burnout.
Chosen can now spread that work across a larger team. The harder part is finding a way to pay for it without taking away the free features that brought people to SteamDB in the first place.
Nexus has already made one important promise: everything that is free on SteamDB today will remain free.
They also state that there are no plans to require new logins, sell personal data or introduce display or programmatic advertising.
Instead, the company is considering partnerships, integrations and affiliate links when users leave SteamDB to buy a game. None of those options has been confirmed as the final business model.
New features are different. Nexus has left open the possibility of charging for services that do not exist today, which could eventually include some of the tools built around SteamDB's data.
Checking a game's update history should remain free under Nexus' current promise. What is still unclear is whether new tools built on top of that data, such as automatic compatibility checks for large mod collections, will also be free.
For now, the more interesting part of the acquisition is what SteamDB could add to Nexus Mods. Game updates have been breaking modded setups for years. Giving a mod manager a reliable record of which version you have installed will not fix every broken mod, but it could tell you there is a problem before you install one.
We want to hear from you. Share your perspective in the comments below, and please keep the conversation respectful.
Log in to join the discussion - vote, reply, and share your take.
Log In
11h ago
12h ago
13h ago
14h ago
15h ago
16h ago
8h ago
1d ago
8d ago
9d ago
9d ago
10d ago
