I am currently digging through the spell_query data, and i admit i have a hard time figuring how to interpret the effects.
Wether i try to compare it to parsed (via wowhead) or unparsed description text, i sometime fail at interpreting the $ stuff that's in there. I understood that the last digit refers to the effect number, but sometimes i'm intrigued because some letter change and i don't know why. Example : BoD, there s a $s1 in the description, and in the tooltip it's a $w1, both seem to refer to the same thing, but what do both mean ? For Corruption, it's $o1, then $w1...
Then, i could understand the "base value" and coeficient things, which i'd take as x = base value + coefficient * spellpower, but for example in chaos bolt there is an additionnal "min-max" and a "value range"... the use of which i can't guess because they don't "sum up". Finally, there is sometime cross references to other spell's effects, for example demon leap 54785 referencing demon leap 54786 spell-effects. I could find some testing in the refernces, as in Drain Life where the duration is $689d.$?s74434, which seems to mean it's duration of drain life, but checks for soulburn to modify the duration. And there's the $/6;s1 from incinerate which relates to 1/6th of the base value of effect 1.
All in all, i think i could guess all this, but i'd prefer reading something about it beforehand. So my question are :
- is there any documentation about the proper complete syntax of $ variables
- same for the complete listing of effects types, and what to do with them (I browsed through the dbc extractor python code and found the effects types and subtypes, but there was no comment on what they mean and what action is to be taken)
PS : I know it sounds "useless" to ask for this in the first place, as the tool "just works" but i like digging though things, and figure out what's going on. But here, i'm kinda stuck as i don't want to misinterpret what i read... Thanks in advance for any help.
The formula would be more correctly represented as ( 9830 / 5 ) * 1.08 which gives 2123.
I have checked the SimulationCraft code and the Affliction Warlock numbers for the Rathrak dot ticks come via the following buffs and debuffs:
* Curse of Elements (+8%)
* Ferocious Inspiration/Arcane Tactics/Ret Pally talent (+3%)
* Dark Intent DoT tick multiplier (+9%)
So the formula would then be: ( 9830 / 5 ) * 1.08 * 1.03 * 1.09 which is 2383.806456. This matches the 2384 I saw in the SimulationCraft report I generated. As I do not have a Warlock myself (or Rathrak) it's a little difficult for me to test, however given those 3 buffs and debuffs listed above maybe someone here is able to confirm whether or not they apply in-game.
I have tested the Normal Mode version of the dagger on a training dummy today. While I had 3 stacks of DI and Arcane Tactics, as well as CoE on the Dummy. I got this result:
It seems the DoT does NOT scale with the 9% DoT tick multiplier. (8710 / 5) * 1.08 * 1.03 = 1938 proves this. Shadow Bite is also uneffected by this DoT which is causing me to wonder if the game is actually treating the DoT as a DoT (that may sound strange I know), but instead each tick is treated as a separate direct damage cast. It also DOES scale with Metamorphosis.
In any case, this should help to bring it's simmed damage more in line with that on live.
The first post shows a graph of the value of the procs, but they also link to Simcraft with new graphs with different numbers (although the same order). Do the graphs over at Simulationcraft.org also only take into account the proc values or are they factored in with the scale values for the gear used in conjunction? I'm asking because I'm confused over why for example DMC:V sims higher in the graphs than H:VPLC for Affliction, yet VPLC is used in the BIS-list for T12.
I hope you understand what I mean.
Last edited by krilz : 12/29/11 at 6:31 AM.
Reason: clarification
The general assumption of Conflagrate's mechanic is that its damage is based on the amount of ticks of Immolate currently on the target. (i.e, refreshing Immolate while dynamic haste buffs/bloodlust are present THEN casting Conflagrate will result in harder hitting Conflagrates.)
This can also be seen from the current modelling of the destro priority list, from the action below:
Incidentally, I came across a thread on wowhead, which some people had done their own tests on Conflagrate's mechanics, and apparently it does not coincide with the general assumption and/or the current modelling in simcraft.
If this is truly the case, it might not be beneficial to recast Immolate during dynamic haste buffs/bloodlust, or rather we should be continuing with the normal priority list, since Conflagrate will be hitting for harder anyway, due to the so-called 'virtual Immolate' mechanic that Conflagrate uses.
The general assumption of Conflagrate's mechanic is that its damage is based on the amount of ticks of Immolate currently on the target. (i.e, refreshing Immolate while dynamic haste buffs/bloodlust are present THEN casting Conflagrate will result in harder hitting Conflagrates.)
This can also be seen from the current modelling of the destro priority list, from the action below:
Incidentally, I came across a thread on wowhead, which some people had done their own tests on Conflagrate's mechanics, and apparently it does not coincide with the general assumption and/or the current modelling in simcraft.
If this is truly the case, it might not be beneficial to recast Immolate during dynamic haste buffs/bloodlust, or rather we should be continuing with the normal priority list, since Conflagrate will be hitting for harder anyway, due to the so-called 'virtual Immolate' mechanic that Conflagrate uses.
You're misunderstanding what the thread is saying. The number of ticks the Immolate has is snapshotted, but Conflag uses your current spell power, not the spell power you had when you cast the Immolate, to calculate it's damage. This is what the thread states (it was posted during patch 4.0.6), the community concluded ages ago, and what SimC already does.
Doomguards Doom Bolt cast time isnt simmed correctly at the moment. It always has a cast time of 3 seconds, and doesnt benefit from haste rating. This behavior is wrong like I pointed out in Warlock Mechanics in Cataclysm.
The exact way the doomguard scales with haste seem a little more buggy as I underlined it in this issue.
This same issue also picked up a behavior concerning damage proc trinkets like VPLC or CotC. Is it fixed ?
Noticed that the 4pt13 was badly used on the pull, discarded
actions+=/soulburn,if=pet.felguard.active&!pet.felguard.dot.felstorm.ticking
and added
actions+=/soulburn,if=pet.felguard.active
before BoD, got a ~80 DPS increase.
I noticed simcraft now has an "Ultraxion" setting, which includes incoming raid damage... I'm wondering now if there's a concentration aura style buff that can be toggled? Would be cool to see the differences that aura can make with all the pushback in today's fights.
I noticed simcraft now has an "Ultraxion" setting, which includes incoming raid damage... I'm wondering now if there's a concentration aura style buff that can be toggled? Would be cool to see the differences that aura can make with all the pushback in today's fights.
There isn't currently and it'd require quite some reworking to get it in, so it's not likely to happen soon from a current developer. We are open to patches, until then, hopefully you can run with a shaman or a paladin.
Does Simulationcraft sim out VPLC properly? I sim my warlock and simulationcraft says that the proc on the trinket (normal 384 version) is worth 2.3% of my dps. However, the proc is always greater than 5% of my damage in actually boss fights and usually it is in the 5.5%-6% of my damage range. When I do napkin math to have the proc represent 5.5% of my dps, the 384 VPLC trinket sims out higher than the heroic version of Insignia of the Corrupted Mind. Something simply doesn't seem right here.
My raid group is near a heroic Yor'saj kill and I don't want to pass on heroic ICM but right now the VPLC proc appears to be too valuable to lose. Does VPLC scale somehow with gear and simulationcraft isn't reflecting this?
Does Simulationcraft sim out VPLC properly? I sim my warlock and simulationcraft says that the proc on the trinket (normal 384 version) is worth 2.3% of my dps. However, the proc is always greater than 5% of my damage in actually boss fights and usually it is in the 5.5%-6% of my damage range. When I do napkin math to have the proc represent 5.5% of my dps, the 384 VPLC trinket sims out higher than the heroic version of Insignia of the Corrupted Mind. Something simply doesn't seem right here.
My raid group is near a heroic Yor'saj kill and I don't want to pass on heroic ICM but right now the VPLC proc appears to be too valuable to lose. Does VPLC scale somehow with gear and simulationcraft isn't reflecting this?
Keep in mind that your 5% dmg from VPLC in WoL or recount is your own dmg excluding your pets' dmg. The output in simulationcraft however includes pet dmg. As demo, and especially on yorsahj where your pets are going to a higher % of you dmg, VPLC will appear to Deal a higher % of your dmg b/c it's still procing at roughly the same rate. In actuality, it's doing roughly the same expected amount. Check your logs from a single target fight and you'll see the difference in %
Cunning of the Cruel has had its proc chance tripled, but it's damage reduced by two thirds. I guess their intention is for the overall effectiveness of the trinket to remain the same, but has anyone checked that they didn't break it etc?
I have been running alot of trinket simulations today and I noticed something unusual and unexpected with the affliction trinkets. Using the Affliction T13H profile I found that Heroic Insignia of the Corrupted Mind is a ~1100 DPS (49347 vs 48186) increase over Heroic Will of Unbinding. Can someone confirm this or did I miss something?
I have been running alot of trinket simulations today and I noticed something unusual and unexpected with the affliction trinkets. Using the Affliction T13H profile I found that Heroic Insignia of the Corrupted Mind is a ~1100 DPS (47965 vs 46871) increase over Heroic Will of Unbinding. Can someone confirm this or did I miss something?
without that line it will let WoU stacks fall off during execute and it ends up showing as a lot less dps than it actually is if you play correctly sub-25% with it.
without that line it will let WoU stacks fall off during execute and it ends up showing as a lot less dps than it actually is if you play correctly sub-25% with it.
I have that line present in the Will of Unbinding action list. It serves no purpose and breaks the simulation when used in the Insignia action list, hence why I modified the DS line.
I was never been able to understand this line. And while I am talking about SF, I need to make sure that I read this correctly from simcraft, that SF travels at the speed of 24yards per secons?
I was never been able to understand this line. And while I am talking about SF, I need to make sure that I read this correctly from simcraft, that SF travels at the speed of 24yards per secons?
As far as I'm able to tell, that just makes sure that the sim doesn't cast Soul Fire so late that there's no window between when the buff falls off and the travel time of soul fire between your cast and when ithe buff is refreshed in which an incinerate can hit the target, resulting in an incinerate that wasn't affected by the ISF buff.
I could be wrong, that's just my interpretation of that line.
That line hails from back when ISF was a haste buff and thus more essential. It's quite possible a slightly different set of conditions is more optimal now - feel free to play with it and report back any findings.
How can I model using drain life during demon soul for affliction? I can import a warlock with the drain life SPEC fine and use drain life in the rotation, but as soon as I add drain life to a standard affliction spec's rotation simcraft crashes. Any help?
actions+=/drain_life,if=buff.demon_soul_felhunter.up
Add this to your normal Shadow Bolt profile, just one step before "actions+=/shadow_bolt"
If im not totally wrong, this should do it.