POE-ItemInfo icon indicating copy to clipboard operation
POE-ItemInfo copied to clipboard

Unique Items original value display

Open 4GForce opened this issue 7 years ago • 8 comments

This seems to happen for every unique item that have range values. The file is properly read since the tooltip shows the range but it fails to show the original value.

uniqueitemvaluesontooltipmissing

4GForce avatar Jan 30 '17 21:01 4GForce

Unique data is completely read from a file, just by the name of the item. The script does not compare the affixes.

The potential problem with trying to include the personal rolls is that GGG changed the affix order on uniques every now and then or that the wiki has a different ordering, so we can't be sure that the lines read from the file are exactly corresponding to the lines on the item, so the inserted number might be wrong. If we read all the affixes from the ingame item and only add the roll ranges from a file, we might add them to the wrong line. Either way, I don't see an easy way to be completely safe. That's why rolls are not included yet.

aRTy42 avatar Jan 30 '17 21:01 aRTy42

You'd have to match the mod names, this of course bears the risks of having old data because GGG changed something. But that's what I'm doing for TradeMacros advanced search, that's the main reason for updating those files at every script start from the repo (no release neccessary).

Eruyome avatar Jan 30 '17 22:01 Eruyome

You can't just parse uniques like they are rares? (Or is that what Eruyome is suggesting?)

Nightblade avatar Apr 05 '17 05:04 Nightblade

Uniques have lots of stat lines that are special. The parsing for rares is done by matching the stats on an item to text pieces. There is no fancy method involved, the script uses about 3000 lines of code to account for everything.

Making that work for uniques would require some sort of file or database to look everything up or match against. You can certainly do that, but it is basically a complete rework of the current unique handling and introduces the need for background updates on script start etc. which comes with more opportunities for issues.

The benefit does not seem big enough to me to start such a rework.

aRTy42 avatar Apr 05 '17 18:04 aRTy42

Assuming someone provided an always perfect database of uniques for current patch. Would the effort involved in rewriting the parser be worth it? I haven't looked into this part of the script yet, but this has been an issue I've been wanting to fix too. Could you separate unique and rare parsing completely?

theWarFlower avatar Apr 05 '17 23:04 theWarFlower

They are already separated. The unique "parsing" is just loading prepared data from the uniques.txt file by item name. That's the point here. Adding features like reading the values ingame would require a completely new method for handling uniques.

aRTy42 avatar Apr 05 '17 23:04 aRTy42

Ahh I see now i misunderstood, I should have looked first. It's an entire new project. Thank you for your efforts!

theWarFlower avatar Apr 05 '17 23:04 theWarFlower

Came here to suggest this. If its too much work to match mod names on wiki and item being checked then maybe just display all the mods from the item with their text on the right side of wiki data without trying to match them. With some kind of separator like line of '|' symbols. Will make comparing much faster (especially for people who use fixed position of a tooltip) What do you guys think?

artofvs avatar Jul 30 '17 12:07 artofvs