you’d think if someone was DOOMED they’d take more than 2-4k damage
Because balance.
Because of a mixture of factors:
- It’s in a talent row with a fairly low damage budget.
- It also gives you value in the form of Shard Generation
- It’s damage is balanced around the idea of it having a 20s tickrate
If we keep balance in mind we could juggle numbers around, increase the time it takes to tick and with that allow more damage per tick, even shard per tick, the spell event would “feel stronger” but take more time to tick, be less userfull, and with that have it regarded as weaker.
Truth is, while you are right that some names of spells have more “impact” than their effect suggest, there is a point where the game needs to care more for health and balance of it as a game than for the Lore aspects of spells.
Could you imagine if Fire spells couldn’t damage Fire elementals, Warriors Execute actually decapitated player characters, or Rogues poison didn’t work against Forsakens? the same is in regard to Doom.
Could it deal slightly more so its more balanced in relation to Demonic Calling? For sure, but that don’t mean it would go from 2-4k to 5-10k, but more like a 4% increase in it’s damage.
Could it’s effect summon a Imp instead of giving a shard, reducing the chance of shard overcap? 100%
But changes like bringing it back to tick once every minute so we could triple it’s damage would actually make it a weaker spell who is even less likely to be used.
and Changes like tripling its damage while keeping the current tickrate…well, that wouldn’t be balanced.
Now…if the name is a problem, and you want to be a little funny on the side of puns…
Here is my suggestion, makes so that it summons a Imp instead of giving a shard and rename the talent to IMPending Doom.
Doom has fallen a long way from when a tick could do 5-7% of Netherspite’s HP back in TBC. If it wasn’t constrained by talent budget considerations (ie it was baseline), I could see a world where it did a reasonably heavy amount of damage after 10 sec with a 1 min cooldown (with whatever appropriate secondary effect) to evoke some of its old grandeur.
It’ll probably just stay dead though like GoS, so oh well.
It’s impossible to run away from budget considerations, if it was baseline it would eat away from baseline budget instead, so you either make it very strong and the cost of making other aspects of the core kit weaker or you make it weaker so it don’t impact other stuff.
Shadowlands beta had a baseline Curse of Doom who ticked on a 1 min basis, with a talent that improved it by doubling its damage and making it tick 50% faster(30s tick) and i have no shame in say that every single feedback i gave on beta was to remove it from baseline.
Personally, i feel like Core Demonology without traditional dots in its rotation is at its best, and making part of its rotation Doom by default isn’t rly nice.
Do also note that https://tbc.wowhead.com/spell=30910/curse-of-doom in TBC took 5x longer to tick and existed under snapshotting, meaning you could fuel snashotted procs inside it.
I mean yeah, if it was baseline it would eat into baseline budget and you’d lose something from elsewhere; no free lunch and all that. My point wasn’t really to suggest a change to demo but simply illustrate possible alterations that would have to be made to the spell if Blizzard was hellbent on implementing it in a form that bore some semblance to Doom back when you could turbo charge it with snapshotting.
I’m not really a fan of the current demo, but I know some are, so I have no interest in disrupting what they like (I’m not Blizzard after all).
Why does Curse of Doom suck?
Because as Malacath says, it’s a Shadow Bolt on a 20 second tick.
Seriously, this talent needs help and time has not been kind for it.
To be fair, it sees some uses in situations like mage tower where you can’t cast a lot at the end due to a lot of movement or in pvp, where its a decent shard generation who don’t risk you getting shadowlocked.
And that row isn’t very kind to it, as the low budget on the row don’t allow it to be a whole lot stronger.
the way i see it, a slight buff to it, maybe even making it a 1% higher single target than Demonic Calling in sims would be Ok for the people who rly like to play Doom to play it without feeling bad over it.
The Imp spawn thing would be better in pve as you wouldn’t need to worry about shard capping or akward timings, but not sure how it would be on pvp (as 1 imp is less value than 1 shard)
I wouldn’t mind it having a (small) niche, but I don’t think that niche should be single target.
And yes I kind of think it should do something other than generate a shard. Delayed shard gen is just another thing to track that will mess with the flow of the spec.
Technically, it does have a extremely small niche of giving Demonology Spread-Cleave.
But it’s more around the damage you deal with it (the 175% spell power), than the soulshards you generate(who are pretty close to the shard generation of a Shadow bolt 1SS for 1 GCD of 1,5s reduced by haste vs 1 SS for 1 cast of 2s reduced by haste).
oh yeah, also, no other talent or spell in demonology deals spread-cleave so it kind of wins by default on spread-cleave.
Then you have things like Soulshard maximum limit being 5 (so Doom on 10 targets will waste Soulshards), Soulshard damage value being a lot higher in AOE (so 175% spell power is less impactfull), the Delayed Shard (meaning you can gain a shard who will end up not being used) and overall the idea of high resource flow the spec plays around (meaning you can get 1 Shard generated by Doom while you are already generating 1 Shard by DB/SB or Tyrant)
Who all makes Doom rly struggle with multiple stacked targets.
And a lot of the solutions would basically make it overbudget for the talent row.
- Dot doesn’t hit that hard.
- Waiting for dot to tick is way too long and only tick once.
- Chance to summon a doomguard is impossible because dot had to killed the target and proc is very low.
there is no chance to summon doomguard anymore…actually, even when it “existed” in the tooltip i am pretty convinced it wasn’t coded as i never seen any evidence of anyone proccing it and i have tried to proc it sooo hard.