Apply the Mythic+ damage multiplier to all damage dealt to a tank in any boss script.
The simulator keeps doing iterations until the Error Target is reached. Auto will use the most appropriate metric: DPS for damage specs, HPS for healers, NPS for tanks.
You can use this setting to change the metric if you are e.g. simulating just DPS for a non-damage spec.
Most boss scripts specify a good default fight length. This setting lets you override it to something custom. Leave blank to use the boss script's default.
The "human delay" is how long it takes a human to react to something happening in the game. Setting min and max to the same value is not recommended,
nobody has that kind of consistency.
"Lag" is the amount of time it takes from when you press a key until something actually happens in-game. This plus "human delay" is how long it takes
you to respond to e.g. a random proc. "Lag" is largely inconsequential when e.g. chaining casts on the GCD.
When chaining spells together (on the GCD or a cast time), a human needs to decide on the next action prior to the current cast or GCD finishing.
This controls how far in advance to anticipate, and the min should be a tad longer than the max human delay + lag.
Setting max to zero will disable anticipation, not recommended as it is unrealistic.
Setting min and max to the same value is also not recommended, nobody has that kind of consistency.
If you use macros, you can execute several off-GCD abilities simultaneously, so this defaults to zero. If you usually press all of your cooldowns
manually and don't use macros, you should add a small but realistic delay between each of your simultaneous key presses, try a range from 40-50ms or so.
The game allows you to queue a spell just before its cooldown is finished, and then it will execute the spell exactly as the cooldown completes.
This can have a minor impact on spell timing, because e.g. you could use a spell just before the previous spell's GCD finishes, but the next
spell won't go off until a small amount of time after the GCD finishes because the chosen spell wasn't quite ready, but it was close enough that
the game let you queue it up.
'Next' will test all minor traits that you can activate right now, and shortest paths to all major (one-point) traits not activated yet.
'Minor' will test adding 3 points to each minor trait individually. If you have 3 or more points in a minor trait already, it will remove 3 points.
'Path' will test all combinations that can be purchased with the specified number of points.
The total number of artifact ranks that you can purchase. All unique combinations of max traits that do not exceed this total will be tested.
The total amount of secondary stats to keep. Combinations that go above or below this amount will be thrown out. Set to blank or zero to turn off
secondary stat total restriction.
An extra restriction on allowed stat combinations: discard combinations that have less or more total stats than a realistic set of gear would have in the specified item level range.
'Explicit' mode you pick the stat combinations that you want explicitly.
In 'Ratio' mode you specify a ratio for secondary stats, and a list of average item levels to test.
The stats will vary using a typical stat budget at each item level, and then try your secondary stats in different ratios at each of those item levels.
If you have a large number of stat combinations, it may be useful to randomly sample a more reasonable number of combinations from the total possible.
When using stat sample mode 'Random', the number of unique stat combinations to randomly select from all possible combinations that you have defined.
Include Stats will include the static stats on a special item when simulating. Isolate Effect will isolate just the special effect of the item.
Note that the static stats will be appended to the total stats of your base/current setup (including the stats in the slot being replaced). This avoids
introducing a dependency on your currently equipped item and skewing results.
Auto will pick DPS for damagers, HPS for healers, NPS for tanks. You can change this to e.g. DPS for a tank though, if that's your thing.
Don't set it to something stupid like NPS for a healer.
This lets you rerun just part of the gearing strategy if you don't need to update all of it, then composite a new gearing strategy from this new data and an old run.
The number of points in the stat dataset. Anything less than 250 is not good. Anything more than 2000 is probably overkill. 500-1000 is a good range for most cases.
Margin of error for each point in the stat dataset. 0.1% will be MUCH slower and is overkill. 0.5% is good, but may be a tad more volatile than 0.25%. Usually increasing the number of data points is better than reducing the error.
When data points are created for testing stats and special item combinations, the player's total stats will be kept within the specified range.
This setting has a very large impact on the results. We recommend a range of about 40-50 ilvls. Especially for tanks, you should pick a range that is appropriate
for the content you wish to tank, e.g. don't do ilvl 800-850 for a Mythic 10 strategy, you will get very weird results.
When evaluating special effects, special items' level or your player's average item level will be varied to test different points, but your stat ratio will remain fixed.
This setting lets you try different stat ratios.
Margin of error for data points used to evaluate special effects (legendaries, sets, relics, trinkets). 0.1% will be MUCH slower. 0.5% will be faster but might be too volatile for some cases, you have been warned.
This is a hardcore feature for varying a rotation parameter. e.g. min 10, max 50, step 10 would do a simulation with a parameter set to 10, 20, 30, 40, and 50.
The 'Until Higher' mode will start at the specified value, and go both up and down in step increments until your defined min/max,
but stop if it ever gets higher DPS/HPS/NPS than the starting point. If start is left blank, will start at min and increment up to max. 'Until Lower' is similar but opposite.