PoE-VIEW2

PoE-VIEW2 (PoEView2) is a desktop tool for Path of Exile. It displays characters and stash tabs through the official GGG API, searches them league-wide across all tabs, and keeps the data up to date automatically without exhausting the API rate limit. If the GGG API is unreachable, PoE-VIEW2 keeps working from the local cache.

Login runs via OAuth2 directly against api.pathofexile.com. PoE-VIEW2 never sees your password, and no third party is involved in the login. The access token is stored in the Windows Credential Manager. The account button in the toolbar offers "Log out" once you're signed in — this only removes the locally stored token; it does not revoke the authorization on GGG's side. To fully revoke it, do that from your GGG account settings.

The "2" in the name is history: the first PoE-VIEW was a LabVIEW program, and this one is the rewrite in Python — the second tool of that name. Its registration with GGG came along from the older one, which is why the sign-in page still asks you to authorize "PoE-VIEW" without the 2.

Screenshots

All screenshots show synthetic demo data, not a real account.

League-wide search with *: stash tabs and characters appear together in one table, with the Tab column showing where each item came from. Type filters are above, the rate-limit dashboard below. The Value column holds the poe.ninja price; the table starts sorted by it, cheapest first.

A single stash tab with an item selected; its mods are shown in the detail panel below. The bar in front of each line shows where that roll sits on the real tier ladder (or, without a known ladder, between the worst and best roll you have ever seen), and the tier stands behind the line.

A character inventory right after a refresh: rows that are new or changed are highlighted, items that disappeared stay visible for one cycle in grey and struck through. The panel underneath logs what moved through the inventory of every character — pulled open here, collapsed to a single line by default. On the right, the levelling panel shows gem progress and the last three hours of experience.

The mod collection as an album: one card per mod, a coloured edge and symbol for its theme, a row of slots — one per tier the game can roll, filled means you have rolled it — and a golden frame for a complete set. Dashed cards are ghosts: mods the game knows that you have not collected in this league yet. The score line above counts collected of possible; the panel below is the selected mod's ladder, straight from game data, with the tiers you still miss left empty.

Every zone you have ever entered, with the monster level the game generated it at. A zone does not have a tier — a visit does: maps are numbered items that send you to a map of that tier or lower, so the same zone shows up at several levels. Expand one to see each level with its own visits, deaths and average time. Here Bazaar was run at tier 4 and at tier 5, and the Azurite Mine separates its base (monster level 34, delve depth 0, where nobody dies) from the depths below it.

Your passive tree, with named configurations for the fights that need them. Selected here: "Max fire res" — red is what you would refund, green what you would take instead, white stays. Click nodes to build a configuration right in the picture; the background shows whose part of the tree you are in.

Features

Browsing and searching

