promotional bannermobile promotional banner

LegacyNext

Which Legacy challenge is closest to done, and which of your characters should finish it.
Back to Files

v0.1.0-beta2-forever

File nameLegacyNext-v0.1.0-beta2-forever.zip
Uploader
lxhwslxhws
Uploaded
Oct 2, 2026
Downloads
17
Size
74.0 KB
Flavors
Forever
File ID
9042268
Type
B
Beta
Supported game versions
  • 1.60.1

What's new

Changelog

All notable changes to LegacyNext are recorded here. The format follows Keep a Changelog, and the version numbers follow Semantic Versioning as described under Versioning below.

LegacyNext targets the World of Warcraft: Forever beta, interface 16001. Each release names the client build it was verified against.

Unreleased

0.1.0-beta2 - 2026-10-02

Built against client build 1.60.1 (70170). Nothing new in this release has been seen in game yet, and each entry says so.

Added

  • The window can be resized from its bottom-right corner, and keeps its size for each character. Not yet seen in game.
  • Click a challenge row to open Blizzard's Legacy panel on that challenge, or shift-click it to link the challenge in chat. Not yet seen in game.
  • A minimap button. Left-click opens the window, right-click opens the settings, and dragging moves it round the minimap's edge. Its tooltip shows the reward track, this character's unspent points and the three challenges closest to done. /lgn minimap shows or hides it. Hovering LegacyNext in the minimap's addon dropdown shows the same tooltip. Not yet seen in game.
  • A settings page under Options > AddOns > LegacyNext, with toggles to show and to lock the minimap button. /lgn config opens it. Not yet seen in game.

Changed

  • The roster keys each character by its GUID, so a name change between builds no longer splits one character into two rows. A character saved under Name-Realm moves to its GUID the next time it logs in. /lgn roster forget takes a Name-Realm or a stored key. Not yet run in game.

0.1.0-beta1 - 2026-10-02

Verified against client build 1.60.1 (70170).

Added

  • The window remembers its tab, category filter and position for each character.
  • Blizzard's top tabs for Next Up and Roster, so the selected one stands out.
  • Achievement icons on Next Up and tradeskill rows, and the next reward's icon in the header.
  • Roster names in class colours, with the current character tinted.
  • Tagged releases: a pushed v* tag is linted, tested and packaged into a GitHub release, and the tag becomes ## Version. A copy straight from the repo reports its version as dev.
  • Roster tab (v1): the window has a second tab listing every saved character with Legacy points spent per tree and points unspent, then each tradeskill challenge a saved character has the profession for, closest character first. Next Up's tooltip on a tradeskill row names the saved characters with that profession. /lgn uidump roster prints the tab as text.
  • Roster groundwork (v1): each character's class, level, professions and Legacy tree spend is saved at login and after a level-up, skill or talent change. The game does not return professions or tree spend at logout, so a logout snapshot keeps the stored ones. /lgn roster lists every saved character and, for each tradeskill challenge, which of them is closest. /lgn roster forget <Name-Realm> removes a deleted character.
  • /lgn and /legacynext open the Next Up window: incomplete Legacy challenges ranked by closeness to completion. Each row shows the name, category, points awarded and criteria remaining. /lgn help lists the commands.
  • Category filter over the game's own Legacy categories.
  • Reward track header: current Legacy points, points to the next reward, and that reward's name.
  • Challenge ranking (Model/) in three tiers, each under its own divider: in progress (sorted by closeness), not started (the game's category order), and no progress shown. Closeness reads criterion quantities whenever need > 1, so a 0/42000 reputation criterion is not scored as one step from done. Zero-point challenges are excluded. Challenges with no measurable criteria sit in the last tier rather than at 0%.
  • Other classes' challenges are hidden for the current character, with a line saying how many. They are matched by structure against the character's class name, and nothing is hidden if that fails to match.
  • Reward-track summary (Model/): current level, next threshold and reward name from the sparse renown level list.
  • Guarded client read layer (Api/). Every call is feature-detected, pcalled and checked with issecretvalue, and returns plain tables or nil plus a reason. Covers challenges, the reward track, tree spend and character state. A struct with one uncopyable field is kept and the field named, rather than dropped whole.
  • /lgn probe: one line per client API reporting ok, nil, missing, error, secret or skipped.
  • /lgn dump [section] [page]: a copyable Lua literal of everything Api/ returns, shown in a window you can select from. Sections: all, summary, challenges, categories, rewards, trees, character, probe.
  • /lgn uidump [category]: the window's contents as text, for checking what would render without a screenshot.
  • Addon icon in the AddOns list (Media/icon.tga, original art; see docs/icon-design.md).
  • Escape closes the window. It refreshes on open, on ACHIEVEMENT_EARNED within a second and on CRITERIA_UPDATE at most every five seconds while open, and defers any rebuild, including the first on open, until combat ends. A read that throws shows as the window's error state instead of a Lua error.
  • A key binding to open and close the window, under Key Bindings > AddOns.
  • LegacyNext sits under Achievements in the AddOns list.

Versioning

SemVer 0.x.y while Forever is in beta; 1.0.0 is the release that targets Forever's launch build on 2026-11-04. The client build is not encoded in the version string. One addon version is expected to outlive several beta builds, so each release entry names the build it was verified against instead. LegacyNext.toc carries ## Version: v0.1.0-beta2, which the packager replaces with the git tag at build time, so the tag is the version. Beta builds are tagged -betaN and upload to CurseForge as beta releases. The first upload was v0.1.0-beta1.

This mod has no additional files