By Asep Darmawan 
The PC gaming landscape has long been defined by a constant push-pull relationship between developers and hardware enthusiasts. As graphics fidelity reaches near-photorealistic levels and game worlds expand in both scale and complexity, the burden on consumer hardware grows accordingly. However, a recent incident involving the upcoming online co-op shooter Cinder City has brought the issue of system requirements—and the transparency surrounding them—to the forefront of the industry conversation.
When South Korean publisher NC unveiled Cinder City earlier this week, the initial excitement surrounding its high-octane, zombie-shooter gameplay was rapidly eclipsed by a shockwave of confusion regarding its stated system requirements on Steam. The listing, which at one point demanded an unprecedented 64GB of RAM, sparked a fierce debate about the escalating costs of PC gaming and the state of modern game optimization.
The Chronology of a Technical Mismatch
The controversy began almost immediately after the game’s reveal trailer dropped. Prospective players flocked to the official Steam store page to gauge whether their current rigs could handle the new title. What they found was a set of requirements that seemed to defy industry standards.
Initially, the Steam page listed a minimum requirement of 32GB of RAM, with a recommended specification of 64GB. In an era where 16GB is the industry standard for most mid-to-high-tier gaming PCs, these numbers were staggering. The community reaction was swift and critical, with forums and social media platforms erupting in disbelief.
Within 48 hours of the backlash, the development team at Big Fire Games and their publisher, NC, issued a formal acknowledgment. They admitted that the initial figures were erroneous. The page was subsequently updated, bringing the RAM requirement down to a more "modest" 32GB for both minimum and recommended tiers. However, the saga did not conclude there. Eagle-eyed users soon noted that while the RAM requirement had been walked back, the recommended GPU specification had been quietly "upgraded" from an NVIDIA RTX 4060 to the significantly more expensive and powerful RTX 4070, suggesting that the developers are still fine-tuning their performance targets.
The Economics of Modern RAM
To understand the severity of the initial 64GB requirement, one must look at the current market for computer memory. As of late 2024, the cost of high-performance DDR5 RAM remains a significant barrier for the average consumer. A high-quality 64GB kit (typically 2x32GB) can easily retail for between $200 and $300, and often significantly more depending on speed and RGB features.
When translated into the context of global currency fluctuations and regional pricing, these requirements represent a massive financial commitment for a consumer simply looking to play a single video game. For many, a 64GB RAM requirement would necessitate not just a memory upgrade, but a complete motherboard overhaul, as many older platforms do not support the density required for such kits, nor the throughput of modern DDR5 standards.
The incident highlights a growing disconnect between the hardware enthusiasts who populate development studios and the reality of the average player’s hardware configuration. While developers are working with high-end development kits that often feature massive overheads, the "average" PC—according to the most recent Steam Hardware Survey—typically remains tethered to 16GB of system memory.
Official Responses and the "Optimization" Caveat
The official statement from the developers serves as a masterclass in crisis communication within the tech sector. By labeling the initial requirements as an "error," the studio effectively defused the immediate vitriol while buying themselves time to conduct further optimization.
"We apologize for any confusion this may have caused," the developer wrote in their official Steam community post. "The information has now been updated to the correct specification. Please note that the current system requirements are based on our current development build. As optimization continues, the final system requirements at launch may be lower than those currently listed."
This statement is telling. It implies that the requirements listed are not fixed, but rather a reflection of the current "raw" state of the game engine. In game development, optimization is often the final phase of production. By releasing a title into an unoptimized state, developers risk alienating their player base. By being transparent about the "development build" status, NC is attempting to manage expectations, though it begs the question: why publish such extreme requirements in the first place?
Implications: The Trend Toward "Bloated" Requirements
Cinder City is not an isolated case. In recent years, we have seen a trend where titles are released with requirements that seem to punish the user for the developer’s lack of optimization. The case of LEGO Batman: Legacy of the Dark Knight, where developers were forced to downgrade recommended RAM from 32GB to 16GB after community pushback, serves as a precedent.
There is a growing fear among the PC gaming community that "optimizing" games has become a lower priority for studios compared to hitting release windows. When a game requires 64GB of RAM, it suggests that the engine is either leaking memory or failing to manage assets effectively. If a game is not truly utilizing that memory for gameplay mechanics or visual fidelity, the requirement becomes an unnecessary tax on the user’s hardware.
The Impact on Consumer Trust
Transparency in system requirements is a form of consumer protection. When a developer lists a requirement that is later found to be an "error," it damages the credibility of the studio. Players rely on these specs to make purchasing decisions, including hardware upgrades. If a player purchases a $600 RAM upgrade based on a faulty Steam listing, they are unlikely to view the developer favorably when the requirements are later halved.
The Future of Optimization
As we move into the next generation of gaming, the conversation must shift toward efficiency. Developers like id Software (with the DOOM series) have long proven that games can look spectacular while remaining highly scalable. The Cinder City incident serves as a wake-up call for the industry: the community is watching, and they are increasingly knowledgeable about the difference between a demanding game and an unoptimized one.
Conclusion: A Lesson in Transparency
While Cinder City looks like a promising title—drawing inevitable comparisons to The First Descendant and other high-fidelity shooters—the initial misstep with its system requirements has cast a long shadow. The industry is at a crossroads where the cost of hardware is rising, and the patience of the consumer is thinning.
Moving forward, it is incumbent upon developers to ensure that their "Recommended" specs are a reflection of a polished product, rather than a reflection of their current, unoptimized development environment. For now, Cinder City remains without a firm release date. When it eventually does hit the digital storefronts, the success of its launch may well depend on whether the final requirements reflect the promised "optimization" or if the game remains a hardware-hungry anomaly.
For the PC gaming community, the message is clear: demand better optimization, be wary of "placeholder" specifications, and hold developers accountable when their requirements seem to defy the logic of the hardware market. As Cinder City continues its development journey, one can only hope that the final product respects the hardware of the players as much as it respects their time.
Nana 
Nana Wu 