v0.4.8

Bagwise

v0.4.8 (2026-11-08)

Full Changelog Previous Releases

• Release 0.4.8: fix scan crash on quest-starting items
  C_QuestLog.GetQuestInfo does not exist on every client, and the scanner
  called it for any item that starts a quest. The error aborted the whole
  bag scan, so no item after it got a dot. Look the quest title up through
  whichever function exists, and skip the name when none does.
  Also scan each slot in its own protected call, so one item that raises
  an error can no longer remove every other dot, and show the last such
  error in /bagwise report.
  Bump version to 0.4.8.

v0.4.7

Bagwise

v0.4.7 (2026-11-08)

Full Changelog Previous Releases

• Release 0.4.7: remove the weaker duplicate gear hint
  Item level alone does not say which of two pieces is better, and
  comparing stats is too class-dependent to do safely. A yellow that is
  often wrong teaches players to ignore it, so the rule is removed.
  Bump version to 0.4.7.

v0.4.6

Bagwise

v0.4.6 (2026-11-08)

Full Changelog Previous Releases

• Release 0.4.6: yellow hints for openables, outleveled consumables, weaker gear
  Openables (clams, bags of loot) get a yellow: they take a slot now and
  their contents often stack. Never green.
  Food, drink, potions and bandages whose level requirement is 20 or
  more levels below the player's get a yellow. Elixirs, flasks, quest
  items and items without a level requirement stay silent.
  Bound gear that another piece in the bags outclasses (same slot and
  armour or weapon type, at least 5 item levels ahead, wearable now) gets
  a yellow. Slots filled twice need two better pieces. Unbound and kept
  items are skipped.
  Bump version to 0.4.6.

v0.4.5

Bagwise

v0.4.5 (2026-11-08)

Full Changelog Previous Releases

• Release 0.4.5: read secondary professions from the Skills tab too
  Professions were read from GetProfessions() alone when it returned
  anything. That API leaves out First Aid and clients differ on where
  fishing and cooking sit, so a secondary profession could look missing.
  Its recipes then read as "You don't have this profession" and never
  got the "Bank it" check.
  Take every index GetProfessions() returns and always read the Skills
  tab too, so the two fill each other's gaps. Skill ranks come from
  whichever has them.
  Add a professions line to /bagwise report showing what was read and
  from where, so a wrong reading is visible.
  Bump version to 0.4.5.

v0.4.4

Bagwise

v0.4.4 (2026-11-08)

Full Changelog Previous Releases

• Release 0.4.4: bank-it hints, yellow grays, dot ring, loot dot fix
  Add yellow hints for recipes and reagents you cannot use yet:
  • recipe for a profession you do not have (may sell on AH)
  • recipe far above your skill, and reagents your professions will
    not use for a long while: "Bank it"
    The skill a recipe needs is read from its tooltip.
    Gray handling: raise the green threshold slightly, and show a yellow
    "but worth ..." warning on the cheapest gray when it sells for real
    money.
    Dots: add a thin near-black ring and a soft bevel. The tooltip uses
    separate shadowless, centred pearl textures.
    Colours: info blue now matches the item tooltip blue.
    Fix the loot window dot staying after the item is taken.
    Bump version to 0.4.4.

v0.4.3

Bagwise

v0.4.3 (2026-11-08)

Full Changelog Previous Releases

• Run CI tests in a venv so lupa is importable
• Add /bagwise report, group help, rewrite README
• Add icon in-game
• Add CI release workflow and CurseForge project ID
  • Package and upload to CurseForge on tag push with BigWigsMods/packager
  • Run the test suite before packaging so a failing test stops the release
  • Add X-Curse-Project-ID to the TOC

v0.4.2

Bagwise

v0.4.2 (2026-11-08)

Full Changelog Previous Releases

• safety layer, openables, dual-use items
• Make room for loot: mark junk to delete when bags are full
  When the loot window has more items than free slots, rank loot against
  the cheapest junk by vendor price times stack size. Dots to delete pulse;
  every other dot goes quiet. Loot worth less than your junk gets a green
  dot in the loot window.
  • Never suggests consumables, containers, gems, reagents, trade goods,
    recipes, quest items, keys, the hearthstone, profession tools, or
    anything unsellable or marked keep
  • White gear only when already marked safe
    Co-Authored-By: Claude