• OAuth2 login (PKCE) against the official GGG API. The access token is stored in the Windows Credential Manager, not in plain text on disk. Starting without a valid login opens a welcome window that names what is already stored locally and offers to log in or carry on offline; if the login expires while the app is running, a separate window says so. Both stay above the main window without blocking it — local data stays browsable either way.
• Stash tree with folders; special tabs (map and unique stash) are automatically grouped by section or category. Hide empty takes tabs known to hold nothing out of the view — tabs never loaded stay, and every tab keeps being refreshed in the background, so one reappears as soon as it holds something.
• Item table with icon, source tab, position (tab number and grid coordinate, distinguishing tabs with the same name), name, base type, level, quality, stack size, item level, requirements (level, Str, Dex, Int), mods, and value. The mods cell lists every mod the item has, in the order the game writes them — enchant, implicit, explicit — with | between the groups; hover for the full text on separate lines.
• Zone table (toolbar button "🗺 Zones"): every zone you have ever entered, with the monster level the game generated it at — grouped into story, maps, side areas, labyrinth, delve, special areas and the places without monsters, and exportable as CSV. It is built from Path of Exile's own Client.txt, which names the area level on every single zone entry, and it keeps what it has seen even after the game truncates that log. Columns: group, map tier, monster level, visits, entries, deaths, monsters and the average time per visit. Monsters is the number killed per visit, worked out from the game's own /kills answers in that log: the pace between two readings with exactly one map in between, times the average time per visit. It fills in as you use /kills — including any readings you took before installing PoE-VIEW2. XP/h is what your character would earn there now: the pace measured before the level penalty, times today's penalty, so it stays right as you level up. It fills in from now on, from publications that cover exactly one zone. The monster level cell is shaded by how much experience you still get there: green at 100 %, yellow from 50 %, red below. A visit is one map, however often you went in and out of it: walking to a vendor and back through the portal is still the same visit. The game writes a seed for every area it generates, and the same map keeps its seed across returns. Entries counts every time you went in, so many entries per visit mean many trips out and back. Hideouts and towns count every entry as a visit. Updates itself on every zone change while it is open, keeping your filters, expanded zones and scroll position; there is a ⟳ Refresh button too. Expand a zone to see one row per monster level, each with its own visits, deaths and average time. A zone does not have a tier — a visit does: maps are numbered items ("Map (Tier 4)") that send you to a map of that tier or lower, so the same zone shows up at several levels, and averaging across them mixes a tier 1 run with a tier 9 one. Separated by league, because the atlas is rebuilt every season (across the last switch, 44 of 233 areas changed level) and the leagues of one season differ in content. Starts on the league you played most recently. Filter fields right under the column names: type >=70, <45, =Cells or any substring and the table filters as you type, with the same completion over the column's values as the item list.
• Configurable columns: which columns are shown and in what order is set either in the settings dialog (checkboxes and drag & drop) or via a quick toggle in the header's right-click menu. The choice is saved between sessions.
• Column filters in a row of fields right below the column names, supporting comparison expressions such as >=20 for quality or <45 for item level, with autocomplete over the values actually present in that column. Filters, including pinned ones, are kept between sessions.
• Picks up where you left off: window position and size (including maximised), the dividers between the panels, the selected character or stash tab, the sort order, and in the zone table the group, search, filters, sort order, expanded areas and window size.
• Search like the in-game stash search: several keywords separated by spaces must all match, so life resistance finds items carrying both even though the two words never stand next to each other. Quotation marks hold a phrase together ("maximum life"), ilvl:84 and tier:16 match exactly that item level or map tier, and Ctrl+F jumps to the field. Regular expressions are on by default (toggle .*), so patterns built on sites like poe.re work unchanged — sockets are indexed in the in-game notation (R-R-G), making link patterns such as r-r-g|r-g-r|g-r-r work directly. Searched is everything the item says about itself, down to the names of the gems socketed into it.
• League-wide search across all loaded tabs and characters at once. * as the search text lists the entire holdings, useful for exporting a whole league.
• Type filters for Normal, Magic, Rare, Unique, Gem, Currency, Divination Card, and Other, shown as color-coded checkboxes next to the league selector.
• Multi-selection in the stash tree: Ctrl- or Shift-click several tabs, or pick a folder, to view their items together. This shows only what is already cached and never triggers a fetch of its own; tabs that have never been loaded are named in the status bar instead.
• CSV export of the visible, filtered items or of just the selected rows — from the toolbar or the right-click menu of the table, the stash tree, and the character list. The file carries the full item detail: position, requirements, sockets and links, every mod category, influences, flags such as mirrored or fractured, note, and value. The complete, unmodified API object per item is available as an optional extra column.

Item and character views

