Page 3 of 9 FirstFirst
1
2
3
4
5
... LastLast
  1. #41
    Yeah, it seems the theoretical gain becomes lower the better gear we get. At least for your overall DPS % wise. I think it's safe to say that we should hit cap when we get close to BiS. If we take a proper APL into consideration it becomes even more obvious.

    I'll try run some simulations for lower gear levels later to see how much of again it is and if we should keep recommending it for people who believe they can handle it.

  2. #42
    Quote Originally Posted by Harsesis View Post
    On Windlord if you are CCing you are hitting at most 6 targets. This is not enough targets to make Seed spamming effective. At that point it is the highest dps to pick 3 targets and focus on them.
    Took a quick look at my inbuffed damage. Agony is the only spell that has higher dpct than SoC in this situation, so I think best would be SB:SoC for Corruption, SoC spam, spending shard procs on SS:SB, manual Agony for targets for which you don't have shards. Do you have math that shows otherwise?

  3. #43
    Quote Originally Posted by Harsesis View Post
    On Windlord if you are CCing you are hitting at most 6 targets. This is not enough targets to make Seed spamming effective. At that point it is the highest dps to pick 3 targets and focus on them. If you have 1 of each pack available use those and you will do the most effective dps.
    It was just an example of a fight where SoC spam is the highest in this tier. I've never been doing it because it doesn't make the fight easier to pad your DPS on targets that are not being focused (man it was a bitch explaining this to my guld when they thought Affli lock was worse than other classes just because I was lower on the ovreall DPS). I just know other Warlocks have had a high % of their damage coming from SoC.

    If it's a bad example we will need a better one to show at which point haste will pull ahead of mastery with the argument being SoC spam.

    To be completely honest I added this because it's been recommended by other people. I've never even bothered checking this myself because I never felt the need to figure it out. Our guild never struggled with enrage timers on a fight where it could've been an option to get more haste for SoC.

    Extra ticks of Agony mean nothing as if you let Agony fall off you made a mistake.
    There will be times where Agony will drop so it's completely situatonal. Just take Wind Lord as an example. If you keep Agony up on all targets and then a set of adds die you will devote all your DPS to the boss because of the damage taken increase debuff he gets.

    We're not going for 6637 haste purely for Agony, though. The next UA tick is at this level. Another dot we might put up but let drop in multiple target situations.

    I tend to gem this way but I don't always go for socket bonuses. For example a blue socket is not worth going for the bonus if the bonus is something like 60crit. I don't remember what item it is but I had it at one point.
    The gemming part is meant to be purely a guideline. If people know they can get more from ignoring a socket bonus they probably don't need the advice given in the first place. I can reword this though if it's unclear in the first post.
    Last edited by Bonkura; 2013-01-05 at 01:03 PM.

  4. #44
    I recently abandoned the 4717 haste threshold and did some reforging and simcrafting to find the best haste-mastery ratio for me to play with. SimCraft tells me i get the most dps at 7726 haste and 4679 mastery rating:

    My armory: http://eu.battle.net/wow/en/characte...ypsez/advanced

    I cannot explain those particular numbers but perhaps they help you get to the bottom of this nasty affliction spec Xelnath forced on us

  5. #45
    Quote Originally Posted by luckydevours View Post
    I recently abandoned the 4717 haste threshold and did some reforging and simcrafting to find the best haste-mastery ratio for me to play with. SimCraft tells me i get the most dps at 7726 haste and 4679 mastery rating:

    My armory: http://eu.battle.net/wow/en/characte...ypsez/advanced

    I cannot explain those particular numbers but perhaps they help you get to the bottom of this nasty affliction spec Xelnath forced on us
    That seems extreme and impractical for any non-multi dotting fights, though you have pretty good gear so I don't know, I just feel like there's something wrong with the current SimC but I can't provide any reason for it to be and not be fixed already so I guess just gotta roll with it. :L
    Last edited by Kink; 2013-01-05 at 06:50 PM.

  6. #46
    Well, this is why it would be nice to have a SimC Warlock developer on the forums. Or at least someone dedicated with the knowledge who can figure out these results.

    What SirFlipper brings up on previous page is interesting. Trying to figure out how SimCraft handles haste plateaus is something we should've done long ago. The answers to this just never seem to show up here.

  7. #47
    Quote Originally Posted by Palmz
    There was a lot of confusion with people bringing up top warlocks not being at the hit cap at the beginning of the tier but with Exp and Exp gems not showing up on the armory and Orc's having the wand off Elegon, it looked like they weren't capped but in actuality they were. The hit cap is still very, very important.
    There is alot of confusion when people bring up hit capped warlocks from WoL at the moment, because there is no perfect method of telling what their dps would have been with different reforgings.

    Quote Originally Posted by Palmz
    I've brought it up before in past discussions so in a nut shell I will say this. Missing one Haunt, especially in a period where you are running highly modified DoTs, under Hero/Lust is a terrible damaging loss. It's damage lost from preemptively setting up a good line to spam MG's and take full advantage of the time these DoTs are up, especially in a period where you are required to do burst damage.

    I made two simc logs that have a Haunt hit/miss during a BL. I look at the Haunts fired at ~0:30 so there is only BL and no DS and many procs have run out. Also there is only one shard remaining so both locks can only cast MG during the next 8 seconds. It would be different to have the non-capper use another Haunt because then he has shorter MG time during BL and one less Haunt outside BL so to speak.

    Stats used are

    non-cap:

    gear_intellect=16041
    gear_hit_rating=2969
    gear_crit_rating=2222
    gear_haste_rating=6808
    gear_mastery_rating=5958

    hit-cap:

    gear_intellect=16041
    gear_hit_rating=5100
    gear_crit_rating=2222
    gear_haste_rating=6808
    gear_mastery_rating=3827

    It might look bad in this thread, but I should not get any of that hit from haste, or the logs would have events at completely different places.

    Here is non-cap
    Code:
    16.507 Warlock loses relic_of_yulon
    17.383 Warlock performs soul_swap (164345)
    19.458 Warlock gains jade_spirit_1 ( value=0.00 )
    
    29.903 Warlock haunt hits Fluffy_Pillow for 0 shadow damage (miss)
    29.903 Target Fluffy_Pillow avoids Warlock haunt (miss)
    30.060 Warlock agony ticks (14 of 33) Fluffy_Pillow for 18360 shadow damage (hit)
    30.060 Warlock corruption ticks (14 of 22) Fluffy_Pillow for 15533 shadow damage (hit)
    30.158 Warlock unstable_affliction ticks (14 of 22) Fluffy_Pillow for 16943 shadow damage (hit)
    30.298 Warlock malefic_grasp ticks (2 of 4) Fluffy_Pillow for 10087 shadow damage (hit)
    30.298 Warlock agony ticks (14 of 33) Fluffy_Pillow for 13770 shadow damage (hit)
    30.298 Warlock corruption ticks (14 of 22) Fluffy_Pillow for 23998 shadow damage (crit)
    30.298 Warlock unstable_affliction ticks (14 of 22) Fluffy_Pillow for 12707 shadow damage (hit)
    30.929 Warlock malefic_grasp ticks (3 of 4) Fluffy_Pillow for 10087 shadow damage (hit)
    30.929 Warlock agony ticks (14 of 33) Fluffy_Pillow for 13770 shadow damage (hit)
    30.929 Warlock corruption ticks (14 of 22) Fluffy_Pillow for 11650 shadow damage (hit)
    30.929 Warlock unstable_affliction ticks (14 of 22) Fluffy_Pillow for 12707 shadow damage (hit)
    30.929 Warlock performs malefic_grasp (192604)
    30.929 Warlock malefic_grasp hits Fluffy_Pillow for 0 shadow damage (hit)
    31.031 Warlock agony ticks (15 of 33) Fluffy_Pillow for 18360 shadow damage (hit)
    31.031 Warlock corruption ticks (15 of 22) Fluffy_Pillow for 15533 shadow damage (hit)
    31.129 Warlock unstable_affliction ticks (15 of 22) Fluffy_Pillow for 16943 shadow damage (hit)
    31.458 Warlock loses 1650.00 intellect (temporary)
    31.458 Warlock loses jade_spirit
    31.560 Warlock malefic_grasp ticks (1 of 5) Fluffy_Pillow for 10087 shadow damage (hit)
    31.560 Warlock agony ticks (15 of 33) Fluffy_Pillow for 13770 shadow damage (hit)
    31.560 Warlock corruption ticks (15 of 22) Fluffy_Pillow for 11650 shadow damage (hit)
    31.560 Warlock unstable_affliction ticks (15 of 22) Fluffy_Pillow for 26177 shadow damage (crit)
    32.002 Warlock agony ticks (16 of 33) Fluffy_Pillow for 37822 shadow damage (crit)
    32.002 Warlock corruption ticks (16 of 22) Fluffy_Pillow for 31997 shadow damage (crit)
    32.100 Warlock unstable_affliction ticks (16 of 22) Fluffy_Pillow for 16943 shadow damage (hit)
    32.191 Warlock malefic_grasp ticks (2 of 5) Fluffy_Pillow for 10087 shadow damage (hit)
    32.191 Warlock agony ticks (16 of 33) Fluffy_Pillow for 28366 shadow damage (crit)
    32.191 Warlock corruption ticks (16 of 22) Fluffy_Pillow for 11650 shadow damage (hit)
    32.191 Warlock unstable_affliction ticks (16 of 22) Fluffy_Pillow for 12707 shadow damage (hit)
    32.822 Warlock malefic_grasp ticks (3 of 5) Fluffy_Pillow for 10087 shadow damage (hit)
    32.822 Warlock agony ticks (16 of 33) Fluffy_Pillow for 13770 shadow damage (hit)
    32.822 Warlock corruption ticks (16 of 22) Fluffy_Pillow for 11650 shadow damage (hit)
    32.822 Warlock unstable_affliction ticks (16 of 22) Fluffy_Pillow for 12707 shadow damage (hit)
    32.973 Warlock agony ticks (17 of 33) Fluffy_Pillow for 37822 shadow damage (crit)
    32.973 Warlock corruption ticks (17 of 22) Fluffy_Pillow for 15533 shadow damage (hit)
    33.071 Warlock unstable_affliction ticks (17 of 22) Fluffy_Pillow for 16943 shadow damage (hit)
    33.453 Warlock malefic_grasp ticks (4 of 5) Fluffy_Pillow for 10087 shadow damage (hit)
    33.453 Warlock agony ticks (17 of 33) Fluffy_Pillow for 13770 shadow damage (hit)
    33.453 Warlock corruption ticks (17 of 22) Fluffy_Pillow for 11650 shadow damage (hit)
    33.453 Warlock unstable_affliction ticks (17 of 22) Fluffy_Pillow for 12707 shadow damage (hit)
    33.453 Warlock performs malefic_grasp (181981)
    33.453 Warlock malefic_grasp hits Fluffy_Pillow for 0 shadow damage (hit)
    33.944 Warlock agony ticks (18 of 33) Fluffy_Pillow for 18360 shadow damage (hit)
    33.944 Warlock corruption ticks (18 of 22) Fluffy_Pillow for 15533 shadow damage (hit)
    33.988 Warlock gains jade_spirit_1 ( value=0.00 )
    33.988 Warlock gains 1650.00 intellect (temporary)
    34.042 Warlock unstable_affliction ticks (18 of 22) Fluffy_Pillow for 16943 shadow damage (hit)
    34.084 Warlock malefic_grasp ticks (1 of 5) Fluffy_Pillow for 9457 shadow damage (hit)
    34.084 Warlock agony ticks (18 of 33) Fluffy_Pillow for 13770 shadow damage (hit)
    34.084 Warlock corruption ticks (18 of 22) Fluffy_Pillow for 11650 shadow damage (hit)
    34.084 Warlock unstable_affliction ticks (18 of 22) Fluffy_Pillow for 12707 shadow damage (hit)
    34.715 Warlock malefic_grasp ticks (2 of 5) Fluffy_Pillow for 9457 shadow damage (hit)
    34.715 Warlock agony ticks (18 of 33) Fluffy_Pillow for 13770 shadow damage (hit)
    34.715 Warlock corruption ticks (18 of 22) Fluffy_Pillow for 11650 shadow damage (hit)
    34.715 Warlock unstable_affliction ticks (18 of 22) Fluffy_Pillow for 12707 shadow damage (hit)
    34.915 Warlock agony ticks (19 of 33) Fluffy_Pillow for 18360 shadow damage (hit)
    34.915 Warlock corruption ticks (19 of 22) Fluffy_Pillow for 15533 shadow damage (hit)
    35.013 Warlock unstable_affliction ticks (19 of 22) Fluffy_Pillow for 16943 shadow damage (hit)
    35.346 Warlock malefic_grasp ticks (3 of 5) Fluffy_Pillow for 9457 shadow damage (hit)
    35.346 Warlock agony ticks (19 of 33) Fluffy_Pillow for 13770 shadow damage (hit)
    35.346 Warlock corruption ticks (19 of 22) Fluffy_Pillow for 11650 shadow damage (hit)
    35.346 Warlock unstable_affliction ticks (19 of 22) Fluffy_Pillow for 12707 shadow damage (hit)
    35.886 Warlock agony ticks (20 of 33) Fluffy_Pillow for 18360 shadow damage (hit)
    35.886 Warlock corruption ticks (20 of 22) Fluffy_Pillow for 15533 shadow damage (hit)
    35.977 Warlock malefic_grasp ticks (4 of 5) Fluffy_Pillow for 9457 shadow damage (hit)
    35.977 Warlock agony ticks (20 of 33) Fluffy_Pillow for 13770 shadow damage (hit)
    35.977 Warlock corruption ticks (20 of 22) Fluffy_Pillow for 11650 shadow damage (hit)
    35.977 Warlock unstable_affliction ticks (19 of 22) Fluffy_Pillow for 12707 shadow damage (hit)
    35.984 Warlock unstable_affliction ticks (20 of 22) Fluffy_Pillow for 16943 shadow damage (hit)
    36.857 Warlock agony ticks (21 of 33) Fluffy_Pillow for 18360 shadow damage (hit)
    36.857 Warlock corruption ticks (21 of 22) Fluffy_Pillow for 15533 shadow damage (hit)
    36.955 Warlock unstable_affliction ticks (21 of 22) Fluffy_Pillow for 34903 shadow damage (crit)
    37.220 Warlock performs unstable_affliction (177297)
    37.220 Warlock unstable_affliction hits Fluffy_Pillow for 0 shadow damage (hit)
    37.306 Warlock performs corruption (173985)
    37.306 Warlock corruption hits Fluffy_Pillow for 0 shadow damage (hit)
    37.828 Warlock agony ticks (22 of 33) Fluffy_Pillow for 18360 shadow damage (hit)
    37.828 Warlock corruption ticks (1 of 16) Fluffy_Pillow for 12656 shadow damage (hit)
    
    total: 968 167

    and hit-cap
    Code:
    17.324 Warlock performs soul_swap (164345)
    19.848 Warlock loses relic_of_yulon
    
    29.891 Warlock haunt hits Fluffy_Pillow for 82743 shadow damage (hit)
    29.891 Fluffy_Pillow gains haunt_1 ( value=0.00 )
    30.047 Warlock agony ticks (14 of 33) Fluffy_Pillow for 23480 shadow damage (hit)
    30.047 Warlock corruption ticks (14 of 22) Fluffy_Pillow for 19864 shadow damage (hit)
    30.272 Warlock malefic_grasp ticks (2 of 4) Fluffy_Pillow for 11821 shadow damage (hit)
    30.272 Warlock agony ticks (14 of 33) Fluffy_Pillow for 17610 shadow damage (hit)
    30.272 Warlock corruption ticks (14 of 22) Fluffy_Pillow for 14898 shadow damage (hit)
    30.272 Warlock unstable_affliction ticks (13 of 22) Fluffy_Pillow for 16251 shadow damage (hit)
    30.825 Warlock unstable_affliction ticks (14 of 22) Fluffy_Pillow for 21668 shadow damage (hit)
    30.903 Warlock malefic_grasp ticks (3 of 4) Fluffy_Pillow for 11821 shadow damage (hit)
    30.903 Warlock agony ticks (14 of 33) Fluffy_Pillow for 36276 shadow damage (crit)
    30.903 Warlock corruption ticks (14 of 22) Fluffy_Pillow for 30690 shadow damage (crit)
    30.903 Warlock unstable_affliction ticks (14 of 22) Fluffy_Pillow for 33478 shadow damage (crit)
    30.903 Warlock performs malefic_grasp (192604)
    30.903 Warlock malefic_grasp hits Fluffy_Pillow for 0 shadow damage (hit)
    31.018 Warlock agony ticks (15 of 33) Fluffy_Pillow for 23480 shadow damage (hit)
    31.018 Warlock corruption ticks (15 of 22) Fluffy_Pillow for 40920 shadow damage (crit)
    31.534 Warlock malefic_grasp ticks (1 of 5) Fluffy_Pillow for 12609 shadow damage (hit)
    31.534 Warlock agony ticks (15 of 33) Fluffy_Pillow for 17610 shadow damage (hit)
    31.534 Warlock corruption ticks (15 of 22) Fluffy_Pillow for 14898 shadow damage (hit)
    31.534 Warlock unstable_affliction ticks (14 of 22) Fluffy_Pillow for 16251 shadow damage (hit)
    31.796 Warlock unstable_affliction ticks (15 of 22) Fluffy_Pillow for 44637 shadow damage (crit)
    31.891 Warlock haunt ticks (1 of 4) Fluffy_Pillow for 0 shadow damage (hit)
    31.989 Warlock agony ticks (16 of 33) Fluffy_Pillow for 23480 shadow damage (hit)
    31.989 Warlock corruption ticks (16 of 22) Fluffy_Pillow for 19864 shadow damage (hit)
    32.165 Warlock malefic_grasp ticks (2 of 5) Fluffy_Pillow for 12609 shadow damage (hit)
    32.165 Warlock agony ticks (16 of 33) Fluffy_Pillow for 17610 shadow damage (hit)
    32.165 Warlock corruption ticks (16 of 22) Fluffy_Pillow for 14898 shadow damage (hit)
    32.165 Warlock unstable_affliction ticks (15 of 22) Fluffy_Pillow for 16251 shadow damage (hit)
    32.767 Warlock unstable_affliction ticks (16 of 22) Fluffy_Pillow for 21668 shadow damage (hit)
    32.796 Warlock malefic_grasp ticks (3 of 5) Fluffy_Pillow for 12609 shadow damage (hit)
    32.796 Warlock agony ticks (16 of 33) Fluffy_Pillow for 17610 shadow damage (hit)
    32.796 Warlock corruption ticks (16 of 22) Fluffy_Pillow for 14898 shadow damage (hit)
    32.796 Warlock unstable_affliction ticks (16 of 22) Fluffy_Pillow for 16251 shadow damage (hit)
    32.960 Warlock agony ticks (17 of 33) Fluffy_Pillow for 23480 shadow damage (hit)
    32.960 Warlock corruption ticks (17 of 22) Fluffy_Pillow for 19864 shadow damage (hit)
    33.427 Warlock malefic_grasp ticks (4 of 5) Fluffy_Pillow for 12609 shadow damage (hit)
    33.427 Warlock agony ticks (17 of 33) Fluffy_Pillow for 36276 shadow damage (crit)
    33.427 Warlock corruption ticks (17 of 22) Fluffy_Pillow for 14898 shadow damage (hit)
    33.427 Warlock unstable_affliction ticks (16 of 22) Fluffy_Pillow for 16251 shadow damage (hit)
    33.427 Warlock performs malefic_grasp (181981)
    33.427 Warlock malefic_grasp hits Fluffy_Pillow for 0 shadow damage (hit)
    33.738 Warlock unstable_affliction ticks (17 of 22) Fluffy_Pillow for 21668 shadow damage (hit)
    33.891 Warlock haunt ticks (2 of 4) Fluffy_Pillow for 0 shadow damage (hit)
    33.931 Warlock agony ticks (18 of 33) Fluffy_Pillow for 23480 shadow damage (hit)
    33.931 Warlock corruption ticks (18 of 22) Fluffy_Pillow for 19864 shadow damage (hit)
    34.058 Warlock malefic_grasp ticks (1 of 5) Fluffy_Pillow for 25975 shadow damage (crit)
    34.058 Warlock agony ticks (18 of 33) Fluffy_Pillow for 17610 shadow damage (hit)
    34.058 Warlock corruption ticks (18 of 22) Fluffy_Pillow for 30690 shadow damage (crit)
    34.058 Warlock unstable_affliction ticks (17 of 22) Fluffy_Pillow for 16251 shadow damage (hit)
    34.689 Warlock malefic_grasp ticks (2 of 5) Fluffy_Pillow for 12609 shadow damage (hit)
    34.689 Warlock agony ticks (18 of 33) Fluffy_Pillow for 17610 shadow damage (hit)
    34.689 Warlock corruption ticks (18 of 22) Fluffy_Pillow for 14898 shadow damage (hit)
    34.689 Warlock unstable_affliction ticks (17 of 22) Fluffy_Pillow for 16251 shadow damage (hit)
    34.709 Warlock unstable_affliction ticks (18 of 22) Fluffy_Pillow for 44637 shadow damage (crit)
    34.902 Warlock agony ticks (19 of 33) Fluffy_Pillow for 23480 shadow damage (hit)
    34.902 Warlock corruption ticks (19 of 22) Fluffy_Pillow for 19864 shadow damage (hit)
    35.320 Warlock malefic_grasp ticks (3 of 5) Fluffy_Pillow for 12609 shadow damage (hit)
    35.320 Warlock agony ticks (19 of 33) Fluffy_Pillow for 17610 shadow damage (hit)
    35.320 Warlock corruption ticks (19 of 22) Fluffy_Pillow for 14898 shadow damage (hit)
    35.320 Warlock unstable_affliction ticks (18 of 22) Fluffy_Pillow for 16251 shadow damage (hit)
    35.680 Warlock unstable_affliction ticks (19 of 22) Fluffy_Pillow for 21668 shadow damage (hit)
    35.873 Warlock agony ticks (20 of 33) Fluffy_Pillow for 23480 shadow damage (hit)
    35.873 Warlock corruption ticks (20 of 22) Fluffy_Pillow for 19864 shadow damage (hit)
    35.891 Warlock haunt ticks (3 of 4) Fluffy_Pillow for 0 shadow damage (hit)
    35.951 Warlock malefic_grasp ticks (4 of 5) Fluffy_Pillow for 12609 shadow damage (hit)
    35.951 Warlock agony ticks (20 of 33) Fluffy_Pillow for 36276 shadow damage (crit)
    35.951 Warlock corruption ticks (20 of 22) Fluffy_Pillow for 14898 shadow damage (hit)
    35.951 Warlock unstable_affliction ticks (19 of 22) Fluffy_Pillow for 16251 shadow damage (hit)
    36.651 Warlock unstable_affliction ticks (20 of 22) Fluffy_Pillow for 44637 shadow damage (crit)
    36.844 Warlock agony ticks (21 of 33) Fluffy_Pillow for 48368 shadow damage (crit)
    36.844 Warlock corruption ticks (21 of 22) Fluffy_Pillow for 19864 shadow damage (hit)
    37.089 Warlock performs unstable_affliction (177297)
    37.089 Warlock unstable_affliction hits Fluffy_Pillow for 0 shadow damage (hit)
    37.188 Warlock performs corruption (172797)
    37.188 Warlock corruption hits Fluffy_Pillow for 0 shadow damage (hit)
    37.622 Warlock unstable_affliction ticks (1 of 14) Fluffy_Pillow for 16146 shadow damage (hit)
    37.815 Warlock agony ticks (22 of 33) Fluffy_Pillow for 23480 shadow damage (hit)
    37.815 Warlock corruption ticks (1 of 16) Fluffy_Pillow for 14802 shadow damage (hit)
    37.891 Fluffy_Pillow loses haunt
    
    total: 1 480 099
    Both should have the same amount of ticks from dots and MG. Procs are not the same however. All dots we see after ~0:30s are reciving buffs that were up at ~0:17. Non-cap lock is missing Relic of Yulon, but then he has Jade Spirit later that affects some of the MG ticks. Also the hit-capped lock got the crits.

    With this haunt miss the non-cap lock did 511932 less damage during theese 8 seconds, compared to someone with less mastery and 15 % hit. Fight duration for example is 450s so this is making a difference of 1137 dps. If the 2131 mastery is giving dps at 2.5 per point, then he has a 4190 dps advantage remaining from which he can keep loosing in the other miss events. Miss event of one average MG gcd comes from MG second which is ~80 441 damage in the other profile.

    Quote Originally Posted by Palmz
    Also missing that haunt will bring up a cascading problem. Forcing you to lose 4-5 seconds of mega dot damage, possibly lose the extra damage from a Haunt that might of landed a critical strike, decrease your chances of Nightfall procs and miss your chance to roll Haunts.
    How big is the damage difference with your 4-5s and those other things included? Or how did you end up with them?

    One thing to note about a Haunt miss is that it can not always get worse for slow players. Everyone is expected to cast something else after the Haunt cast time is over. They will often be in the middle of a MG channel when their world crumbles, but they often have nothing other to do than finishing the MG. If they have shards, and they know that it is still a good time to Haunt, only then they would also need some reflexes.

    About shards, if you have a constant amount of shard procs set for the fight, and then you miss one Haunt, it does not reduce your MG uptime for whole fight, because you can not take a gcd of it to use another Haunt since there are not enough shards. If MG uptime stays the same so far, your shard number can not get lower, and you actually have the amount of shards set.

    During the BL thing if you start with two shards and miss the first Haunt then in that case the shard generation rng events will be delayed for one gcd, but you are somehow making your damage differences of early shards vs. delayed (by gcd or reaction) ones big here. In a case of 4 wanted Haunts (3 landing), say you miss the second one, making it delaeyd depending on reaction time. But if this means your 3rd Haunt will not get a shard early when you actually wanted it, then during your second Haunt debuff you are without the next shard for too long and you are not even playing the same way as you do when first Haunt is up. You can expect different kind of damage there, so count that in, because simc default action list does, when it is able have more than one shard with BL at the start or under 20 %, and it does not appreaciate hit rating.

    Any other miss event but not the Haunt one would directly lower the MG uptime. Therefore when hit-cap versus non-cap is simmed there are less shards for the latter, and it is easily seen, unless he reforges it for haste, but dps is what it is.

    Quote Originally Posted by Palmz
    Another example would be re-casting a DoT with 1 second left on your trinket buff. With out the hit cap, for instance at the pull, typically your Jade Spirit, DMC trinket proc and Lightweave will end at the same time and be the first of your 6-7 buffs to fall off. With the hit cap you can do a SB:SS with 1 second left with these procs and continue to roll for high amounts of damage while quickly procing Nightfall for more Haunts.
    And people would fail at this at 3-8 % rate. What if the non-hit cap lock who does not like it, clips each of the dots separately, begining with those closest to a legit refresh point? Without clipping it looks about like (0:00 DS), 0:08 UA, 0:10 Corr, 0:13 CoA. There are alot of procs there at 0:13 and some seconds after it. One more Haunt can be used immeadetly when wanted and it does not depend on rng. This is default action list ofcourse where missing those spells is not statistically significant enough to make hit cap amazing.

    For all of your post you are refering to the dps gain of being below 15 % hit rating as a number of "200-300 dps". But is this not a number from default action list in simc and probably only for some ridiculous 12 % beginner? If you have so many bright ideas about how to play then why don't you first seek for the unique value of hit rating for theese styles, instead of asuming it must be critical? Or it is the other secondary stats I mean that might become stronger too but also faster.

  8. #48
    The Lightbringer nightfalls's Avatar
    Join Date
    Sep 2012
    Location
    Rochester, NY
    Posts
    3,715
    Quote Originally Posted by Harsesis View Post
    On Windlord if you are CCing you are hitting at most 6 targets. This is not enough targets to make Seed spamming effective. At that point it is the highest dps to pick 3 targets and focus on them. If you have 1 of each pack available use those and you will do the most effective dps.
    There are 7 targets, with some more effective than others...

  9. #49
    When I initially did a quick and dirty check on the Hitcap vs no-Hitcap thingie, I actually changed Haste to Mastery and not Hit and then incorrectly claimed that dropping Hit was actually a DPS loss. I corrected myself a couple of posts later, dropping 3% Hit is in fact about a 300 DPS gain, see this and this post (which also link to the relevant reports, so you can check the simulation settings yourself.

    Now, I think that the current APL favors not hitcapping for two reasons:
    - it refreshes DoTs as early as possible no matter the power of the DoTs and the current spellpower
    - it uses Haunt everytime it can, which makes it less likely to miss a Haunt within a DS window
    Saving Shards for DS can be added to the APL without changing too much, but dynamically refreshing early or late depending on the spellpower/haste of the DoTs is more complicated. Especially because you might want to refresh a weak DoT late if you are about to pop DS and will then refresh anyway.

    With this in mind, I think that the logic behind hitcapping still holds merrit. You eliminate one random factor that might just take you that few seconds to long to react to or that might take your focus away from some crucial encounter mechanic. Hitcapped you can basically plan your rotation 5 or 10 seconds ahead, without hitcap you might need to decide on the spot what to do.

    As for Windlord, I am pretty sure that spamming SoC while using your Shards for SB:SS is the way to go if you have 7 targets (SB:SS should have a higher DPET than any other spell if you apply all 3 DoTs, didn't check that though). Feel free to provide any numbers to the contrary. As I mentioned before, even at Wind Lord SoC is only 5% of your overall damage. This is obviously due to the 600% additional damage the Boss takes after a group dies, but even if you ignore this mechanic, you will always have DoTs ticking on as many targets as you have Shards for, so I would not be sure that Haste is at some point the best stat for such a fight.

    Quote Originally Posted by Bonkura View Post
    Well, this is why it would be nice to have a SimC Warlock developer on the forums. Or at least someone dedicated with the knowledge who can figure out these results.

    What SirFlipper brings up on previous page is interesting. Trying to figure out how SimCraft handles haste plateaus is something we should've done long ago. The answers to this just never seem to show up here.
    I am still waiting for you to incorporate them into the original post or at least reply to them. SimCraft does not "handle" Haste plateaus, it just simulates your character (by executing a simple action priority list). The haste plateaus do not have to be "treated", they just happen.

    Quote Originally Posted by luckydevours View Post
    I recently abandoned the 4717 haste threshold and did some reforging and simcrafting to find the best haste-mastery ratio for me to play with. SimCraft tells me i get the most dps at 7726 haste and 4679 mastery rating:
    ...
    My armory: http://eu.battle.net/wow/en/characte...ypsez/advanced

    I cannot explain those particular numbers but perhaps they help you get to the bottom of this nasty affliction spec Xelnath forced on us
    I would assume that this is a local maximum and not a global maximum. If I go for this Haste rating I lose DPS, but I can't really explain what is going on there... will need to take a closer look tomorrow.

  10. #50
    Quote Originally Posted by SirFlipper View Post
    Now, I think that the current APL favors not hitcapping for two reasons:
    - it refreshes DoTs as early as possible no matter the power of the DoTs and the current spellpower
    - it uses Haunt everytime it can, which makes it less likely to miss a Haunt within a DS window
    Saving Shards for DS can be added to the APL without changing too much, but dynamically refreshing early or late depending on the spellpower/haste of the DoTs is more complicated. Especially because you might want to refresh a weak DoT late if you are about to pop DS and will then refresh anyway.
    Then default list must be good at simulating non-hit cap dps if real players also do not let their dots drop.

    I wrote above what a MG second is. Missing a dot at any duration remaining means losing damage based on this, in every list that has MG as a filler. Compared to it, in that above profile, DoT second for UA is ~13 872 damage. If the UA is dropped it can be down for any amount of time, also smaller than 1 s, and not always for a gcd. In lists where dots are alowed to drop there would be zero to few damages like this missing for the non-cap (not in the logs, logs have ticks, UA second is from average dot dps).

    Default list has many shards only in the first DS, and it uses them the way it does. After that it can have 1 or 0 shards when the next DS is ready. So how this could go is that you say it misses the same amount of Haunts as a list that has more shards ready before DS. When default suffers a Haunt miss event it is with higher probability an event with somewhat less damage loss, while the other profile has a good chance to have those Haunts missing that are in DS. This is not proper for deciding what stat is good necessarily. Consider if the other list has 4 shards when DS begins. As he misses, this has the damage penalty I did not want to consider above, because it is actually followed by another Haunt. It is very likely that those 4 shards, and new shards generated, will last through the DS. My example had shards for quite long.

    Then when you compare damages in new list there are results like "All DS covered with Haunts (hit-cap)" and "All DS covered with Haunts while getting misses as is expected (non-cap)"

    In default list instead you are comparing damages that had "as many Haunts during DS as possible (hit-cap)" vs. "8 s full Haunt missing from a DS (non.cap)".

    I still say that it can be easy to say that some event or style is making hit rating more or less valuable. But for gear decisions you would have to know the value of other stats also.

    Quote Originally Posted by Sirflipper
    With this in mind, I think that the logic behind hitcapping still holds merrit. You eliminate one random factor that might just take you that few seconds to long to react to or that might take your focus away from some crucial encounter mechanic. Hitcapped you can basically plan your rotation 5 or 10 seconds ahead, without hitcap you might need to decide on the spot what to do.
    If you do not trust random factors then you should not expect to be dealing much consistent damage with the proc boosting. Also when you do it you are first supposed to react to see a new buff coming up, which is as hard as seeing a miss warning. Then, if there were no smart robot addons, you would start making decisions reflecting on the durations of three different dots. If you decide to wait for the proc to go short before you refresh, you will have to focus on the buff timer for 5-10 seconds. If you only focus on the addon then since all procs are random and some can come up immeadetly after expiring, you will probably focus on that addon for 100 % of the time. Is any of this better for dealing with the bosses, compared to the quick decision making you deal with in non-cap?

    Another thing is someone better make the action lists that follow procs, more humanly possible than what the default is now, or I guess people's hype for those dps gains won't be justified.

  11. #51
    Quote Originally Posted by Bonkura View Post
    I've even had a Warlock in my guild following this and stacking mastery to well above 8000. Then he complained about me doing more damage because I had slightly more mastery when I was also sitting at almost 2000 more haste than him. This at Sha of Fear HC progress... sigh.
    Hej Bonk, fan vilken kuk du är.

    Anywho, I am this warlock he speaks of, and while we were at it Bonk here had not even just better gear then me overall, but also had 4 set bonus - which I did not.
    Sure he did more damage than me, at the pull, he had some sick burst (me 260k he 300k) but at the end of the fights we were about the same, and also, in ph2 - with alot of adds - I did MORE damage then him.

    Anyway, I'm not even qualified (or frankly, I can't be arsed) to go into this discussion about what is best etcetc, I just had to come and defend myself :>

  12. #52
    Quote Originally Posted by Kozya View Post
    Hej Bonk, fan vilken kuk du är.
    Made me lol

    kozya is super warlock.

    Clear evidence stacking mastery to above 8k is the way to go?
    Last edited by Micke; 2013-01-06 at 05:14 PM.

  13. #53
    Quote Originally Posted by Micke View Post
    Made me lol

    Kozya is super warlock.
    And who are you? :>

    And WoL agress with you.

  14. #54
    Quote Originally Posted by Kozya View Post
    And who are you? :>

    And WoL agress with you.
    Just a fellow-countryman, and just went a little silly to match your post, didn't mean anything by it :P still good to match someone with lesser gear though ofc.

  15. #55
    Ah.

    Well I just had to say something about what Bonk here said.

    I'm not claiming that "my way" is THE way to go, or that Bonk's is but what I do works great for me, I have several top 10 ranks so unless someone proves to me that this way (or any other for that matter) it THE way, I'm sticking with mine. :>

  16. #56
    Quote Originally Posted by SirFlipper View Post
    I am still waiting for you to incorporate them into the original post or at least reply to them. SimCraft does not "handle" Haste plateaus, it just simulates your character (by executing a simple action priority list). The haste plateaus do not have to be "treated", they just happen.
    I haven't had time to go through everything in the thread more than reading what's been posted. I'll get to it in a day or two. Sorry about that.

    I also have to admit that it's probably good if I don't respond to everything and let other people share their thoughts on what's being discussed here with unbiased opinions. Especially since I'm no genius when it comes to theorycrafting and just doing this to encourage a discussion about the topics brought up here. ^^

    Quote Originally Posted by Kozya View Post
    Anyway, I'm not even qualified (or frankly, I can't be arsed) to go into this discussion about what is best etcetc, I just had to come and defend myself :>
    I didn't mention your name so why does it matter?

    Quote Originally Posted by Kozya View Post
    I'm not claiming that "my way" is THE way to go, or that Bonk's is but what I do works great for me, I have several top 10 ranks so unless someone proves to me that this way (or any other for that matter) it THE way, I'm sticking with mine. :>
    You're just proving that you are a really good player who doesn't spend much time with theorycrafting and just go for the general suggestions for gearing. In theory you're not losing more than ~1% DPS so it's not really that big of a deal and you're probably aware of it.

    Let's leave it at that.

  17. #57
    Super Moderator Elysia's Avatar
    Join Date
    Jul 2009
    Location
    Baylife
    Posts
    9,549
    Keep the guild drama off these boards, please.

  18. #58
    Dreadlord Cebel's Avatar
    Join Date
    Oct 2009
    Location
    Arkansas, United States
    Posts
    951
    Quote Originally Posted by Elysia View Post
    Keep the guild drama off these boards, please.
    their guild is dead and trash anyways no biggy :P


    [Infracted]
    Last edited by Radux; 2013-01-07 at 07:36 PM.

  19. #59
    Quote Originally Posted by pixul View Post
    their guild is dead and trash anyways no biggy :P
    Stop this now. Things have been going great in this thread. No one cares what you think about my old guild and it's just sad that you bring it up.

  20. #60
    Epic!
    Join Date
    Oct 2010
    Location
    France, Illidan-EU
    Posts
    1,742
    Well, this is why it would be nice to have a SimC Warlock developer on the forums. Or at least someone dedicated with the knowledge who can figure out these results.
    Gobuchul (aka Zakalwe on EJ) comes by sometimes on this forum, he is the one in charge of the warlock module if I'm not mistaken.
    NEW Android App : World of Quizzcraft
    Test your knowledge of WoW with more than 1100 questions and 80 achievements!

    Web Apps : Deaths Analyzer, WoL Timeline, Megaera Dps Calculator
    WoW-Heroes

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •