Steam's Three-Year Gate: How One Indie Game Exposes Platform Approval Power
An Australian indie horror developer has spent three years waiting for Steam approval on a game built with Valve's own Source engine — a delay that raises structural questions about the world's largest PC games marketplace.
An indie horror game called AMYGDALA: Prelude has been stuck in Steam's approval queue for three full years, despite using Valve's own Source engine — the same development toolkit that built Half-Life 2 and Team Fortress 2. The developer, posting as @pirat_nation on X, said on 2 May 2026 that Valve has provided no explanation for the hold and no estimated resolution date. The case exposes a structural imbalance in PC gaming: one company controls the world's dominant storefront, and one company's approval decision can effectively determine whether a years-long project ever reaches its audience.
The approval gap
Steam's review process has never been transparent. Developers submit builds, undergo technical checks, and — in most cases — receive clearance within days to months. Extended delays do occur, often tied to technical complexity, third-party integrations, or mod-kit compatibility. But three years is anomalous even by the standards of a platform that has spent two decades normalising wait times. The sources do not indicate what specific technical issue — if any — Valve has flagged in AMYGDALA: Prelude's submission, or whether the review has been actively ongoing or simply stalled at an internal stage.
What is clear is the opportunity cost. A game that entered review in early 2023 has now missed three years of release windows, festival visibility, wishlists, and community momentum. Indie titles live and die on timing; a three-year gap can shift a project's competitive context entirely.
Why Source?
AMYGDALA: Prelude's choice of Source engine is worth examining on its own terms. Valve open-sourced a modified version of the engine in 2023, and community forks remain actively maintained. For an indie team, the engine offers a credible 3D pipeline without licensing fees and a known visual signature — that particular Source look that reads as deliberately nostalgic to an audience that grew up with Valve's early titles.
The irony is that Source-based games on Steam are, in a narrow sense, Valve-adjacent projects. They run on the same engine Valve uses internally. They target the same runtime environment Valve controls. And yet that technical proximity does not appear to have expedited AMYGDALA: Prelude's review. The sources do not indicate whether Valve's internal tooling creates particular review considerations for Source-based submissions — whether, for instance, engine-specific audit steps add friction that does not exist for Unity or Godot builds.
Platform as gatekeeper
Steam holds roughly 75 percent of PC game distribution by revenue, a dominance that makes its approval decisions commercially existential for studios without an established audience. The platform has no formal published service-level agreement for review turnaround, no independent arbitration mechanism, and no published list of rejection criteria beyond broad technical and content guidelines. Developers who feel aggrieved can email Valve's developer relations team; appeals are not a formalised process.
This asymmetry has been a feature of the platform's design since its early years. Gabe Newell and Valve have consistently framed Steam as a curated marketplace rather than a neutral infrastructure layer. The trade-off developers accept is access to Steam's 1.3 billion active accounts in exchange for ceding editorial control. But the AMYGDALA: Prelude case is at the outer edge of what developers have historically accepted as reasonable friction.
In broader indie development — particularly the narrative-focused horror space AMYGDALA: Prelude appears to occupy — multiple storefronts exist as fallback options. itch.io and Epic Games Store offer lower barriers to entry. But the audience concentration on Steam remains vast; listing a game elsewhere without a Steam presence is, for most commercial titles, a significant visibility disadvantage.
What happens next
Valve's silence on the specific delay leaves the developer with limited recourse. Public pressure through social media — as @pirat_nation has now applied — is one avenue, and it has produced outcomes in isolated cases where unusual attention forces a response. Alternative storefronts are the other. But neither changes the structural reality: one company holds effective veto power over a significant portion of the world's independently developed games, and the criteria for that veto remain opaque.
The AMYGDALA: Prelude case is not an isolated grievance — it is a data point in a broader pattern of platform dependency. The indie development ecosystem normalised platform risk when it normalised Steam as the primary launchpad. What three years of silence on a Source engine title surfaces is that this risk is not hypothetical; it has a real timeline, a real developer, and a real game that has not yet reached its audience.
This publication reported on the developer's claims as stated in their publicly posted account. Monexus reached out to Valve for comment but had received no response at time of publication.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://x.com/pirat_nation/status/1909019428926017670