Skip to content

PoB Agent Edition 0.9.5

Choose a tag to compare

@urbanvcode urbanvcode released this 15 Nov 12:20
· 2 commits to main since this release

Public beta. Please report problems.

Tree compare view with a respec planner, the AI can point at things in PoB and show its advice there, and fixes from testing (warnings, character sync, budget planner, weapon trade searches, support advice, Doedre's Tongue, respec mana, passive suggestions). Based on Path of Building Community v2.67.2 (same as 0.9.4). After updating, restart PoB Agent Edition and your AI app.

Added

  • See the AI's passive tree changes on top of your own tree, and plan the respec: the Tree tab's Compare now labels every changed node with a box beside it: "NEW", "REMOVED", "MASTERY CHANGED: old -> new" or "JEWEL CHANGED", in PoB's compare colours (green, red, blue), with the AI's one-line reason under it when it left one. Boxes are placed so they don't overlap; the new "Labels" box hides them. A planner panel beside the tree ("Plan" box) shows what the respec costs (Orbs of Regret, points used of the points you have), one row per change (a notable or keystone with the small passives that lead to it) with its own DPS, EHP and weakest-max-hit change as PoB calculates it, and a tick box per row: untick a change and the total is recalculated at once, with the same warnings as what_if (a skill left without mana, over-reserved mana, attributes short, a resistance falling under the cap, a lost immunity, nodes that lose their path). Click a row to centre the tree on that node. "Save as new tree" keeps the ticked changes as a new tree; your own tree is never changed. The Compare list also has "Other build..." (any saved build of the same class) and "Last sync" (your character as it was at the previous sync). Mastery swaps and ascendancy refunds are counted but not priced.
  • Compare any two trees, and see which changes to take first: the Compare list also has "Guide..." (any stage of an imported guide) and "Paste code/link..." (a PoB code or a pobb.in, poe.ninja, pastebin or maxroll link, loaded only for comparing). A tree of another class still shows its differences, with a clear "the class differs" note. Changes are numbered in the order to take them (best gain per point or Orb of Regret first, but never before the nodes they need; refunds start at the edge of the tree), and nodes and boxes are coloured by their gain: green for damage, blue for defence, red for a loss, brighter for bigger, with a legend and a button back to PoB's own colours. Hover a changed node to see what changed, why (the AI's note) and its own gain. Each row has an "Apply" button, and "Apply ticked" / "Apply all" write the changes into a new tree; your own tree is never changed. Jewels, cluster jewel nodes and mastery choices that differ are labelled too.
  • The AI can point at things you can't find in PoB: ask "where is the spell suppression mastery?" and the AI marks it in the window: a pulsing ring around the node with a numbered box ("1. Spell Suppression Mastery: pick ..."), its path from your tree, and the tree centred on it. It can also mark an item slot or flask, a skill group or gem, a Configuration option or a Calcs row, several at once numbered 1, 2, 3 for step-by-step help. Marks stay until you click them away or press "Clear AI marks", are never saved in the build, and the PoB window is never opened or brought to the front for them.
  • Marks that guide you step by step: marks now come in styles (pulsing ring, blinking outline, glow, arrow) and meanings: green for "do this", red for a problem, blue for information, in colours that stay distinct with colour blindness. A single mark (or the current step) gets a spotlight that dims the rest, and the tree glides there instead of jumping. The AI can run a guided tour (Next / Back on the box), light up the route to a passive numbered in the order to take it, point at one mod line of an item, show what a candidate item would replace with the stats that change (green better, red worse), show a gem swap with socket colours or where to move a gem, and add PoB's gain to a mark ("+2.7% DPS / +15% EHP"). Clicking a link in the AI chat panel marks that node, item or gem too. "Show AI marks again" brings back the last marks for a minute after clearing, and the AI can replay earlier ones. "Motion: off" next to "Clear AI marks" stops all pulsing, blinking and zoom animation (remembered). Marks use PoB's own UI units, so they follow its UI scale.
  • The AI shows instead of only telling: when PoB is open, every AI client is now told to show its advice in the window (marks, a guided tour, or the tree compare view) and keep the chat for the numbers and the why. Suggestions from the optimiser, passive and support-gem suggestions, anoints, guide comparisons and what_if now come with a ready "Show it in PoB" step, with PoB's gain on the mark. It never opens or brings the PoB window to the front.
  • The AI can open that view for you: set_view { view: "TREE", compare: 2 } (a tree number or name, a build name, "guide::", "last sync", a PoB code or link; compare: false turns it off) switches the window to the Tree tab with the planner open. compare { tree } gives the AI the same list of changes, gains, respec cost and warnings (skip unticks changes, save_as keeps the rest as a new tree), compare { a, b } compares any two of those without opening either, edit { op: "apply_tree" } applies changes into a new tree, and edit { op: "spec_notes" } lets it write the one-line reasons shown in the boxes (saved in the build file). optimise and what_if { keep } now say in one line how to show passive changes on the tree.

