DropTheCheapestThing

v2026.4-13-g1513f9d (2026-09-20)

Full Changelog Previous Releases

• An option to stop marking junk in the bag addons (#2)
  The switch is read inside the two callbacks rather than around the
  registration. Bagnon and Baganator are told about the plugin once, when they
  load, and neither offers a way to withdraw it, so a flag checked at
  registration would only take effect after a reload -- and an option that needs
  a reload is one people report as broken.
  Defaults to on, which is what everyone has today, and the toggle greys itself
  out when neither bag addon is loaded, the way the appearance toggle does
  without transmog.
• API: drop with sell_if_available could be confused by unsellable items
  If at a merchant, and the cheapest item was something unsellable, if
  sell_if_available was set we'd call drop_bagslot with drop_only based
  on the function-level sell_if_available, not the item-level sell_only
  which actually took whether it was sellable into account.
  This wouldn't be terrible, but it would stall selling items via the API
  because it'd claim it was selling it, print the message, then error "the
  merchant doesn't want this item"... and just get stuck.
• Bindings: also offer bindings for drop/sell/sell-or-drop
• Bindings: add a binding for never consider as well
• Bindings: move to a dedicated category
  Blizzard stopped header displaying anything back in 2022, and doesn't
  plan to change that (see: Stanzilla/WoWUIBugs#305). This makes a binding
  like "Toggle the item under the mouse" extremely hard to interpret when
  mixed with other addon bindings.
  Refs #34
  Follow-up-to: 513e44fa7d48122ebaf6528a92b59e8ec34faba5
• Don't load Bindings.xml in the TOC
  It's magic, Blizzard loads it if it's present. It being the TOC causes
  an error because blizzard
  Refs #34
  Follow-up-to: 513e44fa7d48122ebaf6528a92b59e8ec34faba5
• Auction values were used for the sale total chat summary
• API.Drop ignored sell_if_available
• A key that toggles the item under the mouse in Always Consider (#30)
  Built over the snippet in the issue, with the Lua moved out of the XML into
  config.lua -- the file that already holds db and already owns the two lists --
  and the message going through DEFAULT_CHAT_FRAME like the rest of the addon.
  No default key. The binding sits under its own header in the keybinding UI,
  so it is bindable to a controller button as well, which is free with Blizzard
  bindings and is what makes the addon usable without a mouse.
  .luacheckrc gains the two BINDING_ globals; without them luacheck fails the
  build with "setting non-standard global variable", which I checked by running
  your lint both ways on a scratch runner.
• Never consider the greys that buy the Baubleworm pets (#14)
  Nine grey items are the currency for the three Baubleworm pets. They look
  exactly like junk, and selling one costs the pet, so they go in the same
  hardcoded list as the Haunted Memento. Item ids are the ones in #14.
• Slash commands for drop and sell (#4)
  /dtct drop and /dtct sell do what the minimap button's clicks do, through the
  API that api.lua already exposes; /dtct sell all sells the list, capped at the
  buyback limit. Anything else opens the config, so /dtct on its own behaves as
  it always has.
• Load on World of Warcraft: Forever (interface 16001)
  Forever is a fourth game line beside Retail, Classic Era and the Classic
  expansions. Build 1.60.1 (69913) reports interface 16001, so the addon shows
  as out of date there and only loads with the out-of-date box ticked.
  No code change is needed. That client reports WOW_PROJECT_ID as
  WOW_PROJECT_MAINLINE, and its API is complete for everything this addon
  touches: C_Container, C_Item and C_TransmogCollection all exist. Checked in
  the game rather than assumed -- dropping and selling work, and the merchant
  hook takes.
  BigWigsMods/packager already maps 16??? to the forever game type, so the
  release workflow needs nothing.
• Fix quest item detection