[Release] Path of Exile Item Info Script - Affix Breakdown and More (Version 1.8.6)

"

Won't work at all for me. AHK loads the script just fine, but Ctrl+C does nothing. Once, when I opened the script, it showed the info for an item in my inventory (but on my desktop, not in game).

"

_D_S_ wrote:

I updated it further, just occured today to me that there were still the old values for crit multi on amulets and quivers

/your script folder/data/CritMultiplier_AmuletsAndQuivers

8|8-14
21|13-19
30|20-24
44|25-29
59|30-34
73|35-38

I also forgto to update the IIQ stat for the mf flask, updated version in my old post or http://www33.zippyshare.com/v/52247905/file.html

"

chumppi wrote:

@zaregu - Download the latest version of AHK from http://ahkscript.org/download/

Autohotkey.com is an outdated website.

"

kentgrav wrote:

Just an FYi to anyone that uses the TierRelativeToItemLevel Option. It doesn't display correctly if the Item level happens to be equal to the Level of the affix Tier. I.E. in this case:

Rarity: Rare
Morbid Shelter
Sadist Garb
--------
Evasion Rating: 463 (augmented)
Energy Shield: 152 (augmented)
--------
Requirements:
Level: 68
Dex: 103
Int: 109
--------
Sockets: G-G B G
--------
Itemlevel: 69
--------
+60 to maximum Mana
48% increased Evasion and Energy Shield
+8 to maximum Energy Shield
+33% to Cold Resistance
+7% to Lightning Resistance
39% increased Block and Stun Recovery

The max mana tiers are:

1|15-19
11|20-24
17|25-29
23|30-34
29|35-39
35|40-44
42|45-49
51|50-54
60|55-59
69|60-64
75|65-68


So it should display that the Tier for the mana on this item is T1 for its item level. It displays it as T2 because the item is exactly Item level 69. Currently it evaluates this using the following code:

If (TierRelativeToItemLevel AND (RangeLevel > ItemLevel))
{
Break
}

It should read:

If (TierRelativeToItemLevel AND (RangeLevel >= ItemLevel))
{
Break
}

You will then no longer have this problem. Cheers.

"

Sublimeasaurus wrote:

Every time I run this script, I get an error and it exits. This is both with the current version 1.7.5, and with the bleeding edge version. I cannot find the text given in the error message.