Usage
Unique Matcher currently supports only resolution of 1920x1080px in fullscreen mode. If you play PoE in windowed mode, the matching will likely fail.
NOTE: You can optionally force enable other resolutions by setting
OPT_ALLOW_NON_FULLHDinunique_matcher/constants.pytoTrue, but you have been warned.
Using socket notches other than the basic ones will decrease accuracy on socketed items (the more sockets, the lower the accuracy). For best results use the basic ones.
In the Installation section you should have started the AHK shortcut script. By pressing Win+s a new screenshot is put into data/queue folder.
The app processes screenshots from the data/queue folder, on success they are placed in data/done and on error into data/errors.
Results are saved into a CSV file in data/results. The files are named according to the current date and time. If you click the Create snapshot button, a new file will be created and used until the app is closed or you click the button again. This is useful to differentiate between several runs/maps/locations.
As already mentioned, Socket Notches affect the accuracy. Here you can see the difference:
| Good | Okay | Not so good |
|---|---|---|
 |
 |
 |
You can of course test the app with any notches, it should probably still be very accurate.
Since the item image is semi-transparent, you can see what's in the background and so does Unique Matcher. If the item cannot be detected, try moving it somewhere without stuff in background. See different Maligaro's Cruelty for example:
| Good | Problematic | Problematic |
|---|---|---|
 |
 |
 |
General rule of a thumb is that the more uniform the background, the better the results.
These items are 1x3 in inventory, but if there are 2 or 3 sockets, they obscure the item image. This can result in mis-detected items. See Taproot for example:
This item base is known to cause issues. If you take a look at Turquoise Amulets uniques, Maligaro's Cruelty is a bit similar to Ungil's Harmony. If this is combined with some background noise, these two can be mis-detected.
In case you find an issue, report it in Issues and include the last log from data/logs.