A game bought on disc in 1999 was the version on the disc, permanently, unless the player did something about it. There was no update check, no background download and no notification. Patches existed, and finding out about them was the player’s problem.
How people actually found out
Discovery ran through the enthusiast press, cover discs, and word of mouth on forums and newsgroups. A magazine might mention that a patch had been released; the disc on the cover might carry it. Otherwise, a player had to think to check the publisher’s website, which required knowing it existed and having a connection worth using.
Substantial numbers of people therefore played the shipped version indefinitely, bugs and all, unaware that fixes existed. This was normal rather than exceptional, and it shaped how developers thought about launch quality: the disc version was, for a large share of the audience, the only version.
Applying a patch was a manual operation with real risk
A patch was an executable that modified an installation in place. It usually checked the version it was upgrading from and refused if that did not match, because patches were often incremental: 1.0 to 1.1, then 1.1 to 1.2, with no direct route from 1.0 to 1.2.
Miss a step and the sequence broke. Apply patches in the wrong order and the installation could end up in a state no patch recognised, with reinstallation the only fix. Anyone who modified game files, which included most people running mods, could find a patch refusing to run because a checked file no longer matched what it expected.
- Patches were frequently one-way. Reverting meant reinstalling from disc and starting the chain again.
- Saved games often did not survive a version change, and this was not always documented prominently.
- Mods were version-specific, so patching could break a working setup with no route back short of reinstalling.
Why version numbers still matter today
Anyone installing one of these games now inherits the whole situation. The disc is at its original version. The patches that once lived on a publisher’s server may or may not still be findable. And any modification being used will specify a version requirement written when that version was current.
This produces a recurring and confusing failure: a mod that will not load, with an error suggesting file corruption, when the actual problem is a version mismatch that the mod’s documentation stated plainly two decades ago.
Digital rereleases complicate it further. A rereleased version is usually the final patch level, sometimes with additional changes for modern compatibility. That is convenient for playing and awkward for mods, because it may not correspond exactly to any version a mod was ever tested against.
The practical approach
Establish what version an installation is at before doing anything else. Most games report it on a menu screen or in a file header, and knowing it converts a vague problem into a specific one.
Then read the mod’s documentation and believe it. Where it names a version, that is not a suggestion. Where a patch is required and no longer available from its original source, community archives frequently hold it, and this is one of the more valuable things such archives do.
What was lost when updates became automatic
Automatic updating is better in nearly every respect. Fixes reach everyone, the version is knowable, and nobody has to maintain a mental map of patch chains.
What it removed is the ability to stay put. A player who preferred an earlier version, or needed one for a mod, could simply not install the patch. That option has largely gone, and with it the ability to preserve a specific version of a game as it existed at a specific moment.
For a game as a product this rarely matters. For a game as an artefact, being unable to hold a version still is a genuine loss, and one that will become more visible as more of the current era’s software becomes historical.