• Pearl dots, vendor wording for unwearable white gear
  Dots
  • Replace the tinted gray disc with baked-color pearl spheres
    (dot_green, dot_yellow): highlight, sheen and a solid offset drop
    shadow like the item count digits, fully inside the frame (no clipping)
  • Generated by tools/make_dot_textures.py; remove textures/dot.tga
  • 13px frame, anchored 1px from the slot corner; tooltip header uses
    the same textures
    White armor
  • Armor the class can't wear (level-aware, e.g. shamans mail until 40)
    and armor worse than equipped gear is tagged "vendor" when it has a
    sell price; the tooltip says "Safe to vendor" instead of
    "Safe to delete"
  • Items with no vendor price still say "Safe to delete"
    Co-Authored-By: Claude
• Mark white armor you have already out-geared
  A common-quality piece of armor now gets a green dot when every slot it
  could go in holds a green-or-better item with an equal or higher item
  level. Empty slots, unloaded items and weapons stay silent. Rings and
  trinkets must lose to both of their slots. Equipment changes now
  rescan the bags, and /bagwise dump shows the gear each white was
  compared against.
• Scan the reagent bag, add loot window tooltips and /bagwise why
  Bag scanning, dots and tooltips stopped at bag 4, so items in Forever's
  reagent bag (bag 5) got nothing. A small Bags module now decides the
  last scanned bag from the client's bag slot constants, and every part
  uses it.
  Loot window rows now show the same verdict, profession and quest info
  as bags, with "Not needed" in place of "Safe to delete" for green.
  /bagwise why [item] prints the class, faction, quests (with done state
  and faction), recipe professions and verdict for one item.
• Count only quests the player's faction can take
  Alliance and Horde versions of a quest have separate IDs, so an item
  used by both waited on a quest the player could never complete and
  never got a quest-completed verdict. The quest generator now records
  each quest's faction from its race mask (Forever's extra race bits
  included), and the scanner drops the other faction's quests before
  judging completion. Quests with no faction data are kept, so missing
  data keeps an item silent instead of marking it safe. /bagwise dump
  tags quests with their faction.
• add /bagwise dump, richer /bagwise status, single version source
• restyle tooltip verdicts as a dot header
• label verdict lines with the suggested action
• stop giving consumables a verdict
• fix reagent tooltips missing on some bag slots
• add keep and flag overrides, fix tooltip errors
• add support for WoW forever client
• update readme with license
• add compatability for baganator
• add quest info and quest completed verdict
• add reagent and quest-item data generators, flag unused Trade Goods
  Two new Python tools (pure stdlib, no dependencies):
  • tools/build_reagent_professions.py: generates data/reagent_professions.lua
    from wago.tools DB2 data (501 reagent items across 9 professions)
  • tools/build_quest_items.py: generates data/quest_items.lua from Questie's
    classicQuestDB.lua (2783 items across 2933 quests)
    New verdict rule: Trade Goods items not used in any recipe, quest,
    or class/vendor reagent table get a green dot ("No recipe uses this").
    Also fixes Commands.Init crash on login (stub had no Init function).
    Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
• remove reagent info on non-bag tooltips
• improve code quality and remove shift feature
• add reagent profession tooltips and crafting verdicts
  Reagent items now show which professions use them, with skill
  ranges on shift-expand.
• improve visual appearance of dot
• add class reagent verdicts
• Add vendor reagent verdicts (Epic 5)
• add itemLevel fallback for gear with reqLevel=0
• remove isUsable tests, add reqLevel test
• disable isUsable rule, remove IsUsableItem from scanner
• update verdict tests for merged isUsable rule
  stories 1.1 (class restrictions) and 1.2 (race restrictions) now
  use a single IsUsableItem check instead of separate fields.
  Tests use isUsable = false/true/nil to match the new item shape
• wire up events and bag frame hooks in entry point
• add dot overlay for bag slot frames
• add bag scanner with verdict caching
• add verdict rules for story 1.3
• add verdict rules for stories 1.2
• scaffold skeleton with verdict rules for stories 1.1
• initial commit