[Release] Path of Exile Item Info Script - Affix Breakdown and More (Version 1.8.6)
|
This script just keeps getting better and better.
|
|
|
I am glad you are back hazydoc, this script is awesome. I stopped using it a while ago because it showed a lot of wrong information and was misleading me a lot so I decided to just check stuff manually instead. I am ready to use the script again :)
Quis custodiet ipsos custodes?
| |
|
[please remove, double post]
Last edited by restoutlife on Jan 4, 2015, 4:49:50 AM
|
|
|
[UPDATE] Some mini-fix again from my last update(sorry my bad, I swear I didn't see these stuff from that last update)
1/04/2015 Fixed Windripper's values for its added lightning(sorry, my bad!) Fixed Reaper's Pursuit's wrong implicit values Fixed Pyre's Implicit values not separated from the item mods Now using hazydoc's 1.7.7 current official version
Spoiler
"
Spoiler
Last edited by restoutlife on Jan 4, 2015, 4:55:15 AM
|
|
|
1.7.8 is out! Changes:
" EDIT: 1.7.9 is out! Changes: " PoE Item Info tooltip script - reveal detailed affix breakdown for any rare or unique! http://www.pathofexile.com/forum/view-thread/790438 | IGN: Sadou Last edited by hazydoc on Jan 4, 2015, 10:35:25 PM
| |
|
Looks like the most recent version was commit with a small error.
Missing quotations around the question mark in line 201, works after I put in the other one. The line in question is: AffixDetailEllipsis := "? IGN: ThisIsAReallyBadIdea Last edited by KingOfTheWild on Jan 5, 2015, 3:43:03 PM
|
|
" Which Editor are you using to display the script? The ? should be an ellipsis character "…" so depending on how your editor interprets the script's file encoding the ellipsis character might show as a question mark and if your editor cannot display wide characters it might gobble up the missing quotation mark as well. If your editor supports it, try changing the interpreted file encoding setting to ANSI or Unicode (both should work). I just checked with the latest version I am about to release in EditPlus 3, Notepad, and Scite4AutoHotkey and they all display the AffixDetailEllipsis line correctly. EDIT: 1.8.0 is out! Changes: " PoE Item Info tooltip script - reveal detailed affix breakdown for any rare or unique! http://www.pathofexile.com/forum/view-thread/790438 | IGN: Sadou Last edited by hazydoc on Jan 5, 2015, 8:42:10 PM
| |
|
I can't run the script, it just says
 so sad to that. what can i do? ty for great script. IGN : NamuHangru (lvl 100)
IGN : Namu_Hangru (lvl 100) Crit Physical MF Archer iir 253 & iiq 103 |
|
" What AHK version are you using? As a quick fix: open the script in a Unicode capable editor (Notepad.exe should do) and save as file encoding Unicode. Alternatively, you can just change the ellipsis character in the line "to for example three dot characters as in ". I am pretty sure this happens because I changed the file encoding again a few versions back but I am puzzled as to why there should be an error since I have 4 different AutoHotkey versions installed and I test the script with each and every one of them. I usually test the script against AHK ANSI, AHK Unicode 32-bit and AHK Unicode 64-bit, AHK Classic (v1.0). AHK Classic just doesn't work anymore but that is not due to file encoding but rather AHK features used but the others should work fine. I can change the file encoding back to Unicode of course but in theory AHK Unicode should read AHK ANSI scripts just fine and AHK ANSI then shouldn't display that line 1 error because it can't interpret the 16-bit Byte-Order-Mark. Oh well, I might have to scrap the AHK ANSI compatbility again and go back to just requiring a Unicode capable AHK. PoE Item Info tooltip script - reveal detailed affix breakdown for any rare or unique! http://www.pathofexile.com/forum/view-thread/790438 | IGN: Sadou Last edited by hazydoc on Jan 6, 2015, 7:18:23 AM
| |
" What AHK version are you using? As a quick fix: open the script in a Unicode capable editor (Notepad.exe should do) and save as file encoding Unicode. Alternatively, you can just change the ellipsis character in the line "to for example three dot characters as in ". I am pretty sure this happens because I changed the file encoding again a few versions back but I am puzzled as to why there should be an error since I have 4 different AutoHotkey versions installed and I test the script with each and every one of them. I usually test the script against AHK ANSI, AHK Unicode 32-bit and AHK Unicode 64-bit, AHK Classic (v1.0). AHK Classic just doesn't work anymore but that is not due to file encoding but rather AHK features used but the others should work fine. I can change the file encoding back to Unicode of course but in theory AHK Unicode should read AHK ANSI scripts just fine and AHK ANSI then shouldn't display that line 1 error because it can't interpret the 16-bit Byte-Order-Mark. Oh well, I might have to scrap the AHK ANSI compatbility again and go back to just requiring a Unicode capable AHK. PoE Item Info tooltip script - reveal detailed affix breakdown for any rare or unique!
http://www.pathofexile.com/forum/view-thread/790438 | IGN: Sadou |
