Skip to content

0.3.0

Choose a tag to compare

@github-actions github-actions released this 10 Oct 18:43
· 5 commits to main since this release
0.3.0
00053c3

GearFall

0.3.0 (2026-10-10)

Full Changelog Previous Releases

  • Version 0.3.0
  • New gearing rule: never make respec suggestions
    A sibling-only item (the alt's own spec rejects it, another spec of the
    class would use it) can now be a final "no" instead of a respec hold.
    One gate in SpecUsesItem's known-spec branch, before the sibling probe:
    no respec verdicts, no respec holds, no respec tags anywhere downstream;
    the rejection reason stays the honest main-spec one. Per-alt override
    wins over the account-wide default; the spec-less class question is
    deliberately untouched.
    Co-authored-by: BlueAI Platform/opencode/GLM-5.3-Flash orosei-sylvanas@murlo.cz
  • Unique-Equipped items: plan at most one copy per alt
    Two identical Unique-Equipped trinkets were both drafted to the same
    alt (one into each trinket slot) even though the alt can only ever
    wear one. GetItemLinkInfo now captures a uniqueEquipped flag from
    C_Item.GetItemUniquenessByID - calibrated on 120100: the plain tooltip
    line reads back isUnique=true with nil category fields, so the flag
    accepts the category-less shape (and, defensively, the -1 pseudo-
    category); a named limit category flags only when its cap is 1.
    A copy of a unique the alt already wears still pins to the worn slot
    (higher ilvl = upgrade of that slot), and a duplicate of a copy already
    inbound - real send ledger or draft projection - pins the same way and
    scores delta 0, falling to the next alt or Left over. The hold budget
    follows suit: one unique copy per item per alt. /gear debug stats now
    prints the raw uniqueness API values beside the flag, and the scan
    report marks flagged items UNIQUE-EQUIPPED.
    Co-authored-by: BlueAI Platform/opencode/GLM-5.3-Flash orosei-sylvanas@murlo.cz
  • Add /gear flush and a Distribution alert for stale incoming-gear promises
    A mailed upgrade that got returned or expired used to leave a promise
    that never cleared: the slot stayed phantom-blocked and the window kept
    "Arrived - equip it" state for gear that would never arrive. /gear flush
    [alt|all] (with confirm) drops the stale ledger, and the Distribution
    window grows a warning-! alert (transmog-icon-warning-small) beside the
    Rescan button when promises to the current character are not visible in
    the draft - right-click it to clear.
    Co-authored-by: BlueAI Platform/opencode/GLM-5.3-Flash orosei-sylvanas@murlo.cz