@omar please respond
https://us.forums.blizzard.com/en/wow/t/bug-instant-attack-normalization/200006/7
Omar isnât the QA lead. You want Aggrend.
I heard they responded and are fixing this!
That would be the link
This is truly a great find, I have been wondering for a while now much of the classic servers coding is really just retail code mixed in. They may have the 1.12 data, but I havenât heard anything about them having the original servers to run it on. We only hear about their makeshift 1.12 server they use as a reference for the classic servers. At least they have already announced that they are investigating this issue, witch is very reassuring. Keep up the good work.
They didnt say they were investigating they said they have a fix, which is not suprising since it should be a very easy fix.
They have a reference server that is presumably located on a private network in the Blizzard Campos where they compare numbers from the live client. To put it another way the have a full running version of 1.12 with all the data.
This post is classic confirmation bias
Mana Regen appears to be tracking with the expected values after level 20. Before level 20, itâs slower.
So if youâre making a case for the âItâs too easyâ because theyâre using Legion/BFA numbers on mana regen, youâre barking up the wrong tree.
Do you have a reliable reference for how they behaved in 1.12?
Do you have a suggested methodology for testing it? (that can be compared against a reference ideally)
Blind testing is blind testing, if we donât know what the results are supposed to be, the results donât do much.
Iâm personally holding off on testing +damage and +healing scaling until I have use of gear that does more than +10 in total. Of course, my preference for raw stats for the lower levels instead also helps keep that test at bay for me in beta.
Iâm not particularly eager to do the number crunching involved in coefficient results that fall inside the ânoise levelâ(/range) of the spell being tested. Thatâs not just a simple matter of âcast fire ball three times and record the numbersâ when it has a range it can hit for which is much larger than the predicted increase in potency.
Youâre talking about dozens of casts that need to be made both before and after equipping the relevant gear. In order to get a feel for the actual damage range is. Lack of a training dummy(introduced in TBC) makes it that much more âfunâ to test.
Basically itâs probably on the list for a quite a few people to âget around toâ but theyâre hoping somebody else will test it before they do.
What I am talking about is how when a warlock goes from level 1 to level 2, his rank 1 shadowbolt goes from doing 12-16 damage (in the tooltip) to 12-17 damage (in the tooltip) and in actuality the damage does go up.
From my memory, ranks of spells should not have their damage scale up based on character level, but remain static. I could be wrong, but I donât recall this as how it was.
I would not pretend it is insignificant. A warriorâs execute doing 1000 base damage would do either 3300 in a Vanilla-based system, or 3600 in a Legion-based system. Thatâs rough math, too, and not counting anything like contribution from strength, AP, weapon skill, talents, etc.
What about your skills and attributes going up? Remember, Classic now has, for example, âYour skill in Balance has increased to 10,â and âYou gain 1 point of Intelligenceâ on level-up. It could be that.
But on vanilla, intellect did not give spell damage, only more mana and more crit chance.
How the increase in spec skill works I have no clue. I just remember spell damage being static across all levels, and would like it checked.
I never checked, actually, and I played a Mage in PvP grind. I used to down-rank spells all the time but never paid attention to what the damage ranges were on them, or how they related.
Stuff started scaling in 2.0 and after.
I asked someone to check pet attributes because they are supposed to be static per level in 1.12. They started scaling in 2.0.
So far no one has volunteered to do that.
Is it using modern numbers or simply the way the new client processes those numbers.
Remember, this is not a 1:1 conversion. The codebase has changed tremendously over the years. And they did say they are trying to get as close as possible.
Does not make this invalid, just food for thought.
In this case it was using Legion numbers.
Someone fix this. . My fellow dwarf, Brokthorn is making himself sick over it!!
More than likely, hold on to your helm my friend, its BFA figures. The code base, unless my memory is completely foggy, is not just a straight fork. They have to stay pretty close to the base branch to keep up on security patches and stuff. backporting would be a pain down the line.
Sorry for that news
DudeâŚit is fixed. Go read the beta forum.
and it was legion numbers, not BFA numbers.
Read the bug report in the beta forum.