• Character view: equipment and inventory appear in the same table as stash items and are just as searchable and filterable.
• Character paperdoll (double-click a character): equipment laid out as a doll instead of flat table rows, including the jewels socketed in the passive tree.
• Character sheet export (right-click a character): a Markdown document laid out like an old pen-and-paper RPG sheet — equipment by body slot and the gems socketed into each piece, with their level, grouped by which ones are actually linked. No computed stats (life, resistances, DPS): the API doesn't provide them, they come from the game client simulating the full passive tree. The sheet ends with the passive tree: ascendancy, keystones, notables and masteries with their values, the small passives added up, your jewels, and what is within reach — every notable, keystone and jewel socket at most four more points away, with the path. Paste it into an AI chat or a forum post to get advice on where to put your next points. Ruthless characters get GGG's Ruthless tree with its own values. The tree data comes from GGG's skilltree-export on GitHub and is refreshed weekly.
• Passive tree window (right-click a character > Passive tree…): the current tree, a history of every change, and named configurations — say "Max fire res" for a boss that needs it. Save the current tree as one, or import a link from the official tree planner, a Path of Building code or a pobb.in / pastebin link — a build with several trees (one per levelling stage, say) becomes one configuration per tree you tick. Right-click a configuration for rename, duplicate, delete and the rest (the tree you are looking at stays; Ctrl/Shift-click to delete several at once); the usual shortcuts work (Ctrl+S, Ctrl+Z, F2, Del, Ctrl+D, and Ctrl+V in the list imports whatever tree or build link is on the clipboard). Compare with shows any configuration against any other — what to change going from "Lvl 61-80" to "Lvl 81-90", say — instead of against your current tree. A build's trees stay together under a collapsible group, and each configuration has its own notes (a build's Path of Building notes come with the import). Leveling plan: right-click a configuration and Level towards this — it becomes the goal, and the plan leads there from your class start one point at a time (each next to an earlier one; damage first, then defence and damage by turns; masteries as soon as they open up; Set order lets you click your own order). One point per level from level 2 (read live from Client.txt), quest points with +1 quest / −1 quest. The tree numbers the next ten points, and on every level-up the status bar and a small always-on-top window name the point to take now; a slider lets you watch the tree grow from 0 points to the goal. When GGG ships a new tree, trees and configurations from the old one stay viewable on the tree they were made on (read-only, marked e.g. "· 3.29.1"). For each configuration you get the respec as a to-do list against your current tree (refund, allocate, change mastery, number of points and the gold it costs at your level) and what it gains and loses in stats. Open in planner shows any of them in the official planner. Everything is grouped by theme — defence, minions, offence, utility — with colours and symbols, a totals summary on top (all allocated nodes added up, the key values first), and Within reach is a table you can filter ("fire res"). The Tree tab draws the tree itself — zoom, drag, search — and shows a configuration's respec in green and red right on the tree, with the points used and the most your level allows (all 24 quest points, 23 if you helped a bandit). The background marks each class's area (red Strength, green Dexterity, blue Intelligence, striped for hybrids), with class and ascendancy names around the edge. Every class's ascendancies sit just outside its area (yours outlined in gold, with your allocated nodes). Build configurations right in the picture: click a node to allocate it with the shortest path, right-click to refund it (and whatever would be cut off), click a mastery to pick its effect (its tooltip lists them all). The tooltip tells you the cost first; changes stay a draft until you save them. Ctrl+C copies the name and ID of the node under the mouse (Ctrl+Shift+C with its stats); type an ID into the search to jump to that node.
• Enlarged item view (double-click an item): large icon and the full property and mod text without the compact detail panel's line clipping. Divination cards show their real artwork from GGG's own CDN instead of the generic icon the stash API returns for every card.
• Item value via poe.ninja prices: a Value column (chaos or divine depending on magnitude) plus the total for the visible items in the status bar. Covers currency, fragments, uniques (including 5- and 6-link pricing), gems (matched exactly by level, quality, and corruption), divination cards, scarabs, essences, and fossils. Unknown prices stay empty rather than showing 0. The status bar also names how old the current price set is, so a genuinely cheap item is distinguishable from a stale price.
• Copy for Path of Building: right-clicking an item puts it on the clipboard in the game's own item text format, ready to paste into PoB. Aimed at stash items in particular — PoB imports characters by itself, but cannot reach your stash.
• Configurable item lookups: right-clicking an item can open it in reference sites you define yourself (name plus a URL template with a {slug} placeholder). Nothing is preconfigured — see Data sources.

Mod collection

• Every mod line the API shows you is collected — from your stash tabs and your character inventories alike: how often seen, lowest and highest roll, on which item levels — kept apart by league (temporary leagues each get their own pot, the permanent ones share one) and by rarity, with corrupted items counted separately. The collection fills itself from the existing cache on first start and grows from then on without a single extra request. A sighting is one item passing through your hands; the same item fetched again on the next refresh does not count twice. The collection only learns what is identified at the moment GGG publishes it. The API sends no mods at all for an unidentified item, so anything you identify and sell before the next publication never reaches it.
• A bar in front of every mod line in the item panel: where this roll sits on the real tier ladder of that mod — full means the best roll the game can give — with the tier (T1 gold, T2 silver, T3 bronze) behind the line. Where no ladder is known, the bar compares against the worst and best roll you have seen yourself. ✦ marks a mod seen for the first time.
• Real tier ladders from game data: PoE-VIEW2 downloads public game data (RePoE) in the background at start and builds the tier ladder of every prefix and suffix per item base — checked against a real stash: 81 % of all tier-capable sightings have a proven ladder. Hybrid mods (e.g. "Fire and Lightning Resistances") are a known gap.
• The album (toolbar button "📚 Mods"): one card per mod, with a coloured edge and symbol for its theme, a row of tier slots (filled = rolled) and a golden frame for a complete set. Ghost cards show what the game can roll but you have never collected in the selected league; the score line reads "73 of 313 mods collected". The detail panel lists every league and rarity the mod was seen in and its full ladder — T1 at the top, unlock level, how often seen, your best roll, the missing tiers left empty. Search, kind/league/rarity filters, sorting by name, newest finds, most seen, most complete or most missing; a table view for serious searching; ⟳ reloads what the collection gained while the window was open. The album opens on the league you are viewing.
• Base stats are collected too: armour, evasion, energy shield, ward and block per armour type, physical and elemental damage, crit and attacks per second per weapon type — as cards of their own and with the same bar on the item panel.

