Changelog

0.6.0 (2026-10-25)

The first release, on CurseForge. Everything built for the Forever beta so far ships in it:

• Talents. Paste a build code from foreverarmoury.app (FAT1-, FAT2- or FAT3-, the last with the Talented rank) and the build sits beside the talent window: a list of your builds and a strip of icons in the build's order, the points taken faded with a check, the next one lit with Now or its level, the rest with theirs. Hover lights the talent in the tree, click takes the next point, shift-click or Apply spends every point due, all or none, after one confirm. Swap says whether your other spec fits a build, and the trainer's reset says how many points Apply will spend after it. Export gives your class's builds back as codes.
• Leveling gear. The site's 54 leveling routes ship in the addon, so /fa gear works with nothing pasted: a panel beside the character window with the pieces to get at your level, each marked when you wear or carry it, then the ones coming, with where each drops. Hover for the tooltip, shift-click to link it. A FAG1- route pasted from the site wins for its class, spec and side.
• Legacy. Paste a FAL1- plan and it sits beside the Legacy window: the plan's perks in the order they're bought, a strip of their own, hover and click as the talents', and Apply across the three trees, one commit a tree, all or none in each.
• The windows. An FA button at the top right of the talent, character and Legacy windows puts the addon's panel away and brings it back; each part has a switch and a command (/fa, /fa gear, /fa legacy, /fa options); the strips fill the window's height and scroll, and the panels end where the windows do.
• Built on the Forever beta (client 1.60.1.70450). The talent reader works from the game's own node data, a build with a talent it can't place carries on and says which, and /fa debug lists every talent as the addon reads it.

What follows was written as each piece landed, before anything was released; all of it is in 0.6.0.

0.5.2 (never released; in 0.6.0)

The leveling gear routes the addon ships are the site's new ones (forever-armoury #1631):

• Forever's own loot is on the routes. Data/Routes.lua is written again from the site at b2b9d45: 54 routes, 2,610 pieces (2,554 before). They now weigh Forever's own dungeon and quest items, which the old routes' weapon lists left out, such as Durgen's Crescent Axe from the Hall of Thanes as the Alliance Protection warrior's and paladin's main hand at 13, and the loot of Ruins of Lordaeron, Excavation Site: Wetlands and City of Dalaran.
• The routes are 36 to 60 pieces. The shipped-table test now holds a route to the site's own rule, 1 to 80 pieces, rather than the old 37 to 59.

The gear panel ends where the character window does, and its list scrolls (forever-armoury #1606):

• The panel's bottom is the window's. The panel is anchored to the window's top right as before and now also by its bottom left to the window's bottom right, so the game keeps the two edges lined up at any scale. Before, it had a fixed height of 526 (12 rows) and hung about 50 units below the window in the beta. With no character window, or one that gives no height, the fixed height stays.
• The rows fit the height. The panel shows as many rows as fit between the top of the list and a 20 margin at the bottom, 32 a row (never fewer than one), worked out when it is laid out and again whenever its size changes (OnSizeChanged); rows are made as the height first needs them and the rest are hidden. The window's height is read guarded, as the live client has thrown on some frame reads.
• A route longer than the rows scrolls. The mouse wheel over the panel moves the list by one row, kept in range as the builds list does. The pieces to get now stay first and the order is unchanged. The first row shows a ⋮ when pieces lie above it, and the last ⋮ N more when N lie below, at the right of the row's second line (a source that is long is cut short before it). When a single row fits and pieces lie both ways, it shows the ones below. The tooltip follows the cursor to the piece the wheel brings under it.
• What only the beta can show: the panel's bottom edge on the window's at the beta's scale, the number of rows it holds there, and where the markers sit against a long source line.

A button on each window puts the addon's panel away and brings it back (forever-armoury #1604):

• A small square button, "FA", at the top right of the talent window, the character window and the Legacy window, left of the window's own close button (its CloseButton field, else the global it is known by, such as CharacterFrameCloseButton; at the window's top right when there is none). Its tooltip is "Forever Armoury — hide the level plan" (or "the leveling gear", "the Legacy plan"), or "show" when the panel is put away. A click puts the panel and its strip away together, and the next click brings them back. The button is lit gold while the panel is out. The choice is the account's and survives a reload (shown in the saved variables, one flag a part, out to start with).
• A part that is off still shows its button; a click turns the part on and shows the panel, so a new player finds the panel without a command.
• The commands and switches work as they did. /fa plan on, /fa gear on, /fa legacy on and the options page's switches also bring a panel back; /fa, /fa gear and /fa legacy bring back a panel that was put away (on the window if it is open, else with the window as it opens) instead of closing the window.
• What only the beta can show: where the button sits against each window's close button and art (the addon ships no icon, so it is text), and the close buttons' names on the three windows.