Fixed

  • Support gem advice now counts the shock your skill applies itself: PoB only counts a shock (or chill) on the enemy when Configuration says "Is the enemy Shocked?", so a skill that shocks on its own was measured as if it never did. Supports that add raw damage then looked better than ones that keep the shock. The worst case was Elemental Focus, which stops the skill inflicting ailments, ranked above Volatility. suggest { kind: "gems" } and the optimiser's support swaps now rank with the shock and chill your skill inflicts, sized by PoB's own shock calculation for the enemy you set, and say so ("Counts your own shock (~28% more damage taken)"). A shock below PoB's 5% minimum (common on pinnacle bosses) is not counted, and the result says that too. A support that stops the skill inflicting ailments is ranked without them, even when the config says the enemy is shocked, and is flagged: "you lose your shock (~28% more damage taken), chill and freeze". what_if and edit warn when a change takes away an ailment the skill was applying, and when the config would still count it.
  • The 3.30 Doedre's Tongue now works, so a lightning spell can ignite: PoB did not understand "All Damage can Ignite against Cursed Enemies" (or the Shock and Freeze versions), so it added nothing and an Arc build with a curse showed no ignite at all. Those lines are now understood: with a curse on the enemy, lightning damage ignites (and freezes or shocks with the other versions), and without a curse it doesn't. PoB's own item list has the 3.30 Doedre's Tongue (30-35% resistances, 25-50% chance to Freeze, Shock and Ignite, one of the three new lines as Ignite / Shock / Freeze versions); the old one is kept as "Pre 3.30.0". PoB still does not model "Cursed Enemies cannot inflict Elemental Ailments on You".
  • what_if and edit say when PoB doesn't understand an item line: a custom item for theorycraft (a new league's unique, say) can have lines PoB can't read, which silently count for nothing. Equipping an item now lists every such line ("Warning: PoB did not understand this line of Doedre's Tongue (Amulet), so it adds nothing to the numbers").
  • Every PoB warning is checked, not only mana: whatever PoB's side bar lists under "Warnings" (an attribute requirement not met, unreserved mana below zero, too many gems in a slot, and so on) now shows in what_if and edit as warnings that are new or gone after the change. The optimiser names such a warning as a side effect and ranks those suggestions after the ones that add none. diagnose lists every skill that can't be used and the full warning list.
  • A character sync after gear changes no longer turns your main skill into an aura: the game sometimes lists your socket groups in a different order (gloves first, say), and the sync used to keep the group's number instead of the skill, so the synced build could come back with Haste as the main skill and the report said "DPS: 97,539 -> 0 (-100%)". The sync now finds your main skill again by its gem and supports; if that skill is gone it picks your damage skill with the highest DPS (never an aura, herald or other utility skill) and says so. When the main skill did change, the report says "Main skill changed: X -> Y" and no longer shows a DPS change measured on an aura. A newly socketed aura (Anger, say) is now named on its own line: the game doesn't say whether it is switched on, so the AI asks you, and the line shows your unreserved mana both with it on and with it off.
  • The sync is honest about bandit and pantheon: pathofexile.com's public profile doesn't include them, so a sync can only keep what the synced build already has. The report used to say they were "set by PoB's importer". It now says which ones it kept. If the synced build has none but another build of the same character does (Soul of Lunaris + Shakari in your AI build, say), it names that build and gives the one-step change to copy them, so the AI asks you what you picked in game. Later syncs keep them.
  • A budget plan for more damage now looks at the damage slots first: plan_upgrades { budget: "30c", focus: "dps" } used to search helmet, body armour, gloves, boots and belt first and could run out of trade searches before it reached your weapon, quiver, rings or amulet. It now searches the slots in the order PoB says they can add the most damage to your build (the same order the per-item search has used since 0.9.2), and ends with a "NOT REACHED" line that names every slot it didn't get to and why (search limit, a pause asked for by the trade site, or more slots than one question can cover), with the exact slots to ask for next.
  • Weapon trade searches find weapons again: searching bows (or any weapon) for a stat such as "increased Attack Speed" or "Adds # to # Lightning Damage" found 0 listings, because on a weapon those rolls are the weapon's own ("Local") stats and the search asked for the global ones. trade_search now uses the weapon's own stat whenever the type is a weapon category ("bow"), a weapon base ("Imperial Bow") or the slot is Weapon 1/2: the same bow search under 30c now finds thousands of listings. "bows" works like "bow", and the result reminds you that "Adds # to #" filters compare the average of the two numbers (Adds 60 to 140 = 100).
  • Passive and respec suggestions no longer leave a skill without mana: the optimiser could rank "Respec Mana Mastery into Projectile Mastery" first (+2.8% DPS) when taking out the Mana Mastery left too little unreserved mana to cast Sniper's Mark, so the real result was a big DPS loss. 0.9.4 only checked new auras for this. Now every passive, mastery, ascendancy and respec suggestion is checked the same way: it is ranked by its real result with the cheapest fix in its steps ("+ switch off Clarity (frees 98 mana) - NEEDS THE FIX IN THE OPS"), or listed under "Would help but cannot be used now" when no fix leaves a gain. suggest { kind: "passives" } does the same check, and guide { next } marks a passive step, gem or item that breaks a skill ("BREAKS A SKILL: ...") and ranks it by its real result. An attribute shortfall is no longer shown as "A SKILL CAN'T BE USED (mana)".
  • Passive suggestions no longer skip nodes at random: suggest { kind: "passives" } and the optimiser try a few hundred passives per call, and the order they went through the tree changed from run to run, so on a big tree a good node (often an ascendancy notable such as Void Beacon) was sometimes never tried. They now go through the tree in a fixed order with the ascendancy nodes first, so the same build gives the same suggestions every time.

