Polestar 0.2.1

Polestar 0.2.1: a redesigned welcome, quests that tick the right objective, an in-game bug report with our Discord, and guide packs explained plainly. Polestar is now open source on GitHub.

Install or update

With the CurseForge app: search for Polestar Guides (https://www.curseforge.com/wow/addons/polestar-guides). By hand:

1. Download Polestar-0.2.1.zip below (not "Source code").
2. Delete the old Polestar folders from World of Warcraft/_classic_beta_/Interface/AddOns/ (_forever_ from launch), then unzip this one there. You should see Polestar, Polestar_Guides, Polestar_QuestDB and Polestar_ItemDB.
3. Quit the game completely and start it again; a /reload does not load new addon folders.

Polestar_Recorder-0.2.1.zip is optional. SHA256SUMS holds the checksums. Questions and bug reports: the Polestar Discord, https://discord.gg/vMbee6F2e9, or GitHub Issues.

For players

• Quests with several objectives check off the right one: a goal counted the objective at its place in the quest's text instead of its place in the quest log, so in The Guns of Northwatch "Kill Cannoneer Smythe" showed the 10/10 medals and Captain Fairmount never ticked. 135 goals in 46 quests of the leveling guides now count the objective they name.
• A new character's welcome survives the intro cinematic: the cinematic closed it as it started and it never came back. It now waits for the cinematic to end, or comes back on the page it was on.
• The welcome is redesigned: three pages under a starlit hero (two for a later character), with step dots. It shows the guide window, the arrow and every guide at a glance; setup shows each choice's description and the colour schemes as cards that apply as you click; the last page shows your first guide on its zone painting, the beta note, the Discord invite as a link that opens it ready to copy, and what guide packs are.
• The guide menu lists only the guides your character can follow on your own faction: an Undead no longer sees the Orc and Troll Durotar and Barrens guides there. The other faction's button and All still list every guide.
• Guide packs page: the problem report box grows to fit long problem messages.
• Options > Guide packs says plainly what a guide pack is: someone else's guides in a separate addon, supported by its author. Its link opens docs/GUIDE_PACKS.md, a new page on packs for players and for authors.
• Search ranks an item first as covered by a guide only when a guide Lookup would open for it collects it: one of Polestar's own, or one from the pack chosen under Suggest guides from.
• Polestar is open source: the code, the guides and the tools that build them are on GitHub under the GPL-3.0.
• Report a problem from the game: the bug in the guide window, beside Skip, opens a report on the step on screen. Say what went wrong and Polestar writes the rest (the step and each goal's state and position, where you stand, your race, class and level, the versions and any errors it caught), sized to fit one Discord message, for you to copy and paste on the Polestar Discord (the game can't open links: "Get the invite" gives the invite once if you haven't joined yet). The guide window's menu and /polestar report open it too.
• The Polestar Discord is one click away: Discord's mark at the foot of the hub's and the settings' sidebars, and /polestar discord, give its invite to copy.

For guide authors

• A pack reads as a pack in the game's AddOns list: its TOC title is "Polestar Pack: <title>", it sits under Polestar's entry next to Polestar's own addons, and without notes in pack.json its line is "Guide pack for Polestar by ". Polestar's menus show the title as written.
• docs/GUIDE_PACKS.md: what a pack is, the steps from new to publishing, what the tools require and what we ask of authors.
• playtest plays a step for a class none of the guide's races can be, and a guide with a class header, as the first race on the guide's side that can be that class: an only Druid step in a Horde guide is played as a Tauren.
• play and dev --play stop the Lua session and exit when it cannot start, instead of waiting on it; the page redraws on its own after a rebuild.
• new keeps the port of an http origin (http://host:3000/...) in the pack's workflow and dev container.
• lint reports a | in a second or later pro or con at that entry's own line, once for each entry that has one.
• compile no longer reads data/forever/dungeons.json: a quest only DungeonJournal knows gives its title and lvl in the guide, so nothing from DungeonJournal reaches a guide pack.
• find and lint number a quest's objectives as the game lists them in the quest log: creatures, objects, items, kill credits, then exploration, with QuestieDB's exceptions. quest Q.O in a guide written before 0.2.1 may point at another objective: check each against find <quest>.

For contributors

• THIRD_PARTY.md, docs/RELEASING.md and the README say what a release holds from each data source: QuestieDB facts in the guides and the quest markers, credited; never the Codex or the zone crossings pack.
• Two more independent route searches (the fourth on the data 0.2.0 ships with) back the README's numbers and docs/SIMULATION.md; the charts compare the guides with those of 0.1.0.
• The README charts display again: an SVG's generated header no longer holds --, which XML comments forbid, and a test checks every committed SVG for it.
• docs/curseforge holds the CurseForge listing: the description to paste, the summary, the project settings and what to upload where. readme brand draws the project avatar and, with rsvg-convert installed, writes the listing's PNGs (avatar, banner, route charts) beside it.
• preview draws a multi-line edit box's text wrapped from the top, and the report window and the Discord invite are scenes of their own, held to the text-fit audit. THIRD_PARTY.md credits Discord's mark, the one piece of art Polestar ships that it did not draw.