SimulationCraft for Warlocks (Panda Edition) - Page 25

ZumoO · 08/31/12, 3:42 AM

I don't know if this is already taken in account by Simcraft and not sure if this is intended by Blizzard (would be more logical for Trolls ?), but Orcs currently gain 1% expertise when equipping a wand.

• Zakalwe · 08/31/12, 5:22 AM

Definitely seems like a bug, and it's not just wands, I gain the 1% of expertise when wielding no weapon at all as well. And no, the sim is not reflecting this at present.

ZumoO · 08/31/12, 5:31 AM

From Wowpedia :

As fist weapons use the unarmed skill, Axe Specialization works when you are unarmed as well.

randa · 08/31/12, 7:34 AM

This line should be changed
Q 10.48 life_tap,if=mana.pct<35

into
Q 10.48 life_tap,if=mana.pct<35&buff.dark_soul.down

• Zakalwe · 08/31/12, 7:49 AM

Why? That's a haste buff, it benefits life tap as much as it benefits anything else.

Scathbais · 08/31/12, 1:51 PM

On Destro AOE:

Given RoF has a significantly higher DPET than F&B:Incinerate (620k vs 350k dps) and given that mana never goes below ~80%, why wouldn't we stack consecutive RoFs until F&B:Immolate needs to be recast or mana got lower than x%?

In other words, why the "if=!ticking&!in_flight conditional" on RoF?

I just checked, no matter how many RoF you cast, it does not increase damage done.

• Zakalwe · 08/31/12, 1:53 PM

You can't stack RoF, at least you couldn't when I tested it months ago in beta.

Scathbais · 08/31/12, 1:55 PM

Originally Posted by Zakalwe

You can't stack RoF, at least you couldn't when I tested it months ago in beta.

delete

Gohinad · 09/01/12, 5:34 AM

I just wanna verify few things I am not sure about:

1.
actions+=/haunt,cycle_targets=1,if=!in_flight_to_target&remains<tick_time+travel_time+cast_time&soul_shard>1

tick_time? What ticks does haunt have? Does this mean you should time it to land when there is still 0.5/1/2s left on old haunt?

What number is used in simulation for "tick_time"?

2.
actions+=/malefic_grasp,chain=1
why is dps loss if you add "interrupt=1" to this line

3.
actions+=/agony,cycle_targets=1,if=(!ticking|remains<=action.drain_soul.new_tick_time*2)&target .time_to_die>=8&miss_react

Since interrupting MG is dps loss i wanted to refresh Agony before it cast another MG if duration of Agony is shorter than cast time of MG, but still longer than tick of Agony.

I added |remains<=action.malefic_grasp

actions+=/agony,cycle_targets=1,if=(!ticking|remains<=action.drain_soul.new_tick_time*2|remains<=action.malefic_grasp)&target.time_to_die>=8&miss_react

but this is throwing me error. What is correct line for this? (I know this wont matter on lvl 90, i am just curious.)

• Zakalwe · 09/01/12, 5:55 AM

1. 2 seconds. To quote GC: "These spells have been turned into periodics, despite not really doing anything periodically, so that you can take advantage of this same ability to clip the last couple seconds with no loss."

2. I imagine this is because we don't let the sim interrupt channels perfectly - we add a delay at an average of 250 milliseconds after the most recent tick, and it's better to pay that price for 4 ticks than for less.

3. The expression you're looking for is action.malefic_grasp.new_tick_time*4, since it always ticks 4 times. But since drain soul ticks exactly twice as slow as malefic grasp, this ends up being exactly equivalent to action.drain_soul.new_tick_time*2, so you don't need to add anything.

EDIT: The 250 millisecond average delay after channeled spells is tunable using the option "channel_lag". If you set this to anything lower than 180 milliseconds or so, interrupting malefic grasp is no longer a loss, but a gain.

Ysz · 09/03/12, 2:17 PM

I noticed that the reforging and gemming of the current Affliction profile is not based on the scale factors from the Simulationcraft. (Int>SP>Mastery>Haste>Hit>Crit)
I can understand that people may still want to be hitcapped out of personal preference, but shouldn't the reforging be focusing on mastery?

← Click Here

netsach · 09/04/12, 4:42 AM

@Ysz : You were right, as i saw the profiles being modified in the code, but i wanted to add that the best tool to estimate reforge optimization is the reforge plot, not stat weights for reforges. Why that ? because stats weights are calculated by adding stats relatively to the current values (ie upgrading items) and not by reforging (removing stats and adding stats).

Update #1 : Demo AOE scenario is better then normal prio from 4+ targets instead of 6+.

Changed : actions+=/run_action_list,name=aoe,if=num_targets>3

4 targets
225907 53.3% Warlock_Demonology_T14H_aoe
197686 46.7% Warlock_Demonology_T14H
186453 53.4% Warlock_Demonology_T14N_aoe
162746 46.6% Warlock_Demonology_T14N
125240 51.3% Warlock_Demonology_PreRaid_aoe
118851 48.7% Warlock_Demonology_PreRaid
110725 53.6% Warlock_Demonology_T13H_aoe
95721 46.4% Warlock_Demonology_T13H

5 targets
274211 55.6% Warlock_Demonology_T14H_aoe
218785 44.4% Warlock_Demonology_T14H
227297 55.8% Warlock_Demonology_T14N_aoe
180241 44.2% Warlock_Demonology_T14N
158614 54.9% Warlock_Demonology_PreRaid_aoe
130123 45.1% Warlock_Demonology_PreRaid
136893 56.1% Warlock_Demonology_T13H_aoe
107302 43.9% Warlock_Demonology_T13H

Update #2 : Refreshing Corruption on 2-3 targets using ToC is an upgrade

Changed : actions+=/touch_of_chaos,cycle_targets=1,if=dot.corruption.remains<20

2 Targets
146433 50.4% Warlock_Demonology_T14H_toc
144339 49.6% Warlock_Demonology_T14H
120570 50.4% Warlock_Demonology_T14N_toc
118787 49.6% Warlock_Demonology_T14N
87625 50.4% Warlock_Demonology_PreRaid_toc
86325 49.6% Warlock_Demonology_PreRaid
70219 50.4% Warlock_Demonology_T13H_toc
68977 49.6% Warlock_Demonology_T13H

3 Targets
175233 50.4% Warlock_Demonology_T14H_toc
172433 49.6% Warlock_Demonology_T14H
144674 50.5% Warlock_Demonology_T14N_toc
141753 49.5% Warlock_Demonology_T14N
105636 50.5% Warlock_Demonology_PreRaid_toc
103641 49.5% Warlock_Demonology_PreRaid
85227 50.8% Warlock_Demonology_T13H_toc
82707 49.2% Warlock_Demonology_T13H

Update #3 : i confirmed for T13H too, so i'll updated the code and regenerated the profiles

Sonicator · 09/07/12, 7:39 PM

What does this mean in simulationcraft?

soulburn,line_cd=15,if=buff.dark_soul.up&shard_react

what is the "line_cd=15" part? What is that 15 in there?

• Zakalwe · 09/08/12, 4:54 AM

Line cooldown. It means that action line won't be activated again for 15 seconds after it's activated.

Loot · 09/09/12, 3:04 AM

Now... it is often we need to interrupt MG/DS before it is over, shall we interrupt right after a tick? Can this be modeled in simcraft in the sense: interrupt if=time_since_last_tick<tick_length%3 or something in the lines?