The Empty Castle: How Ubisoft Launched a 23 KB "Ghost" Version of Heroes of Might & Magic 3 on Steam

The turn-based strategy masterpiece Heroes of Might & Magic III is widely regarded as one of the finest PC games ever created. Originally released in 1999 by New World Computing, its tactical depth, enchanting soundtrack, and addictive "just one more turn" gameplay loop have kept a dedicated community active for over two decades.

However, the game’s modern distribution history has been fraught with frustration. For years, Steam users were forced to choose between a deeply flawed 2015 HD remaster or migrating to rival platforms to experience the game in its definitive form.

When current IP owner Ubisoft quietly made the original, expansion-complete version of the classic available on Steam, it should have been a moment of triumph for strategy enthusiasts. Instead, it quickly devolved into a technical embarrassment. Upon purchasing the title, players discovered that Ubisoft had forgotten to include the actual game files, delivering a "ghost" download of just over 23 kilobytes that refused to launch.

Main Facts: The Empty Download and the "Dummy Executable"

On the day of the release, eager players who paid the $10 asking price to purchase the original version of Heroes of Might & Magic III on Steam were met with an unprecedented technical error. Rather than downloading the roughly 1 gigabyte of data required for the game and its expansions, the Steam client completed the download almost instantaneously.

The 23.49 KB Game

A closer inspection of the installation folder revealed a total file size of just 23.49 KB. The download contained no game assets, no sound files, no maps, and no game engine. Instead, it consisted of a single, non-functional "dummy" executable file.

The Launch Error

When players attempted to launch the game through Steam, the operating system generated an immediate error message indicating that the executable could not find its supporting assets or was simply a placeholder. In essence, Ubisoft had successfully created a Steam store page, set up a payment gateway, and configured a download pipeline, but failed to upload the actual video game.

Immediate Backlash

The community response was swift and unforgiving. Within hours of the listing going live, the game’s Steam store page was flooded with hundreds of reviews, driving its user rating down to an 80% "Mostly Negative" score. Angry players accused the publisher of unprecedented negligence, warning others not to waste their money on an empty folder.

Chronology: The Rocky Road of Heroes III on Digital Storefronts

To understand why this release was so highly anticipated—and why its failure is so stinging—it is necessary to examine the timeline of Heroes of Might & Magic III across modern digital distribution platforms.

[1999] Original Release (Restoration of Erathia + Expansions)
  │
  ├─► [2008] GOG.com Launches "Complete Edition" (Definitive DRM-free version)
  │
  ├─► [2015] Ubisoft Releases "HD Edition" on Steam
  │            (Lacked expansions due to "lost" source code; heavily criticized)
  │
  └─► [Present] Original Version Quietly Listed on Steam
               (Launches as a 23.49 KB empty file; massive review bombing)

1. The Golden Era and GOG’s Dominance (1999–2008)

Following the collapse of original publisher 3DO, the rights to the Might & Magic franchise were acquired by French publisher Ubisoft. In 2008, digital preservation platform GOG.com (Good Old Games) released Heroes of Might & Magic III: Complete Edition. This version bundled the base game, The Restoration of Erathia, with its two essential expansions: Armageddon’s Blade (which added the Conflux faction and a random map generator) and The Shadow of Death. For over fifteen years, GOG remained the undisputed home of the definitive Heroes III experience.

2. The Flawed 2015 Steam HD Edition

In 2015, seeking to capitalize on the game’s enduring popularity on Steam, Ubisoft released Heroes of Might & Magic III – HD Edition. However, the release was widely panned by hardcore fans. Ubisoft claimed that the original source code for the expansions had been lost, meaning they could only remaster the base game.

As a result, the Steam HD version lacked:

• The Armageddon’s Blade expansion.
• The The Shadow of Death expansion.
• The crucial Random Map Generator, which gave the game infinite replayability.
• Multiple factions, campaigns, and balance updates.

For a decade, the community’s universal advice to new players was to avoid Steam entirely and purchase the Complete Edition on GOG.

3. The Surprise Classic Release and Immediate Failure

In an attempt to rectify this long-standing issue, Ubisoft decided to bypass the source code limitations of the HD remaster by simply publishing the original, un-remastered Complete Edition directly to Steam. This version, running via legacy compatibility wrappers, was meant to finally bring parity between the Steam and GOG offerings. However, the launch was immediately derailed by the missing asset blunder.

