I come here today to share some importaint information with you and have a chat about it. Ive searched and couldnt find this specific topic before.
Basically +healing scales wrong with improved HOT’s (healing over time) spells.
Let me set up a scenario:
2 Druids, both with 3/3 Improved Rejuv talents, none with the t2 set bonus.
Druid 1 has 600 +healing, Druid 2 has 700+ healing.
Druid 1 casts rejuv on the tank, works like a charm. Druid 2 doesnt see this and casts rejuv, it overwrites the previous one (as it should).
Now druid 1 wants to cast his Rejuv again, he cant! Whay? It says a more powerfull spell is already active.
The only difference here is the +healing. Talents are the same and none has the t2 set bonus.
Our priests are experiencing it with Improved Renew aswell.
Is that how +healing is intended to work with HOT’s? I seem to remember the only thing not allowing you to overwrite HOT’s was improved talents or the set bonus.
Am i remembering wrong? Are you experiencing this aswell in your raids?
TLDR:
You cannot overwrite an improved HOT, if the caster of said HOT has more +healing then you do. Even with the same talents and skill bonuses!
EDIT:
After some more diggin and talking to random folks, i found this:
"Healing overtime effects didn't stack. For druids this meant that when you tried to cast rejuvenation on a tank where another druid with higher spell power had his rejuvenation, you would get "A more powerful spell is active."."
It seems I was indeed remembering wrong.
EDIT2:
After more digging, i found another site supporting the idea that it was like this in vanilla: Only one druid could put a HOT on the target, so the druid with the most spell power could put a HOT on their targets (otherwise, you got an error message “a more powerful spell is active” or yelled at)
This is how the game functions in vanilla since you can only have one type of hot on you at any time. The lower +healing Druid will not be able to cast a rejuv on a target that the higher +healing Druid has already cast their rejuv on.
Hmm i cant seem to find any information to confirm that it was like that in vanilla and i dont remember it being like that.
Do you have a source somewhere?
EDIT:
I found some more info hidden away om Github, the OP has been edited.
I find that source very dubious. It links a dead forum post as a source. Judging from the date of the github issue this post was linked in 2014. By then the original vanilla forums were already gone, so this quote is very likely just some player saying what he thinks it used to be about 8 years after the fact. I don’t think you can draw any conclusion at all from the linked issue.
For what it’s worth, my memory lines up with what you first described, though I’m absolutely not willing to state that for a fact.
Im not sure at all.
The github i linked seems to be an old issue on some private server. Dont know much about private servers, but i assume people were full on doing them in 2014 and this group “cmangos” seems to be rather big in the private community and have alot of different WOW DB entries on github.
I dont remember it being like this, but i cannot find anything else on the topic.
You’re overthinking it.
We already know Classic was made with the original Vanilla data they still had left as reference, so in essence they could look at the way the game was coded back then on one screen as they rewrote a lot to function in Legion’s engine, which Classic uses, on another screen.
So you can infer from the way it behaves in Classic to be like how it was back then.
Classic was made by mashing the “most complete database” from vanilla into the Legion client and hoping it worked well enough to play the game and some things slipped through, in that process.
Im just trying to verify if this was actually in vanilla, because i dont remember it at all and i cant seem to find a whole lot of information supporting it, other then that private server issue from Github.
EDIT:
I managed to find another source of information about this, OP has been edited.
Only one druid could put a HOT on the target, so the druid with the most spell power could put a HOT on their targets (otherwise, you got an error message “a more powerful spell is active” or yelled at).
Link in OP.
Uuh no, they had the actual patch 1.12 still left in storage. The complete game. Just like many other game companies stores their games. This wasn’t normal to do for the non-console game companies until around a decade ago though.
The problem is that they didn’t store any of the versions of Vanilla prior to patch 1.12 however, which is what has been the source of a lot of grief in terms of compromises.
The pserver community are the ones who had to search all over the web for anything they could find to create the first pserver though. They also used a lot of what they themselves remembered, too.
Which is what made them unreliable for some things, like proc rates, drop rates and so on. Because they never had access to the actual game itself. It was just the raw engine.
It’s also why the feat of creating pservers from scratch like that is so incredibly impressive.
They recreated the systems in the latest server software. Whether or not hots overwrite based on spellpower is a software decision that isn’t in the database they copied. Systems like that have to be manually verified and the code for them has to be written if the old system differs from the new system. It’s very easy to miss a detail like this, it working like this currently in classic is not solid proof that it used to work like that in vanilla.
It did work like this in vanilla. I was there and played it. Why do you need an “official source” to believe it?
The sky is blue and grass is green. Not everything needs an official source.
Working as intended. It was like this through the entirety of classic as they worked in the same way as buffs. A weaker buff cannot override a stronger buff even if the stronger buff has 1 second duration left.
Also using a trinket to temporarily buff spell power and casting a hot will cause your unbuffed hot to fail to cast due to “a more powerful spell” being on the target.