Levelling

• Experience per hour while a character is open, at no extra API request — level and experience already come with the response that loads the equipment. It is measured per area, over the time actually spent in there, so hideout time does not water it down and a break does not make it collapse. Once the number is older than a minute, it says so.
• Three-hour graph: one bar per finished area, its width the time spent there. Gaps are real — no experience was made in them. Leaving a map and coming back puts both visits on one dark block showing the rate for the map as a whole, so the cost of the trip outside is visible. An area that cost experience on balance hangs below the line in red, capped at a quarter of the height so one death cannot squash the rest. A line across the graph marks your average rate and says which stretch it covers: it begins at your last level-up, or after a break of more than half an hour, whichever came later, ends with your last section once you have stopped playing for more than half an hour, and is drawn solid and green over exactly that stretch — dashed before it, where it is only a yardstick for the older bars. How long the stretch is stands next to the number. If you lost experience in that stretch, the line names two rates — "⌀ 85K net · 34M gross · 22 min": what you actually kept, and what came in while nothing went wrong. The distance between them is what dying costs you. The rate counts only the time you spent in areas that give experience: hideout, town and the hubs stay out of it, and every map since the last update counts, not just the one you left last. The graph survives a restart: measured sections are stored per account and drawn again next time, so closing the program does not empty it. Time to the next level stands under the rate ("⏱ Level 80 in ~2 h 34 min"), projected from your pace in the zone you are in — or, in your hideout or a town, the last combat zone before it — at that same area level, since the level penalty depends on it. Without such sections it uses your average. Hover over the line to see which rate it used. Hover over a bar to see what it was: the zone (with map tier and area level, or several zones with their times), when, how long in combat, the experience gained and the rate, the level penalty at that area level, deaths in that stretch, and for a map left and re-entered the total for the whole map. Loot is deliberately not in it — it is the one number that could not be told reliably. The bar the tooltip describes is marked with a light band over its whole time span, so even a bar only two pixels tall is easy to find.
• The maps you ran before starting PoE-VIEW2 show up as well, drawn fainter than the measured ones. Their length comes from the game's own Client.txt and is exact; the experience gained while the program was closed is spread across them evenly, which is an estimate — hence the fainter bars. This needs the Client.txt watch, and it only happens when the last stored experience is still within the three-hour window; after a longer break the graph starts empty as before.
• Death counter: with the Client.txt watch enabled, the levelling panel counts the shown character's deaths of the last 24 hours ("☠ 4 deaths (24 h)") and the graph marks each death with a small red triangle at the top edge — even above a green bar. The bars alone cannot show this: each bar is the net of its stretch, and a death inside a good run disappears in it. The count is read from the game's own log, so it survives restarts, and the rolling window means a session running past midnight keeps its count.
• Watched stack sizes: right-click any item and pick Watch stack size to put it in a table filling the right-hand side of the levelling panel. It adds up every loaded stash tab and character of the league, so a glance tells you how much Wild Crystallised Lifeforce you are sitting on. Items left in the map device are missing from the total: the official API does not expose that inventory. A ≥ marks a total that is still missing unloaded tabs. Drag a row to reorder the list; it keeps the order you gave it across restarts and is never re-sorted by amount.
• Gem progress: one narrow bar per socketed gem, its filled height the gem's level, coloured by the attribute it needs — the strip reads as a profile of the character, so the short bars are the gems lagging behind. A thin yellow line inside each bar is the progress towards the next level, and the translucent yellow block below it is what the gem gained since the program started — after a level-up it starts again from the bottom. Hovering a bar opens a table of all gems with the one under the mouse highlighted. A solid bar in a vivid colour marks a finished gem (level 20, or 21 corrupted). A yellow cap means the opposite: the bar is full but the gem is below its maximum — gems never level up on their own, so that is character power waiting to be claimed.