Already installed (0.9.0 or 0.9.3 or 0.9.4)? Click Update now on the Overview banner (or run tools\update.ps1): it downloads only the changed files, about 1.3 MB / 1.1 MB / 1.1 MB. Then restart PoB Agent Edition and your AI app.

New install:

  • PoB-Agent-Edition-0.9.5-win64.zip (252.6 MB): extract, double-click Install.cmd (needs Node.js 20+, which it offers to install).
  • PoB-Agent-Edition-0.9.5-win64-portable.zip (286.2 MB): unzip and play with Start PoB Agent Edition.cmd, no Node.js needed; Connect AI apps.cmd connects your AI app.

SHA256:

  • PoB-Agent-Edition-0.9.5-win64.zip: fae72f5480c4795607f7bec93bacd9b6e97bb7c28cb5d6fcbf39d5f9a7d2e040
  • PoB-Agent-Edition-0.9.5-win64-portable.zip: ee4160fccf26d7f04520689a072bf6ad8c8e4dcf33f5cbb71b0ba0bcf7c0f5d8
  • PoB-Agent-Edition-0.9.0-to-0.9.5-update.zip: 39644ad60076d265e6dae258ef4f248442d9b2924abb63d6c92da630ce28e84d
  • PoB-Agent-Edition-0.9.3-to-0.9.5-update.zip: 3d57bdbc7ae728536fc0dbd9726909a1ab4c2de221496a68713add004183d0ec
  • PoB-Agent-Edition-0.9.4-to-0.9.5-update.zip: 08a4e771ae009951d97b1158d7a7b9950f4454be7d442a0b2d802a6d5e6c0b41