The strip's icons keep their places while it scrolls (forever-armoury #1601):

• Fixed slots. The strip is a column of slots of one pitch, an icon, the row under it for the Now or level label (kept whether or not the icon has one) and a gap of 4: 63 px at the 44 px icon size. Slot n is at the same distance from the strip's top at every scroll position, so the wheel moves the icons one slot and nothing else shifts. Before, the next icon's label, the gap after the points taken and the ⋮ took room only when in view, so the column reflowed as it scrolled and the last page sat higher.
• The gap is a line. What separated the points taken from the ones coming (8 px of extra height) is now a thin gold line, 1 px, drawn in the pitch above the first point coming, so it moves no icon.
• The dots and the arrows have places. The up arrow's place at the top and the down arrow's at the bottom are kept whether or not they show, and the ⋮ has a footer slot right under the last slot. How many slots fit is floor((height - 76) / pitch), the same with or without the arrows. A plan that fits shows whole and fills from the top; the last page of one that doesn't also fills from the top.
• Fewer, taller slots. Counting the label row in every slot, 850 px holds 12 slots at 44 px (it held 15 icons of 44 + 4); 15 at 34 px, 9 at 56 px. A build of 13 points now scrolls in the talent window at 44 px; the icon size setting gets more in. Both strips share this.
• What only the beta can show: how the line looks between the icons, the wheel moving the icons one slot with nothing else shifting, and whether 12 slots at 44 px is the right trade against the label row.

The Legacy panel works the way the talents' does (forever-armoury #1594):

• The strip and the panel hang under the Legacy window's side tabs, on its right edge, instead of past them: the tabs stay clickable and the addon's column lines up with the window. They are anchored to the trees tab itself, so the game keeps them lined up at any scale; 284 below the window's top when there is no such tab. The strip runs from under the tabs to the window's bottom, never past it.

• The gear panel's tooltip stays to the right of the panel, and the game's comparison with what's worn no longer covers the list: when the game puts ShoppingTooltip1/ShoppingTooltip2 to the left of the tooltip, over the panel (no room on the right), they go in a row instead, as the game lays them out when it has room (forever-armoury #1607): the first right of the tooltip, the second right of the first, 4 px between. Each one's "Equipped" header hangs above its top edge, so a row leaves it clear. It follows the game's own placement (TooltipComparisonManager:AnchorShoppingTooltips, run after it, so a rebuild when an item's data arrives is laid out too) and checks once more after the tooltip's Show(). A client that won't give the positions keeps the game's placement. What only the beta can show: that the manager exists under that name and ShoppingTooltip1:GetLeft() answers there, and when the game places the comparison relative to our Show().

• The row slides left as a whole only as far as the screen forces (forever-armoury #1607): when the tooltip's left plus the widths of the tooltip, the comparisons shown and the 4 px gaps passes the screen's right edge (UIParent:GetRight(), else GetScreenWidth()), the tooltip's point to the panel moves left by the overflow, top unchanged, so the last comparison ends at the edge and the comparisons follow. The offset is worked out on every hover, so leaving a piece puts the tooltip back; a row that fits leaves it where it hangs, and so does a client that gives no widths or screen edge. What only the beta can show: that the row reads whole beside the tooltip at the screen's edge.

• One strip for both windows. The strip of icons moved out of TalentUI.lua into Strip.lua (FA.Strip.New(owner)), which draws it, scrolls it (wheel and arrows), lights the hovered point's button in the tree and shows the tooltip, and asks its owner for the rest: the plan's points in order (plan(offset, count)), where it hangs (anchor()), the tree's button (button(entry)), the tooltip's lines (tooltip(entry, tip)), what a click can do (can(entry)), the click and the shift-click (spend(entry), spendAll()), and a key that changes when the character's points do (refreshKey()). The talent window's strip is the first owner and does what it did; the settings page's sliders for where the view starts and the icon size (FA.db.strip) are now for both strips. FA.LightButtons moved with it.

• The Legacy strip. While you follow a plan that can be bought, a strip hangs on the Legacy window's right edge past its side tabs, with the panel against it: the plan's ranks in the order Apply buys them (tree by tree, by row, a perk's prerequisite and the points its tree wants first), an icon for each rank with r/m. The ranks the account has are faded with a green check, the next has the gold border and glow, with Now under it when a Legacy point is available and the cap isn't spent, else wait; the ones coming wear their tree's short name, Prof, Adv or Res, where the talents' wear a level. The icon and name are the game's trait definition's, read through the tree's config (as the talents' are), falling back to the site's icon (Legacy.PERKS now has each perk's icon name, from public/data/legacy.js) and the perk's name. Legacy.Order(plan) is every rank of a plan from nothing in the buying order, from which the strip's taken ranks come; the ranks still to buy are Progress's steps, so the strip and Apply agree.