Supporting Data: Comparing Storefront Offerings

The discrepancy between the broken Steam release and existing versions of the game highlights the magnitude of the publisher’s oversight.

The Financial Irony

While Ubisoft charged $10 for an empty directory on Steam, GOG.com coincidentally had the fully functional Complete Edition on sale for 50% off ($4.99) at the exact same time. This pricing dynamic further incentivized frustrated players to refund their Steam purchases and migrate to GOG.

Technical Underpinnings: How Does a "Ghost" Release Happen?

To understand how a multi-billion-dollar publisher like Ubisoft can accidentally sell an empty game, one must look at the mechanics of Steam’s developer backend, known as Steamworks.

[Developer Local Build] 
       │
       ▼
[Steamworks Backend] ──(Misconfigured Depot?)──► [Public Release Branch] ──► [Player PC (23 KB Dummy)]

Steam Depots and Branches

When a publisher prepares a game for Steam, they organize the game files into "depots"—logical folders that hold the assets, executables, and libraries for different operating systems or language versions. These depots are mapped to specific "branches" (such as Beta, Internal Testing, or Public).

In a standard release pipeline:

1. Developers upload the complete game assets to a secure testing branch.
2. Quality assurance testers verify that the build launches and plays correctly.
3. Upon approval, the administrator merges the testing branch into the Public default branch, making it available for purchase and download.

The "Dummy Executable" Failure Mode

The presence of a 23.49 KB file yielding a "dummy executable" error suggests a severe configuration error in Ubisoft’s Steamworks dashboard.

It is highly likely that the administrator configured the Steam store page to point to a temporary "stub" or testing build rather than the actual release depot. When the game went live, Steam’s servers served the empty placeholder branch to paying customers, while the actual game files remained locked in an unlinked private developer depot.

Official Responses and Expected Resolution

At the time of writing, Ubisoft has not issued a formal public apology on its main social media channels, though community managers on the Steam discussion forums have acknowledged the issue.

Time-Zone Discrepancies

Industry observers note that the delay in deploying a hotfix is largely due to geographic and administrative time-zone differences. Ubisoft’s primary digital distribution and production teams are headquartered in Montreuil, France (Central European Time). Because the game was published late in the day, the blunder went unnoticed by the internal publishing team until the following business morning.

Historically, "depot configuration" errors of this nature are relatively simple to resolve once noticed. A backend administrator simply needs to redirect the public Steam branch to the correct file depot and push an update. However, the speed of the fix does little to erase the embarrassment of the initial launch.

Implications: Quality Control and Legacy Preservation

While the "empty game" bug will undoubtedly be patched, the incident raises broader, more troubling questions about modern game publishing, quality control, and the preservation of classic intellectual properties.

1. The Decline of Publisher Quality Control

For a major publisher to release a product without verifying if it contains the actual game files points to a systemic lack of human oversight. Modern digital storefronts rely heavily on automated pipeline tools, which can lead to catastrophic failures if developers treat legacy releases as passive, low-effort revenue streams. The fact that no one at Ubisoft attempted to download and test the public Steam build before pressing "publish" is a stark reminder of how classic portfolios are sometimes managed by major corporations.

2. The Superiority of Preservation-Focused Storefronts

This incident serves as a powerful advertisement for GOG.com and the DRM-free movement. While Steam operates primarily as an automated open marketplace where publishers manage their own uploads, GOG employs dedicated curation and compatibility teams to ensure that classic games run reliably on modern operating systems before they are listed for sale. For retro PC gamers, the contrast in quality control could not be more obvious.

3. Impact on Future Franchise Releases

The timing of this blunder is particularly unfortunate for Ubisoft. The publisher is currently preparing to launch a new entry in the franchise, Heroes of Might & Magic: Olden Era, alongside other rumored remake projects.

For a community already skeptical of Ubisoft’s handling of the Might & Magic brand, a high-profile failure to launch a 25-year-old game does little to inspire confidence. If Ubisoft hopes to rebuild goodwill ahead of its upcoming strategy releases, it must prove it can manage its legendary back catalog with the respect and technical competence that the franchise’s legacy demands.