Mega Crit’s decision to delete Slay the Spire 2’s controversial Doormaker boss shows how community feedback, data, and design philosophy are colliding during early access – and what it means for difficulty, fairness, and long‑term replayability.
Doormaker Is Dead, Long Live Aeonglass
In Slay the Spire 2’s latest beta patch, Mega Crit pushed a big red button on its most divisive design experiment. The Act 3 boss Doormaker has been completely removed from the game and replaced with a new encounter, Aeonglass. For a studio that usually prefers small, incremental tweaks, deleting a headlining boss is about as extreme as it gets.
This moment is bigger than one fight. It shows how Mega Crit is trying to navigate a tougher early access climate, reconcile raw player sentiment with cold balance data, and still ship a roguelike that can hold up for thousands of runs.
Why Doormaker Went Too Far
On paper, Doormaker was not a statistically unfair boss. Mega Crit said that, across millions of runs, its overall difficulty and player win rate were slightly lower than the other Act 3 bosses. Numbers suggested it was actually a bit weaker.
The problem was how it created that difficulty. Doormaker cycled through phases that attacked the core verbs of Slay the Spire: it exhausted cards out of your deck, blocked your ability to draw, and spiked card costs. For a deckbuilder, those are fundamental systems. Hitting them all at once turned the fight into a parade of constraints.
Mega Crit’s own patch notes describe the core issue clearly. Doormaker “had interesting micro decisions in the fight” but it was “over the complexity threshold” the team wants for Act 3 bosses and it still had “lingering issues.” That is the key distinction. The devs liked the decision density inside the fight, but not the way it stacked complexity, rules text, and punitive mechanics on top of already long runs.
It also created a specific kind of loss. Reaching Act 3 usually means your deck is finally online. Doormaker’s design often invalidated what you had built by shredding key cards or locking your engine out of the game. Players described it as watching a “god‑tier run brutally and unforgivingly obliterated” in a way that felt out of step with other bosses, even if the raw win rate lined up.
So the issue was less “too hard” and more “hard in a way that breaks what makes the game fun.” For a late‑game roguelike boss, that is a dangerous line to walk.
When Data Clashes With Player Emotion
The Doormaker saga is a textbook example of the tension between designer data and player perception. Early on, Mega Crit defended the boss by pointing to internal stats. If millions of runs show the fight is slightly weaker than the other Act 3 options, then surely the community was just adapting to something new.
The problem is that difficulty curves alone do not capture how a fight feels. A boss that deals a fair amount of damage can still feel oppressive if it removes your agency, forces obscure rules interactions, or punishes specific archetypes disproportionately. Doormaker did all three at various points of its iteration.
Community sentiment made that disconnect obvious. Steam reviews dipped after early Doormaker patches, subreddit threads filled with flowcharts explaining phases, and a lot of discussion focused on how the fight ruined runs that otherwise felt earned. Even players who beat it consistently often described it as annoying rather than satisfying, which is arguably worse for a roguelike designed to be played on repeat.
In the end, Mega Crit took the rare step of siding with player emotion over data. The studio did not claim the community was wrong about difficulty. It instead admitted that, despite being numerically fine, the fight lived outside the experience they want Slay the Spire 2 to deliver.
Aeonglass and the Reset Button
Rather than endlessly iterate on Doormaker, Mega Crit chose the nuclear option and replaced it outright with a new Act 3 boss, Aeonglass. That choice says a lot about how the team views early access.
Doormaker had already gone through balance passes and partial redesigns. At some point, there are only so many bandages you can put on a fight whose core concept is at odds with your target complexity. Mega Crit acknowledged that starting fresh would give them more room to experiment with a cleaner premise instead of forever patching a boss many players already disliked.
Aeonglass represents a reset of expectations. It still has to challenge heavily powered‑up decks and test different archetypes, but it can do that with a narrower mechanical focus and fewer moving parts. That is more in line with how Slay the Spire 1’s iconic bosses worked: focused, legible threats that demanded different answers without rewriting the rules of the game every turn.
Community Feedback As A Design Tool
Slay the Spire 2’s early access period has been noisy. New characters, alternate acts, multiplayer and more have all landed into a passionate player base that is used to extremely high standards from the first game. The Doormaker controversy became a focal point for that friction, including waves of negative Steam reviews from parts of the community.
Mega Crit’s response has evolved over time. Initially, the team used community feedback as one signal among many, but still anchored on its datasets. Later patch notes grew more candid about frustration, acknowledging that some players simply did not find the boss fun to fight, even if it was beatable. With patch v0.105.0, they effectively turned that sentiment into a concrete design decision by removing Doormaker entirely.
At the same time, the team is trying not to be whiplashed by every complaint. The new biweekly patch cadence is part of that strategy. Weekly updates on the original Slay the Spire led to developer burnout, and constant small changes can make it hard for the community to develop stable strategies or provide clear feedback. Longer gaps between patches give time for metas to settle and for the team to see which complaints persist once players adapt, versus which ones point to genuine design misfires.
That broader context matters when looking at Doormaker. This was not an instant surrender to backlash. The boss survived balance waves, was defended publicly, and only got cut once it was clear that its core identity could not be reconciled with Mega Crit’s long‑term goals.
Difficulty, Fairness, And The Shape Of A Roguelike Run
Doormaker’s removal also raises a bigger question: what should difficulty look like in a game that is built around failed runs and experimentation?
Slay the Spire’s best encounters rarely feel fair because they are easy. They feel fair because they are understandable and, crucially, telegraphed. You see the enemy’s intent, you have multiple ways to respond, and when your deck comes up short you can usually pinpoint what you should have drafted, upgraded, or played differently.
Doormaker strained that contract. Phases that exhaust cards or prevent drawing can feel arbitrary if you do not have the right tools ready. Losing to a big multi‑hit attack after ignoring scaling is different from losing because a phase happened to strip the one card your engine needed, or because your build was uniquely punished by that specific mechanic. The former feels like a lesson; the latter like a coin flip.
For a long‑tail roguelike, that difference is crucial. Difficulty is supposed to drive replayability by encouraging you to refine lines and discover new synergies. When a boss undercuts that loop by invalidating too many builds in ways that feel opaque or hostile, it does not just end a run, it undermines the desire to start the next one.
By contrast, Mega Crit’s ongoing balance passes elsewhere in Slay the Spire 2 show what they are aiming for. Character kits like the Defect and Regent have been adjusted with targeted buffs and nerfs that shift which cards and relics are best without deleting entire archetypes. Bosses and elites are being tuned to punish different weaknesses, but the core loop of “read intent, play around it, learn for next time” remains.
The Doormaker decision suggests that any encounter which consistently breaks that loop is on the chopping block, regardless of its raw stats.
Replayability In The Age Of Early Access
Slay the Spire 2 is trying to achieve the same near‑infinite replayability that made the first game a staple for years. That means more characters, more bosses, more events, but also more chances for any one piece of content to warp the experience.
The Doormaker saga underlines a few priorities for how Mega Crit is approaching that challenge:
Preserve core systems instead of constantly attacking them. Bosses can tax resources, force awkward lines, or punish greed, but they should not frequently erase the identity of a build or turn off core mechanics for long stretches.
Keep complexity layered rather than piled on. Players can handle a lot of moving parts over the course of a run, but each encounter, especially late‑game bosses, needs a clear hook. The studio’s own “complexity threshold” language shows they want tough fights that are still readable at a glance.
Use early access to test extreme ideas, but be willing to walk away. Doormaker was exactly the sort of aggressive experiment you run when you know you have time to pull it back. Removing it proves that nothing is sacred if it does not serve the final game.
Treat community feedback as a lens, not a verdict. Mega Crit is clearly listening to Steam reviews, subreddit posts, and Discord discussions, then cross‑checking them against its metrics. Doormaker was only deleted once both the data and the ongoing sentiment pointed toward a design that was unhealthy for long‑term retention.
As new features like the Bestiary roll out and more bosses join Aeonglass in Act 3, those principles will quietly decide what stays and what gets reworked.
What Doormaker’s Fall Means For Slay The Spire 2
In isolation, deleting one boss might look like a concession to angry forum threads. In context, it feels more like a statement of intent. Mega Crit is using early access not just to tune numbers, but to refine the texture of difficulty in Slay the Spire 2.
Doormaker showed how quickly an encounter can become a lightning rod when it cuts against the grain of what players value in a roguelike deckbuilder. It also showed that a studio can acknowledge missteps without abandoning its commitment to challenge. Aeonglass is not there to make Act 3 safe; it is there to make it sharp in a way that invites more runs instead of fewer.
If anything, the removal sets a useful precedent. No matter how big or central a piece of content is, it can be replaced if it consistently makes the game worse to replay. For a series that lives and dies on “one more run,” that might be the most important design rule of all.