we did sir we did.. But he kept on saying even retail is bugged thus any source from it isnt viable.. Even when all top guides are saying so.. idk what else to show.. Even the formula from retail is "bugged"
'); document.write(''); var yuipath = 'clientscript/yui'; var yuicombopath = ''; var remoteyui = false; } else // Load Rest of YUI remotely (where possible) { var yuipath = 'https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build'; var yuicombopath = ''; var remoteyui = true; if (!yuicombopath) { document.write(''); } } var SESSIONURL = "s=3b2cc6753a10f5cdc79c6d14a86ca195&"; var SECURITYTOKEN = "guest"; var IMGDIR_MISC = "warmane/misc"; var IMGDIR_BUTTON = "warmane/buttons"; var vb_disable_ajax = parseInt("0", 10); var SIMPLEVERSION = "422"; var BBURL = "https://forum.warmane.com"; var LOGGEDIN = 0 > 0 ? true : false; var THIS_SCRIPT = "showthread"; var RELPATH = "showthread.php?t=331565&p=2701141"; var PATHS = { forum : "", cms : "", blog : "" }; var AJAXBASEURL = "https://forum.warmane.com/"; var CoTTooltips = { rename: true, icons: false, iconsize: 15, qualitycolor: true, overridecolor: { spells: '#839309', items: '', npcs: '#fff', objects: '#fff', quests: '#ffb100', achievements: '#fff' } }; // -->
we did sir we did.. But he kept on saying even retail is bugged thus any source from it isnt viable.. Even when all top guides are saying so.. idk what else to show.. Even the formula from retail is "bugged"
What I said is that tooltips can not be trusted and that you should find some real evidence (other than text).
What you need to do is to say if it should work as v1 (top part, as it currently does) or as v2 (the bottom part)
Edited: May 26, 2016
I strongly believe it should be as v2, which fits the tooltip from blizzard and online retail guides
Edited: May 26, 2016
is this thread real? it is so easy to know how should work, just check a random video from retail 5.4.8: https://www.youtube.com/watch?v=jeI10XjdUSo
He explains pretty well how all affli spell works, at 1:43 he shows agony and it does more dmg already at stack (2) on dummy.
Am I mising something or it was so easy?
Edit: just to help to understand how the dmg is increased, here is the dmg done by each tick on dummy:
1. 3360
2. 5040 (3360*1.5)
3. 6719 (3360*2)
4. 8400 (3360*2.5, it is not showed on video because of zoom-in)
5. 1080 (3360*3, On video it critted so it is showed as 20158)
6. 11760 (3360*3.5)
7. 13440 (3350*4)
8. 15120 (3360*4.5, On video it critted so it is showed as 30237)
9. 16800 (3360*5)
then the clip has been cutted but the next tick should have been:
10. 18480 (3360*5.5)
Edit: I made a mistake, there isn't an increment at tick (10), so the max tick dmg is 16800, not 18480
Edited: May 27, 2016
Ty skullbashat for explaining . So the agony is completly buged here , the dmg is also incorrect. The dmg on 10 stacks should be higher. Hope they fix it soon :D
Can you explain in more detail?
How did you find out that something is wrong?
Can you explain what part of anything was nonsense?
just to explain better, becuase I made a mistake on latest post by thinking tick number 10 would have done more dmgs:
1. 3360
2. 5040 (3360*1.5)
3. 6719 (3360*2)
4. 8400 (3360*2.5, it is not showed on video because of zoom-in)
5. 1080 (3360*3, On video it critted so it is showed as 20158)
6. 11760 (3360*3.5)
7. 13440 (3350*4)
8. 15120 (3360*4.5, On video it critted so it is showed as 30237)
9. 16800 (3360*5)
there isn't any increment at tick (10), so the max tick dmg is 16800, not 18480 as I said before by mistake.
This is clear at 4:41 of the video, in fact the agony's damge are:
(buffed by 5% because curse of element or whatever is called in MoP)
1. 3527 (it is not showed because he cast agony 2 time in raw, so it goes soon to next stack)
2. 5290 (3527*1.5)
3. 7054 (3527*2)
4. 8817 (3527*2.5)
5. 10581 (3527*3)
6. 12344 (3527*3.5)
7. 14108 (3527*4)
8. 15871 (3527*4,5)
9. 17635 (3527*5)
then agany's tick keep doing 17638 as max dmg, so the tick number 9 is the one with (10) "stack power"
Which means the first agony-tick the lock does on Target alredy has the "stack 2 power".
So this is the real tick sequence: ( I am considering the example with 5% dmg bonus of curse of element)
tick 0. 1763 (Basically the lock never see/does on his target the real "base" single tick damage)
tick 1. 3527 (stack 2)
tick 2. 5290 (stack 3)
tick 3. 7054 (stack 4)
tick 4. 8817 (stack 5)
tick 5. 10581 (stack 6)
tick 6. 12344 (stack 7)
tick 7. 14108 (stack 8)
tick 8. 15871 (stack 9)
tick 9. 17635 (stack 10)
tick 10. 17635 (stack 10, same as previous)
tick 11. 17635 (stack 10, still same as previous)
...
...and so on...
Edited: May 27, 2016
This is how a report is properly made. Video evidence of retail.
Tooltips are not good for reporting bugs.
Assuming the formula is correct, Agony will get nerfed... lol
Sooo BlueAo where are you now when someone got the numbers and the damage calculation formula(the main part of it)?
actually I didn't show the base Agony Formula damage, even tho it must not be that hard to calculate it thanks to that video because the player show also his stats at begining.
What I showed with my previous posts is how the agany stack should work, which is exactly how any other stack in the game.
So "stack 2" = x2, "stack 3"= x3 and so on.
I also explained that the first dmg tick done by Agony should be with "stack 2 power" as I explain on the my latest post
This is what I meant by main part of the calculation (how it goes from stack to stack), the other part is as blizzard love to write it "xxxxx% of spell power + xxx% of something + xxxx something else"
Wait, shouldnt you or any other Staff Member check something if its bugged or not? I mean isnt that your job? I wrote about 3 tickets and 2 reports in the bug tracker about Master Pet Tamer missing, and still I get no answers.