• Hover lights the perk's button in the window's tree, in the talents' blue beside the next perk's glow, when the icon's tree is the one on show (GetTalentButtonByNodeID on the tree panel; nothing otherwise), and shows the game's tooltip for the perk (SetSpellByID from its definition, else its name) with Rank r of m, and In the Adventure tree when that tree isn't on show.

• Click the next icon to buy that one rank and commit its tree, through the same path as Apply (FA.ApplyLegacy(plan, 1): PurchaseRank, CommitConfig on the tree's config, all or none for that tree, rolled back and said in chat if the game refuses or the commit fails, no confirm for one rank). The tooltip's last line says why a click does nothing: no Legacy point, the cap, in combat, changes waiting in the Legacy window, or that rank is being bought (Legacy.Applying()). Shift-click is Apply for everything due, through its confirm. A plan from another client build is shown in the list and has no strip.

• Switching trees. When the next rank is in a tree the window isn't showing, the click first switches the window to that tree as its tabs do, then buys: the Legacy UI's tabs send EventRegistry:TriggerEvent("Legacy.SelectTree", index) (the tree's place in LegacyTreeData), which the tree panel and the tab selection both follow; the addon sends that event (with Legacy.SelectPage and the trees page first when the panel isn't visible), else calls LegacyTreeTraitPanel:SelectTree(index). Where neither exists the tooltip says "Open the Adventure tab in the Legacy window to buy it." and the click does nothing.

• The plans list is a section, as the builds' is: a Plans (N) header opens and closes it (closed, it names the plan you follow), open until a plan is followed, and the choice is kept for the account (legacyPlansOpen, since plans are the account's). The perks list stays under it, and Apply stays.

• What only the beta can show: the strip's place and height beside the 920-wide window, the game's names and icons for the perks, that Legacy.SelectTree sent from the addon switches the tree and its tab, that the tree's buttons exist right after the switch, a purchase and commit on a tree the window isn't showing, and the blue hover on the Legacy tree's square buttons.

0.5.1 (never released; in 0.6.0)

The talent strip fills the window's height and scrolls (forever-armoury #1593):

