maxensas/xiletrade

"Bow Attacks fire # additional Arrows" is not parsed from Ctrl+Alt+C text

SnosMe opened this issue · 2 comments

SnosMe commented

Yep, I know it has fixed roll for this item, yet it's good to have correct parsing code in app.

Item Class: Bows
Rarity: Unique
Death's Opus
Death Bow
--------
Bow
Quality: +30% (augmented)
Physical Damage: 91-203 (augmented)
Critical Strike Chance: 7.25% (augmented)
Attacks per Second: 1.32 (augmented)
--------
Requirements:
Level: 70
Str: 70
Dex: 155
Int: 48
--------
Sockets: G-G-G-R-R-G 
--------
Item Level: 81
--------
{ Implicit Modifier — Attack, Critical }
45(30-50)% increased Critical Strike Chance (implicit)
--------
{ Unique Modifier — Damage, Physical, Attack }
115(100-125)% increased Physical Damage
{ Unique Modifier — Damage, Critical }
+50% to Global Critical Strike Multiplier
{ Unique Modifier — Attack }
Bow Attacks fire an additional Arrow
{ Unique Modifier — Attack, Speed }
10% increased Attack Speed
{ Unique Modifier — Attack }
Bow Attacks fire an additional Arrow
{ Unique Modifier — Damage, Physical, Attack }
Adds 17(10-20) to 30(30-35) Physical Damage
--------
The overture stretches thin,
The chorus gathers to begin.
Stacatto, drone, a rest drawn long,
Another hears Death's final song.
--------
Corrupted

image

Item Class: Bows
Rarity: Unique
Death's Opus
Death Bow
--------
Bow
Quality: +30% (augmented)
Physical Damage: 91-203 (augmented)
Critical Strike Chance: 7.25% (augmented)
Attacks per Second: 1.32 (augmented)
--------
Requirements:
Level: 70
Str: 70
Dex: 155
Int: 48
--------
Sockets: G-G-G-R-R-G 
--------
Item Level: 81
--------
45% increased Critical Strike Chance (implicit)
--------
115% increased Physical Damage
Adds 17 to 30 Physical Damage
10% increased Attack Speed
+50% to Global Critical Strike Multiplier
Bow Attacks fire 2 additional Arrows
--------
The overture stretches thin,
The chorus gathers to begin.
Stacatto, drone, a rest drawn long,
Another hears Death's final song.
--------
Corrupted

image

maxensas commented

Hi SnosMe, thanks for your contribution !
I will add this parsing rule in the next release and check for any missed ones.