diff --git a/items_2_help.html b/items_2_help.html index 384d0ec..79a3c72 100644 --- a/items_2_help.html +++ b/items_2_help.html @@ -36,7 +36,7 @@

The advanced item search interface uses two separate expressions: one for filtering items and the other for sorting them. The idea is that you can filter for items matching a set of criteria that are absolutely necessary for the item you want, then sort the remaining items to find the optimal build component. The expressions themselves are mathematical formulae that compute values from the properties of items, such as their damage values and identifications.

As an example, suppose you want a helmet granting at least 10 intelligence that maximizes spell damage gain for a build using the Nepta Floodbringer. We would start by writing a filter for helmets with our desired bound on intelligence:

{prop:type} {op:=} {str:"helmet"} {op:&} {prop:int} {op:>=} {num:10}
-

Then, wee would write an expression that computes the amount of damage we get from the helmet. To do this, we first check the damage numbers for the Nepta Floodbringer: assuming we aren't using any powders, we have 96–112 water damage scaled by the super-fast attack speed modifier of 4.3, giving us a total of 4.3 × (96 + 112) ÷ 2 = 447.2. We then multiply in the spell damage and water damage modifiers and add raw spell damage, giving us:

+

Then, we would write an expression that computes the amount of damage we get from the helmet. To do this, we first check the damage numbers for the Nepta Floodbringer: assuming we aren't using any powders, we have 96–112 water damage scaled by the super-fast attack speed modifier of 4.3, giving us a total of 4.3 × (96 + 112) ÷ 2 = 447.2. We then multiply in the spell damage and water damage modifiers and add raw spell damage, giving us:

{prop:sdRaw} {op:+} {num:447.2} {op:*} {op:(}{prop:sdPct} {op:+} {prop:wDamPct}{op:)} {op:/} {num:100}

And, voilĂ ! In the blink of an eye, we've discovered that Caesura is the best helmet for our criteria, granting 448.14 spell damage.