HeroRotation

HeroRotation

6M Downloads

[Monk/Windwalker]: LUA error when cooldowns near reset

eirhor opened this issue ยท 1 comments

commented

What version of HeroRotation are you using?

11.1.0.13

What version of HeroLib are you using?

11.1.0.05

What version of HeroDBC are you using?

11.1.0.03

What is the issue?

Getting a stream of LUA errors when both Invoke Xuen, the White Tiger and Storm, Earth, and Fire are on cooldown, with ~30 sec remaining, causing all rotation recommendations to disappear untill either one of them are off cooldown and I use either one of them.

29277x HeroLib/Class/Unit/Aura.lua:45: attempt to index local 'ThisSpell' (a nil value)
[HeroLib/Class/Unit/Aura.lua]:45: in function <HeroLib/Class/Unit/Aura.lua:41>
[tail call]: ?
[HeroLib/Class/Unit/Aura.lua]:114: in function 'BuffRemains'
[HeroLib/Class/Unit/Aura.lua]:132: in function 'BuffUp'
[HeroRotation_Monk/Windwalker.lua]:312: in function <HeroRotation_Monk/Windwalker.lua:309>
[HeroRotation_Monk/Windwalker.lua]:1079: in function '?'
[HeroRotation/Main.lua]:476: in function <HeroRotation/Main.lua:455>

Locals:
self = <table> {
 UseCache = true
 UnitNPCID = -2
 UnitCanBeAttacked = false
 UnitGUID = "Player-1305-0D194CB6"
 UnitID = "player"
 UnitExists = true
 TimeToXResourceMap = <table> {
 }
 PredictedResourceMap = <table> {
 }
 UnitName = "Rokemonk"
}
ThisSpell = nil
Filter = "HELPFUL|PLAYER"
Full = nil
(*temporary) = "Player-1305-0D194CB6"
(*temporary) = nil
(*temporary) = "Player-1305-0D194CB6"
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index local 'ThisSpell' (a nil value)"
GUID = "Player-1305-0D194CB6"
SpellID = 137639
Player = <table> {
 UseCache = true
 UnitNPCID = -2
 UnitCanBeAttacked = false
 UnitGUID = "Player-1305-0D194CB6"
 UnitID = "player"
 UnitExists = true
 TimeToXResourceMap = <table> {
 }
 PredictedResourceMap = <table> {
 }
 UnitName = "Rokemonk"
}
AuraDuration = nil
AuraExpirationTime = nil
AuraStack = nil
UnitID = "target"
Index = 1
AuraSpellID = nil

Icon Behavior

None

commented

This should now be fixed in commit b73de85