I propose to completely remove the debuff and buff limits.
Arguments For Removing Buff/Debuff Caps :
Historical context: The debuff andbuff caps were hardware and engine limitations of 2004, not intentional design choices.
Class equity: Allows Warlocks to cast all curses, Hunters to use Hunter’s Mark, and Druids/Priests to use damage-over-time spells without griefing raid members.
Healing freedom: Prevents Resto Druids and Holy Priests from being penalized for using Healing over Time (HoT) spells like Rejuvenation or Renew, which otherwise eat up vital buff slots.
Quality of life: Eliminates the annoying need for “cancel aura” macros and stress over accidental spell overwrites.
Removing it would increase build diversity and make the game more enjoyable by:
Allowing more class variety in raids
Letting players use their full ability toolkit
Reducing the need for complex debuff coordination
Making certain specs more viable without hurting overall game balance
Posted from the Council — voting happens there; discuss here.
The buff/debuff limit creates a condition in which You Can’t Have Everything At Once … which then promotes a circumstance of tradeoffs. In a LOT of game designs (not just this one), being able to Have It All is actually a Bad Thing™ in the long run.
Reason being that once you CAN Have It All you’ve “beaten” the game … so go find something else to do.
In a lot of ways, the rationale behind this viewpoint/perspective is the same one that says you can’t pick every talent from all 3 trees for your character. Once you can Have It All the game becomes boring.
Now, I would hardly expect such arguments to sway the min/max gamer crowd … but I would expect any Game Designer (worth their title) to recognize the hazard.
A different argument against removing the buff/debuff limit comes down to Power Creep … and the inevitable surrender to it. The more debuffs can be thrown at a target, the “quicker, easier, more seductive” the kill. What once was a CHALLENGE turns into a speed bump (if that). That’s because the more powerful the PCs get, the less rewarding the victories they achieve (thanks to Power Creep) become. Player SKILL and Coordination fall by the wayside … because you can, quite simply, Have It All … in ways that are BAD for the long term health of the endgame, and the community of Players who continue to show up for it over the long haul.
When there are no choices about compromises to be made … you can “beat the game” and put it on the shelf, because You’ve Done It ALL.
You argues that the cap creates interesting compromises. In reality, it does the exact opposite by completely deleting entire playstyles and classes from the game.
It destroys class design, not “completes” it: Comparing the cap to talent trees is a false equivalency. Choosing talents is a personal design choice. The debuff cap simply tells a Warlock they cannot use Corruption or a Shadow Priest they cannot use Mind Flay. It forces players to not use the core abilities printed on their character sheets.
The illusion of choice: There is no “tradeoff” decision-making happening here. Min-max culture completely solved the cap years ago. Raid leaders dictate exactly which debuffs are allowed (Sunder Armor, Curse of Recklessness, etc.). The “choice” isn’t a fun tactical compromise; it is a rigid, mandatory checklist that forces everyone else to play a boring, stripped-down version of their class.
Artificial friction vs. fun: Good game design creates challenge through engaging boss mechanics, positioning, and phase transitions. Bad game design creates challenge by having a hidden UI limitation silently delete your teammate’s world buff because you pressed Renew.
2. The “Power Creep & Lack of Skill” Argument
You argues that removing the cap makes the game too easy and ruins the challenge. In reality, WoW Classic’s difficulty is already trivial, and the cap actually stifles individual player skill.
Classic bosses are already “speed bumps”: The idea that the debuff cap is the thin line defending WoW Classic’s “brutal difficulty” is historically inaccurate. Bosses in Molten Core and Blackwing Lair already die in under 60 seconds to modern optimization. Removing the cap doesn’t suddenly make a hard game easy; it makes an already easy game more fluid and satisfying to play.
Enabler of individual skill: With the cap removed, coordination changes from “don’t press your buttons” to “execute your full rotation perfectly.” It allows damage-over-time classes to actually manage their resources and maximize their personal output, which requires more active engagement and skill than just spamming a single filler spell (like Shadow Bolt or Frostbolt) for an entire raid night.
Fixing the “Power Creep” organically: If a game designer is truly worried about power creep from removing the cap, the solution is simple: slightly tune the bosses’ health pools upward to compensate. This keeps the intended challenge alive while allowing players to fully enjoy their classes.
“The buff/debuff cap isn’t a clever game design restriction like talent trees; it’s an outdated 2004 hardware limitation. It doesn’t create ‘meaningful tradeoffs’—it just tells half the classes in the game that they aren’t allowed to press their favorite buttons.”
It was analogy, not an equivalency.
I was pointing out the congruent parallels, rather than the perfect symmetry.
So the “problem” is the Raid Leaders having dictatorial power over who can do what when. That’s a SOCIAL problem, rather than a game mechanical one (albeit it’s a social problem that’s rooted in how the game mechanics enforce limits).
When “more fluid and satisfying to play” means that Bosses in Molten Core and Blackwing Lair can be made to die in under 40 seconds using modern optimization … I guess you could say that’s … progress …?
I would actually argue that you’re on to something, but perhaps moving in the wrong direction here (or in the right direction, but overshooting the mark). Let me see if I can adequately convey what I mean by that.
If you just open things up to a free for all (no limits) … “dogpile on da wabbit” … the “already trivial” will just become even more trivial.
An alternative solution, which would require new and novel scripting to make it work (go figure, eh? ) would be that each member of the raid gets ONE debuff slot reserved for them personally … but then the there are a limited number of “extra” debuff slots for the raid collectively (which is basically the status quo ante, when you think about it). So the modification would be that everyone gets a SINGLE debuff slot “guaranteed” … but anyone who is putting on 2+ debuffs needs to “compete” for the remaining LIMITED debuff slots.
Such as system would favor cooperation/coordination (still) to optimize who is applying what debuffs, but you would be able to avoid a situation where raid members get ZERO debuff slots allocated to them.
I’ll leave arguing about the cap limit on “group” debuff slots for another time. Right now, I’m merely interested in the structure of a possible alternative solution, rather than going to the mat for specific numbers on limits.
However, in terms of implementation of such a Feature Request™ as the one I’ve outlined … that would require some pretty novel coding in order to implement such a method for handling debuff slot allocation limits.
The problem there is that you’re basically seeking a New Balance Point™ for the game. Throw out the old baseline … to make way for the new baseline.
Also, Bigger Bag of HP™ is a really lazy/hackish way of trying to work out a balance point as a game designer. It’s basically a “make everything do 2x the damage and 2x as resistant to all damage” as an attempt at a solution.
Hence why you need to do a kind of “restructuring” to solve the problem (as I’ve outlined above), rather than just tearing down the guardrails and demanding applause.
Breaking Stuff is EASY.
Making Stuff BETTER is … hard.
I think you’re overengineering a solution to a problem that has a much simpler cure.
Your alternative system—guaranteeing one slot per player and creating a competitive pool for the rest—sounds interesting on paper, but it doesn’t solve the social issue you mentioned. Raid leaders would still dictatorially control those “extra” slots, and players would still be flamed for accidentally overriding a priority debuff. It replaces an outdated hardware limit with an arbitrary mechanical headache. Breaking stuff to make it better doesn’t mean we need to make it convoluted.
Regarding the bosses dying in 40 seconds instead of 60: honestly, does it matter? Vanilla bosses are already trivial. The goal of removing the cap isn’t to preserve a non-existent tactical challenge; it’s about modern engagement. Spanning a single button for 60 seconds is boring. Executing a full, satisfying rotation for 40 seconds is fun. We should optimize for player enjoyment, not for dragging out a fight.
Finally, raising boss HP to compensate for the DPS bump isn’t “lazy design”—it’s standard tuning. We saw this with Season of Discovery and Somnus/Classic scaling. It’s an organic way to let classes play at 100% of their intended design without shattering the game’s pacing.
Removing the cap isn’t just “tearing down guardrails.” It’s removing a literal 2004 server-memory restriction so that the game can finally flow the way modern players expect it to.
) would be that each member of the raid gets ONE debuff slot reserved for them personally … but then the there are a limited number of “extra” debuff slots for the raid collectively (which is basically the status quo ante, when you think about it). So the modification would be that everyone gets a SINGLE debuff slot “guaranteed” … but anyone who is putting on 2+ debuffs needs to “compete” for the remaining LIMITED debuff slots.