Staying up to date

• Refresh modes (toolbar dropdown), all on the same clock, computed from the rate limit GGG actually reports rather than a fixed number: Auto alternates between keeping the open view fresh and sweeping the rest of the stash, Single focuses only on the current selection, Stash cycles continuously through the whole league, and Pause stops all background requests. Auto additionally keeps a small reserve free so a manual click never waits.
• Change highlighting in the character view: rows that appeared or changed since the last refresh are highlighted, and items that disappeared stay visible for one cycle in grey and struck through. An item whose socketed gem just gained a level turns green instead of turquoise, so a gem-up is distinguishable at a glance from a genuinely new item.
• Item history: a collapsible panel below the table logs the last 120 items that entered, left, or changed quantity in any character's inventory — a quick way to check what you just stashed, sold, or traded. Stack changes carry the difference, for example 53 (+3).
• Optional zone-change trigger (off by default): PoE-VIEW2 can watch the game's own Client.txt (read-only, path entered by you) and reload the open view as soon as the game reports a zone change, which is when GGG's API tends to publish new stash contents. The toolbar shows the zone most recently detected this way, together with the monster level the game generated it at and — when the gap to your character level is wide enough to cost you — how much of the experience still arrives: Chateau (Lv 68 · 14% XP). The penalty is the community's formula, not our own measurement, and it is marked as an estimate wherever it appears.
• Optional /kills reminder (off by default, Settings > Zone Refresh): on entering a new combat zone — not on returning to the same map through a portal — a short gong sounds and a small window at the top of the game's screen asks you to type /kills in chat. It does not take the keyboard away from the game, and closes itself once the answer shows up in Client.txt. Every answer is written to kills-log.csv in the log folder, with the difference to the previous one and the combat zones in between. The window sits above the game in windowed or windowed-fullscreen mode, not in exclusive fullscreen. If you start PoE-VIEW2 while already inside a map, you get the same gong with a yellow frame that disappears after three seconds — your call whether to take a reading for that run.
• Offline mode: during GGG maintenance or a lost connection, the app shows the last known state from the cache, clearly marked as such (📴). A dot in the status bar carries the same information at a glance: green while the API answers, red during an outage, grey before anything has been requested. It returns to green on its own as soon as a request succeeds.
• The league you were in comes back: PoE-VIEW2 starts in the league you last selected, not in whichever one holds the most items.
• Separate cache per account: every GGG account keeps its own local data, so switching accounts never mixes up stash trees, items, or characters. Nothing is deleted in the process — each account keeps its own state, including when you switch back.
• New release notice: at startup the .exe asks GitHub once whether a newer version exists, and if so shows a link to the release page at the right end of the status bar. Nothing is downloaded or installed automatically — you click, you decide. The answer is kept for six hours; without a network connection nothing appears. Switch it off under Settings → Updates. Running from source never checks.
• Rate-limit dashboard with rules, current usage, and active locks.
• Raw data viewer per stash tab, showing the unmodified API response.
• PoE2 raw data (account menu): asks GGG's API for the PoE2 realm and shows the answer as plain text. It asks the same question three times — without a realm, with poe2, and with a made-up value — and writes the verdict above the raw data, so the tool cannot mistake a PoE1 answer for a PoE2 one. Measured result so far: GGG ignores the realm parameter. All three answers are byte-for-byte identical PoE1 data, the invented realm included, so whether an account has PoE2 characters cannot be determined this way. PoE-VIEW2 reads Path of Exile 1 only.

Data sources

PoE-VIEW2 contacts these hosts, and no others:

• api.pathofexile.com — the official GGG API: login, characters, stash tabs, and items.
• web.poecdn.com — GGG's own CDN, for item icons and divination card artwork.
• poe.ninja — for the optional price display (roughly 1.2 MB per league, cached for up to 6 hours). Prices are unofficial community data. Note that SSF leagues are not tracked there at all: without player trading there is no market activity to derive prices from, so the Value column stays empty in those leagues.
• repoe-fork.github.io — the public RePoE export of the game's mod tables (mods, stat_translations, base_items, about 30 MB), for the real tier ladders in the mod collection. Downloaded at start and cached for seven days. The data itself belongs to Grinding Gear Games; it is fetched at runtime and never shipped with PoE-VIEW2.
• api.github.com — one request at startup, to see whether a newer PoE-VIEW2 release exists (the .exe only; kept for six hours, can be switched off under Settings → Updates). It sends nothing about you or your account.

Beyond that, the item lookups in the right-click menu are empty out of the box. PoE-VIEW2 deliberately ships without any preconfigured reference site, so it never opens a third-party page on its own. If you add an entry in the settings dialog, that is your own decision — please check that the site's operator is fine with being opened this way.

Download (Windows, no Python required)

The releases page provides a ready-to-run PoE-VIEW2.exe for every version. Download and run it — no installation or configuration needed. On first launch, clicking "Log in" opens the GGG sign-in flow in your browser.

Windows SmartScreen warns about an "unknown publisher" for unsigned applications. This affects any application without code signing and can be confirmed via "More info" and "Run anyway".

The GGG sign-in page carries a warning of its own, and two things on it look more alarming than they are. It asks you to authorize PoE-VIEW, without the "2" — that is this tool, under the client name it inherited from its LabVIEW predecessor (see the top of this page). Below the permission list sits a red box saying GGG cannot verify that the request came from PoE-VIEW. Every application without a client secret gets that box: a desktop program cannot keep a secret, since it would ship inside the .exe where anyone could read it, so GGG has no way to prove the request came from this program rather than from something that copied the client ID. It says nothing about your particular login going wrong; PKCE and a state parameter are what protect the login itself in transit.

The permissions the page lists are all read-only: your account name, your profile, your leagues, your characters including their inventories and passive trees, and your stashes. The API offers this tool no way to change anything on your account.

Tech stack

• Python 3.12+, PySide6 (GUI), httpx (HTTP), pydantic v2 (data models), keyring (token storage)
• OAuth2 with PKCE against the official GGG API (no client secret required)

Setup from source

git clone https://github.com/peterm2024/PoE-VIEW2.git
cd PoE-VIEW2
python -m venv .venv
.venv\Scripts\activate          # Linux/Mac: source .venv/bin/activate
pip install -r requirements.txt
python main.py

A .env file is not required; the client ID and contact address have working defaults. If you fork PoE-VIEW2 and distribute it yourself, you should override both (.env.example serves as a template):

• POE_CLIENT_ID — defaults to poeview, a public client ID registered with GGG. You can register your own at https://www.pathofexile.com/developer/docs/authorization; the redirect port 64338 must then match the redirect URI registered there.
• POE_CONTACT_EMAIL — the contact address sent in the User-Agent header. Per the GGG documentation, it identifies the application, not the individual user, and should point to your own address if you distribute your own build.

On first launch, the login button opens the default browser for the GGG sign-in. After that, the session stays valid until the token expires; GGG determines the token's lifetime.

To build your own .exe, see RELEASING.md.

Tests

pytest

The test suite covers data models, the API client, the rate limiter, the worker, and the UI logic. It requires no network access.

Documentation

• CHANGELOG.md — changes per version.
• docs/ARCHITEKTUR.md — application structure and the reasoning behind design decisions (in German).
• docs/api-notes/ggg-api.md — observed behavior of the GGG API, including deviations from the official documentation (in German).
• docs/api-notes/poe-verhalten.md — how the game and GGG's servers behave over time, measured rather than assumed: when the API publishes new data, what Client.txt contains, how socketed gems gain experience, and what turned out to be wrong along the way (in English).
• FALLSTRICKE_UND_WORKAROUNDS.md — solved technical hurdles with cause and fix (in German).

Status

PoE-VIEW2 is in daily use. Login, stash and character views, search, filters, CSV export, refresh modes, price display, levelling display, the mod collection with its album, and offline mode all work. The project is developed by a single person and makes no claim to completeness compared to the official PoE website. Bug reports and pull requests are welcome.

License

MIT

Disclaimer

This product isn't affiliated with or endorsed by Grinding Gear Games in any way. It is likewise not affiliated with or endorsed by poe.ninja, whose publicly available price data the optional value display builds on.