1.0.17

Lib: RangeCheck-3.0

1.0.17 (2024-08-25)

Full Changelog Previous Releases

• Hero Talent spell overrides don't check range.
  Living Flame, Smite and Lightning Bolt can be temporarily replaced by an override spell, rendering the spell useless for range checks.
  This adds "fallback" spells with a higher priority which will be picked instead.
  Emerald Blossom is available and unmodified for Pres and Aug Evoker.
  Mind Blast is available for Disc Priest, where the override happens and no SW:P is available.
  Earth Shock and Elemental blast share the same choice node and act as a replacement for Lightning Bold in this case for Elemental Shaman.

• Offspec spells won't work either. (#33)

  • Offspec spells won't work either.

  This covers unlearned spells from off-specs which appear in the spellbook.

• Remove "Future Spells" from available checks. (#32)

  • Remove "Future Spells" from available checks.

  With 11.0.2.56196 unlearned spells don't work anymore with C\_Spell.IsSpellInRange, similar to how C\_SpellBook.IsSpellBookItemInRange works.

1.0.16

Lib: RangeCheck-3.0

1.0.16 (2024-07-16)

Full Changelog Previous Releases

• Shadowflame can have a unique range in Season of Discovery

• Fix LUA error on using a Portal
  I can't reproduce the actual issue, but the fix is trivial.
  Fixes: #29

• Workaround for unlearned spellbook spells in TWW (#30)

  • Switching to C\_Spell.IsSpellInRange for TWW

  This replaces C\_SpellBook.IsSpellBookItemInRange with C\_Spell.IsSpellInRange in the TWW fallback, to ensure even unlearned spells can be used for range check. IsSpellBookItemInRange does not check unlearned spells.

  To make this work, the spell index used and returned from findSpellIdx is now the spellID in retail, but still the spellbook index for classic/era.

1.0.15

Lib: RangeCheck-3.0

1.0.15 (2024-07-24)

Full Changelog Previous Releases

• Fix error with IsSpellBookItemInRange when loadDepractionFallbacks cvar is enable
  Fixes #26

1.0.14

Lib: RangeCheck-3.0

1.0.14 (2024-07-23)

Full Changelog Previous Releases

• Bump retail toc

1.0.13

Lib: RangeCheck-3.0

1.0.13 (2024-06-11)

Full Changelog Previous Releases

• proper fix for IsSpellInRange
• proper fix for IsSpellInRange on TWW
• Workaround IsSpellInRange & GetSpellBookItemName moved to C_* namespace on TWW
• Fix spellbook functions bookType arg on TWW
• Fix IsItemInRange error on TWW
• Update toc for 10.2.7
• Cataclysm toc file
• Use C_Item api and get ready for TWW
• Register PLAYER_TALENT_UPDATE event on cataclysm
• InCombatLockdownRestriction now applies to all version of the game

1.0.12

Lib: RangeCheck-3.0

1.0.12 (2024-03-05)

Full Changelog Previous Releases

• Fix spell checkers on Classic/SOD
  Sspells with have a min range, e.g. a spell with an 8-30y range, cannot
  be easily used of range checking, because if it isn't in range, that
  could be <8 or >30. Thus we used a second checker to distinguish between
  those two cases.
  Previously only other spells would be consider, but in some cases
  classes have no spells that can fill that gap.
  Thus use an idea by kodewdle to fall-back to the interact list. All we
  need is an interact distance that is bigger than min range and less than
  the max range.
  Fixes: #16

• ShowAllSpellRanks causing range to be invalid when toggled. (#15)
  The library internally in the spell checkers, e.g. checkers_Spell uses the "spell index". The spell index is actually the index into the player's spell book, not the spell id.

  Toggling the "Show all ranks" toggle does change these indexes, since multiple ranks are shown, thus the checkers need to reinitialized.

1.0.11

Lib: RangeCheck-3.0

1.0.11 (2024-02-07)

Full Changelog Previous Releases

• apply InCombatLockdownRestriction for classic era

1.0.10

Lib: RangeCheck-3.0

1.0.10 (2024-01-26)

Full Changelog Previous Releases

• Fix uncached items not setting foundNewItems
  In d0ae656 the logic around itemRequestTimeout was incorrectly
  changed, which exposed a bug in the logic of processItemRequest
  Fixes WeakAuras bug #4836

• Improve Item request processing (#13)
  Currently the addon isn't correctly tracking when an item doesn't exist. This is causing an excessive number of item info queries when logging in, since the same items are being checked repeatedly.

  Testing was done on Classic Era, logging in for the first time after restarting the game.

  Before changes, I recorded 242 GET_ITEM_INFO_RECEIVED events over ~85 seconds when the addon loads.

  After changes, I recorded 30 GET_ITEM_INFO_RECEIVED events over ~5 seconds when the addon loads.

  I've also tested changes on Wrath, but not Retail. As far as I know, the ItemMixin API is unchanged in all game versions.

1.0.9

Lib: RangeCheck-3.0

1.0.9 (2023-12-18)

Full Changelog Previous Releases

• Fix error for not assistable friendly unit in combat

1.0.8

Lib: RangeCheck-3.0

1.0.8 (2023-12-09)

Full Changelog Previous Releases

• Tweak
• Don't assume assists can be attacked.
• Re-enable hostile range checking in combat.
• Add warlock spells in Classic
• Update TOC for Patch 10.2.0