Simple Item Level

v66-8-ga4d22ea (2026-08-09)

Full Changelog Previous Releases

• Key enchantable slots on the expansion, not the flavour
  Classic keeps rolling forward, and it is close to the expansions where
  the armor slots themselves changed, so a single classic table with
  overrides is getting awkward. Give each expansion a row instead, with
  retail as simply the newest of them, and make the enchanter-only ring
  rule data rather than a flavour test. An expansion with no row falls
  back to the newest row below it.
• Enchantable slots per classic expansion, not just Mists
  TBC Classic Anniversary means that a classic/classic_era test is
  insufficient. Key the head and ring slots on the expansion the client
  actually reports. Burning Crusade needs this most: it has ring
  enchants, which vanilla does not, and it reports a different Enchanting
  skill line than Mists does.
  The enchanter test also ran while the file loaded, before the
  professions are known, so it would answer no for everybody. Check when
  a ring is examined instead.
• Flag profession tools that have no enchant
  Tool enchants have been available since Dragonflight, and Midnight still has
  them, but the slot was never in the enchantable list.
• Average item level would read low on retail in 12.1
  The ranged slot check treated a successful pcall as proof that the slot
  exists, but GetInventorySlotInfo("RANGEDSLOT") returns false in 12.1
  instead of erroring. That counted a slot that is not there, so the
  total was divided by 16 rather than 15. Ask IsRangedSlotShown instead,
  which is now available in Classic and so can be used.
• Update TOC for 12.1.0, 2.5.6
• Stop relying on deprecated inventory slot globals
  12.1 moves GetInventorySlotInfo into C_PaperDollInfo and GetInspectSpecialization
  into C_SpecializationInfo.
• Average item level could error on other units in combat
  12.1 makes UnitClass and GetInspectSpecialization return secrets whenever
  the unit's identity is secret, and a comparison against a secret is an
  immediate error. Guard both. The fury warrior check then falls back to the
  15-slot count, which is what it already does on classic.
• Actions: use the luacheck action instead of installing it from luarocks
  The lint job ran apt-get install with no apt-get update ahead of it, which
  fails whenever the runner image package index is stale.
  lunarmodules/luacheck@v1 replaces those three steps and runs the same
  luacheck . --no-color -q. Updates the checkout action from v2 to v7, which
  was still running a node version GitHub is retiring; nothing in that range
  affects a push-triggered workflow. Pins the packager to v2 rather than
  master, so an upstream change can no longer land in a release without
  warning; v2 is the maintained major tag, so fixes within the v2 line still
  arrive.