• Bigger icons that use the strip's height. The strip is as tall as the talent window (about 850 px on the live client) but showed 3 taken, the next and 5 coming as 34 px icons. Now the icons are 44 px to start, a setting from 34 to 56 (strip.size, a slider on the settings page beside the other two), the strip is 14 px wider than they are, and the glow, the check, the gold border, the level badge and the text on the icons (the r/m, the badge's level, Now or the level under the next one) scale with the size. The strip shows as many points as its height holds: floor((height - padding) / (size + gap)), read from the strip itself once it is anchored (850 px when the game hasn't laid it out yet, and drawn again when it does), so a build that fits is shown whole, taken points faded, in its order.
• A build that doesn't fit scrolls. The mouse wheel over the strip moves it one icon a notch, and a small up and a down arrow at its ends (shown only then) move it a page less one. The ⋮ under the last icon still says how many points follow. FA.StripPlan(progress, offset, count) now answers the points from an offset, how many are above and below, where the next sits and how many the build has.
• The view starts at the next talent. The two counts on the settings page now say where it starts, not how many to show: the taken points above the next (3 to start) and the coming points kept in view below it (5), when the strip has room for both. When your points change (a point spent by the strip, Apply or the window, or TRAIT_CONFIG_UPDATED), or you follow another build, the view moves to the next again, unless you have scrolled it: then it stays where you left it until your points change. Moving either count, or the size, puts the view back at the next.
• The hover (#1563) and the click (#1564) work on every icon at every offset: the icons are drawn again, and the icon under the mouse keeps its light and tooltip, as the view moves.
• What only the beta can show: the strip's real height and how many 44 px icons fit beside PlayerSpellsFrame, the wheel on the live client, and how the scaled glow looks at 56 px.

The leveling gear routes are built in (forever-armoury #1591):

• /fa gear works with nothing pasted. The addon ships all 54 of the site's leveling routes (nine classes, three specs, both sides) in Data/Routes.lua, so a fresh install shows the route for the character's class, side and spec. The panel says "Route shipped with the addon."
• A pasted FAG1- route still wins for its class, spec and side, and the panel says "Route from the site." Copy for addon on the site is now for a route the site has changed since the release; forgetting a pasted route brings the shipped one back.
• tools/routes.py writes Data/Routes.lua from the site's public/content/route/<class>.json (python3 -I tools/routes.py, standard library only); its header names the site commit and the date. A route that isn't one of the three specs on both sides, or a slot or source it has no number for, stops it without writing. scripts/release.sh expects Data/*.lua in the zip and nothing from tools/.

Hovering a gear piece shows its tooltip (forever-armoury #1592):

• Hover a row and the game's tooltip for the item shows to the right of the panel (SetItemByID; the item's link when that call is missing or fails, then its name), with where it comes from in full ("Deadmines: Edwin VanCleef", or the quest) and the level the route has it at, so a source cut off with "…" reads whole. Leaving hides it, and so does the row hiding.
• Shift-click a row links the item in chat (the game's HandleModifiedItemClick, else ChatEdit_InsertLink); an item the game hasn't loaded yet has no link to give.
• A redraw leaves the row under the mouse alone, so the tooltip doesn't drop when the game finishes loading an item's name; the status text has room for a fourth line (the route's origin) and the rows sit a little lower.

Read every talent node, and keep going when a pick doesn't place (forever-armoury #1590):

• A node's tree is whichever of its groupIDs is one of the trees' groups. The first beta try (client 1.60.1.70450) showed why the addon read 3 of Arms's talents, 1 of Fury's and 2 of Protection's: each node has 3 to 7 groupIDs, and the talent tree's group is not always the first, which was the only one the addon looked at. A node whose groups name two trees takes the first, and /fa debug nodes says so. A node whose groups don't name a tree goes to the tree its posX falls in or is nearest to, by the x range of the nodes that do have a group (the trees sit thousands apart, the columns 600); a tree is four columns wide at most, so when one tree has no node with a group, the nodes no other tree's range can take go to it by the widest gaps in x; with no group on any node, the x values are split into one run per tree the same way.
• No node is dropped for its rank count. maxRanks when above 0, else totalMaxRanks, else its first entry's maxRanks; a node none of them counts is kept with its rank count unknown, drawn as ? (Rank 1 of ?, 1/?). A node is left unread only when isVisible is false, as the talent window skips it too, or it has no position, and /fa debug lists it with why.
• /fa debug nodes prints every node of the active config as the game gives it, a line each: id, posX, posY, maxRanks, totalMaxRanks, how many groupIDs (listed, a tree's group marked with its name) and entryIDs, isVisible, type, subTreeID, and the tree the addon gave it and why. /fa debug is as it was, and says how many of a tree's nodes went by position.
• A pick that doesn't place is marked, not fatal. A build with a pick no talent of your trees sits under (the site newer than the addon, or a node that did not sort) used to stop at "A talent in this build isn't in your talent trees" with no next talent, no strip and Apply off. Now FA.Progress places what it can and lists the rest (unplaced, each with its tree and cell). The panel says "N talents of this build aren't in your trees" with their cells (three named, then "and N more") and carries on: the next placeable talent is lit; the strip shows each such pick, in its place in the order, as a greyed question-mark icon whose tooltip names the cell; Apply spends the placeable points in order and stops at the first unplaceable one, saying so in its button tooltip, in the confirm and in chat. Chat says the same when the build is imported, once per build.

0.5.0 (never released; in 0.6.0)

Legacy plans (forever-armoury #1567, from #1566):

• FAL1- codes: the site's Legacy tab writes a Legacy plan as FAL1-<build>-<name>-<ranks> (FAL1-70425-Gatherer%27s%20Path-150000000051000000030001000): the client build the perks' order is from, the plan's name as a build's, and 27 base-36 digits, one rank a perk, tree by tree. The import box reads them beside build and gear codes (one paste can hold all three), says what came of each, and Export gives the account's Legacy plans back as FAL1- codes, one line a build.
• Legacy plans are the account's, as Legacy is: kept once for every character, one followed for the account, checked at load like builds (one whose ranks don't read is dropped, a missing name, build or id repaired, with a line in chat saying so).
• A panel beside the Legacy window (LegacySystemFrame, loaded on demand): the account's plans (click to follow, x to forget, arrows and wheel to scroll), the followed plan's perks with the ranks you have and the plan wants, the Legacy points available against the seasonal cap, and the next perk, named and lit in the window's tree with the same glow the talents have (the window shows one tree at a time, so the next perk of the tree on show lights).
• Apply buys the plan across the three trees: one confirm naming the perks, then, tree by tree, C_Traits.PurchaseRank for each rank in an order the game takes (by row, a perk's prerequisite full and its tree's points spent first) and C_Traits.CommitConfig for the tree. It's all or none in each tree: a refused purchase or a failed commit, at once or later (CONFIG_COMMIT_FAILED), rolls that tree back and leaves the others. It stops at the points you have and the seasonal cap, never refunds, and won't start in combat or while the Legacy window has changes of its own waiting. The button says how many ranks it would buy, or why it can't.
• A plan from another client build is shown, never bought: the addon's table of the 27 perks is of build 1.60.1.70425, so a code from another build, whose places in the ranks may mean other perks, is marked in the list and the panel says so.
• /fa legacy opens the Legacy window on its trees with the panel beside it, /fa legacy on|off and a switch on the settings page turn the part on and off.
• Behind it: LegacyCode.lua, Legacy.lua and LegacyUI.lua; BuildCode.lua shares its name helpers, Talents.lua its guard for trait functions the client may lack (FA.Talents.Game), and TalentUI.lua its glow (FA.LightButtons).

Click to take a talent (forever-armoury #1564):

• Click the next icon in the strip and it takes that point: one rank, staged and committed together, as Apply does for a plan of one point (C_Traits.PurchaseRank, then C_ClassTalents.CommitConfig). It's all or none: a refused purchase or a failed commit, at once or later, rolls back and chat says why, in Apply's words. There is no confirm for one point; the tooltip already names it. Chat says what was taken (Spent as Arms says: Deflection.).
• Shift-click the next icon is Apply for every point due, through the same confirm.
• Only the next icon, and only when Apply could spend: a point to spend, out of combat, none of the window's own changes waiting, the build not off its order. Otherwise the click does nothing and the tooltip's last line says why, with Apply's reasons. When it would work the icon highlights under the mouse and the tooltip ends with Click to take it (and Shift-click to take all N when more than one is due).
• While the commit casts, a second click does nothing, and the tooltip says the point is being applied; the strip moves on when the game answers.
• Behind it: FA.Apply and FA.PlanApply take an optional number of points, and FA.Talents.Applying() says whether the addon's commit is casting.

The Talented rank in the build code (forever-armoury #1540):

• FAT3- codes: each build ends with its rank of the Legacy perk Talented, one digit 0 to 5 (FAT3-70170-warrior-Arms%20PvP-0a0a0a0b0b0b1c1c-3), as the site now writes them. FAT1- and FAT2- codes still read, with rank 0. A rank that isn't 0 to 5 is refused with a sentence, as the site does.
• Import keeps the rank with the saved build, and Export writes a FAT3- code with each build's rank. A build from a FAT1- or FAT2- code exports with rank 0 (a FAT1- build's game build is written as 0, which the site reads as the first trees).
• The first point's level is 10 minus the rank the game says, as before; when the game won't say (the Legacy config can't be read) the build's own rank is used, and 10 when neither is known. /fa debug says which rank is in use and where it came from.

The talent column (forever-armoury #1562, #1563):

• A strip of icons beside the talent window: the build you follow, talent by talent in its order, one icon for each rank (a talent with ranks shows r/m on it). The last points you took are faded with a green check, the next one has a gold border and the game's glow with Now under it when you can spend it (else the level it comes at), and the ones coming have the level they're due at in a corner. A ⋮ under them says more follow. The icon and name come from the game; an icon the game hasn't given yet is a question mark. It shows with the panel and only while you follow a build, redraws as you spend points, change build or swap spec, and the panel sits against it. A build that's off its order shows the points it can place and nothing wrong.
• How many it shows is two sliders on the settings page: the taken points (3 by default, up to 5) and the coming ones (5, up to 8).
• Hover an icon and that talent lights in the tree, in blue, beside the next talent's glow, which stays; leaving puts it out. The tooltip is the talent's own spell, then its level and rank, and "Taken" for a rank you have. The highlight is a frame of the addon's, never something written on the game's pooled button.
• The panel's build list is a section: a Builds (N) header with a plus or minus opens and closes it, and closed it says which build you follow. It's open until you follow a build and closed after, and what you choose is kept for the character. The panel is as tall as what it shows, with Import and Export at the bottom.

0.4.0 (never released; in 0.6.0)

Small fixes after the first release (forever-armoury #1539):

• Builds with one name keep each their points: an import updates a build only when its name and points both match one kept, so two Arms builds, or two unnamed ones, are two builds, not one overwriting the other.
• The build list scrolls: an arrow pair under it and the mouse wheel over the panel move it, so an 11th build, and a 100th, can be picked.
• A name is drawn as typed: a | in a build's name is doubled where the addon draws it (the list, chat, the confirms), so a |c colour escape in a name doesn't take effect; a build with no name shows as Unnamed in the confirm and in chat, as in the list.
• The class is read at load, not at PLAYER_LOGIN, so an import before the login event no longer errors.
• Refreshes are one a frame: the panel redraws once however many talent events come, and the addon listens for ACTIVE_COMBAT_CONFIG_CHANGED, PLAYER_REGEN_ENABLED and PLAYER_REGEN_DISABLED, so the Apply button turns off in combat and on again after it. An event name the game doesn't have is said in chat; registering it used to fail without a word.
• The trainer's reset message is said when the reset is accepted, not when the dialog comes up (a cancelled dialog says nothing), and counts the points Apply would spend, from the game's own count, not from the level.
• The reader keeps to the site's (build-code.js): a name is cut to 40 characters with the site's note (and on export, as the site's writer does), a name that isn't UTF-8 is refused, a version is 1 to 3 digits and a game build 1 to 8, Unicode spaces collapse as ASCII ones do, and a long run of dots no longer takes quadratic time (forever-armoury #926). The code's format and version are as they were.
• A trait function the client lacks is said in chat once, by name, and the addon carries on without it, instead of a Lua error.
• Saved builds are checked at load: one that isn't a table or has no picks is dropped, and a missing name or id is repaired, with a line in chat saying so.

The leveling gear part (forever-armoury #280, docs/gear-route.md):

• Gear routes from the site: the Leveling plate's route for a class, spec and side, as a FAG1- code pasted into the import box (one paste can hold a build code and a gear code). Routes are kept for the account by class, one per spec and side.
• The panel beside the character window: the pieces of the route to get at your level, each marked when you wear or carry it, then the ones coming, each as the game's item link with where it comes from (the dungeon and boss, or the quest). The route's spec is the heaviest tree of the build you follow, or one picked with the panel's button.
• /fa gear opens the character window with the panel, /fa gear on|off is the part's switch, and the settings page has it too.

0.3.0 (never released; in 0.6.0)

Fixes before the first release (forever-armoury #1535):

• Apply no longer refuses before anything is staged: the game's CanChangeTalents is only true once changes are, so it's asked after the first point, and a no rolls back.
• A commit the game fails after it starts (its cast) is rolled back, and chat says so.
• Import keeps each build's game build, so Export gives a build back as it came: a FAT2-<build>- code for each game build, one per line, and FAT1- for a build from a FAT1- code.
• The talent sort takes each tree's grid from its own nodes, and says in chat when a talent doesn't sort into a cell (past the fourth column or the seventh row, or on a cell another has). /fa debug prints each node's position, each tree's spacing and first column, and what was left out and why.
• The active config falls back to the active spec group's when GetActiveConfigID has no answer, as the talent window does.
• Build names encode the same under every locale: the encoder spelt letters and digits with %w, which takes bytes above 127 for letters under a UTF-8 locale.
• Talented: the first point's level is 10 minus the perk's rank, read from the game, for the next talent's level, what Apply can spend and the trainer reset's count.
• LICENSE (MIT), .pkgmeta for the CurseForge packager, and the version from the git tag.
• scripts/release.sh builds and checks the release zip from a tag, and uploads it to CurseForge on a flag (forever-armoury #1537).

0.2.0 (never released; in 0.6.0)

• Apply: spends your unspent points as the build you follow says, in order, after one confirm; all or none.
• Swap: following a build your points don't fit names the points it lacks, and says whether your other spec fits it or a trainer reset is needed. At the trainer's reset, the addon says how many points Apply will spend afterwards.
• /fa apply and /fa debug.
• Build codes carry the game build the talents are from (FAT2-70170-…, forever-armoury #1215), so the site opens a code on the right trees; FAT1- codes still read.

0.1.0 (never released; in 0.6.0)

• First version: import build codes from the site, a build list beside the talent window, the next talent of the build you follow lit in the trees, export back to the site, and the level plan part's switch.