Fixed Heroic stats -> mod2 calculated incorrectly

Discussion in 'Resolved' started by yepmetoo, May 12, 2020.

  1. yepmetoo Abazzagorath

    This has been a bug for 4 years now, and it would be nice if it was corrected.

    Original thread on stat consolidation:

    Posted May 6th, 2016. The day the patch went live and we saw the stats, this was posted:

    The mod2s that had their caps moved from 35 to 45% are scaling properly. At 400 and every 400 interval you gain 1 point.

    The others are not scaling right. They are supposed to scale evenly from 400 to 4000 according to the post, but do not seem to be.

    Damage shield mitigation (Hstr)

    It is starting at 400 and every 160 points, but this means that it maxes at +23 above the old cap (i.e. 48 cap instead of 50) at 3920 Hstr. - It should go up every 150 points, so you have 26 at 400 and hit 50 at 4000.

    Avoidance (Hagi)

    It is starting at 400 and every 20 points you gain one, but this means when it hits 4000 it is going to cap at 281 instead of 300. - It should go up every 18 points, so you have 101 at 400 and 300 at 4000.

    Accuracy (Hdex)

    It is starting at 400 and every 26 points you gain one, but this means you will cap at 289 accuracy at 3988 dex. It should go up every 24 points, so you have 151 at 400 and 300 at 4000.

    Combat Effects (Hdex)

    It is starting at 400 and every 160 points you gain 1, but this means you will cap at 123 accuracy at 3920 dex. It should go up every 150 points, so you have 101 at 400, and hit 125 at 4000.

    This information was also PMed more than once to developers and nothing was ever changed.

    Basically, instead of using a 3600 point range (from 401 to 4000), the game is using a 4000 point range, making it impossible to ever hit the "new" caps that were put in 4 years ago since they are supposed to stop going up at +4000 to a stat.

    For example:

    You need +4274 heroic dex to hit 300/300 accuracy.
    You need +4380 heroic agi to hit 300/300 avoidance.

    Would be nice if that "4000" number could be changed to "3600" in where the calculations are for those bugged numbers.
    Kroolhand78, Skuz, Duder and 11 others like this.
  2. yepmetoo Abazzagorath

    Love to see an acknowledgement at some point on this.

    1) It will get changed
    2) It won't get changed, just can't cap them
    3) It won't get changed, but the benefit won't stop until you cap them, e.g., can get to 4380 hagi and 300/300 avoidance
    4) etc
  3. Beimeith Lord of the Game

    I would assume they actually do use a 4000 point range, which starts at 401, and thus requires you to get 4400 to cap and the original post where he said you need 4k to cap he misspoke.

    I don't think it is possible to get that high yet to confirm it?
  4. niente Developer

    Will try to find out about this when things are less busy.
    Skuz and yepmetoo like this.
  5. yepmetoo Abazzagorath

    Several of them cap out at 4000 (like shielding, spell shield, etc), those all work as advertised with 400 point intervals and hitting +4000 should get you to 45%.

    But its really just a coincidence off the fact its 10 into 4000, and they give you the first +1 at 400.

    Now, to be fair, if they did it consistently, there would be a nerf range as well as a much larger benefit range (and we could at least cap everything when we do hit +4000 in a few years).

    To make for less raging, leaving the % mods as is with the 4000 numerator may be a better idea, as they don't even out between how it is versus how it was advertised, until exactly 4000. But the others equalize WAY sooner (and, to be fair, they give more benefit than the % ones anyway).

    Excel doesn't paste into the forums right, so let me do a screen shot or something.
    Wulfhere likes this.
  6. yepmetoo Abazzagorath

    Wulfhere likes this.
  7. yepmetoo Abazzagorath

    Also, could still correct to allow them all to hit max cap at +4000 while starting +1 at +400, but would require making the intervals be non-even. For example, if accuracy was 151 at 400 hdex, you would be +24 hdex per +1 accuracy, but every 24 points you'd have to go to +25 hdex on that 24th one.

    So that would make it more manual, so would depend on how they calculate in the first place. If its a lookup table (doubt it) that would work, but a calculation might not work, unless you truncate or round, so still clunky.
  8. svann Augur

    Less busy? Is there something exciting in the pipeline besides the normal bug fixing and etc?
  9. Beimeith Lord of the Game

    Server merges and new servers? And probably work on the next expansion.
    RPoo likes this.
  10. yepmetoo Abazzagorath

    Small bump, so this doesn't get lost in all the server issues. Really would like to see this fixed/answered ultimately.
  11. Meeko Developer

    This has been fixed internally and should go out in the next update. There were a couple issues affecting how Accuracy, Avoidance, Combat Effects, and Damage Shield Mitigation were being calculated. The other stats that cap at 45 were working correctly.

    The formula for determining how much of a heroic stat is needed for one point of the corresponding mod2 is:
    3600 / (Max Stat - Min Stat - 1)

    Accuracy for example works out to:
    3600 / (300 - 150 – 1) = ~24.16 points of hDex per point of Accuracy.

    A player with 2000 hDex will have 217 Accuracy. This breaks down to:
    +150 from the first 399 hDex
    +1 from the initial point at 400
    +66 ( 1600 / 24.16 ) from the extra hDex over 400.

    Once live, you’ll see a slight increase to these stats depending on what your current heroic value is.
    At 2000 hDex, Accuracy will now be 217 instead of 212.
    At 2000 hAgi, Avoidance will now be 189 instead of 181.
    At 2050 hDex, Combat Effects will now be 112 instead of 111.
    At 2050 hStr, Damage Shield Mitigation will now be 37 instead of 36.

    The tooltip when hovering over your current stat was also updated to match the correct values.
  12. Cragzop Cranky Wizard


    Now hopefully in your work you noticed that casters get diddly from heroics and that will be the next thing you work on. Will not be holding my breath on that though...
  13. kizant Augur

    It's nice to see bugs like these getting addressed.
    menown, yepmetoo, Lophophora and 3 others like this.
  14. yepmetoo Abazzagorath

  15. CatsPaws Devil's Advocate

    Whooo are Yooo Meeko?

    Your name is in red yet your page profile is blocked. Much like Accendo's was when he first started.

    And also like Accendo - your posts cannot be found in staff tracker.

    You joined May 21 of this year.

    Not sure why you have "racoon" where a red name would have their job description. I did not get a chance to apply for the job of "racoon" ???? whats with that?;)
    Sirene_Fippy likes this.
  16. Soulbanshee Augur

    The red name is a forum role display likely tied to the Developer title, and based on past the staff post tracker is a manually curated filter that someone has to update or trigger a change on, and is usually forgotten for new red names.