[Warrior Protection]: Addon throws error after latest build
Flaregood opened this issue · 5 comments
What version of HeroRotation are you using?
11.1.7.01
What version of HeroLib are you using?
11.1.7.01
What version of HeroDBC are you using?
11.1.7.01
What is the issue?
I'm not sure how to best describe this but I notice sometimes the "suggested spell" is not shown on screen. The only thing I can tell you is that is started happening today
Icon Behavior
Icon disappears
Please provide the error. If the icon is disappearing, then a lua error is occurring. If you don't have an addon like BugSack capturing lua errors, then please enable lua errors with the in-game command /console scriptErrors 1. Once you've reported the error, you can then disable the error display with /console scriptErrors 0.
I'm currently raiding. I will install BugSack and provide you with the error details asap
I'm sorry about this formatting. I don't know how to make it better
14x ...rfaceHeroLib/Class/Unit/Player/Equipment.lua:527: attempt to index field '?' (a nil value)
[HeroLib/Class/Unit/Player/Equipment.lua]:527: in function 'HasTier'
[HeroRotation_Warrior/Protection.lua]:381: in function '?'
[HeroRotation/Main.lua]:476: in function <HeroRotation/Main.lua:455>
Locals:
self =
UseCache = true
UnitNPCID = -2
UnitCanBeAttacked = false
UnitGUID = "Player-1309-0C96F315"
UnitID = "player"
UnitExists = true
TimeToXResourceMap =
}
PredictedResourceMap =
}
UnitName = "Flaregood"
}
Tier = 31
Pieces = 2
DFS4Translate =
13 =
}
7 =
}
1 =
}
2 =
}
4 =
}
8 =
}
9 =
}
5 =
}
10 =
}
3 =
}
6 =
}
12 =
}
11 =
}
}
Class = 1
Spec = 73
(*temporary) = nil
(*temporary) = "2pc"
(*temporary) = "pc"
(*temporary) = "attempt to index field '?' (a nil value)"
Cache =
GUIDInfo =
}
APLVar =
}
Enemies =
}
HasBeenReset = true
SpellInfo =
}
UnitInfo =
}
MiscInfo =
}
Persistent =
}
ItemInfo =
}
}
Ah, the Prot APL still has a ridiculous check for tier from Amirdrassil. I recently removed the ability to check tier sets from prior to TWW. I'll push a fix momentarily, and I'll leave another comment here when it's done.
Ok. The fix is pushed in commit f48992b
This commit is included in release version 11.1.7.02, which should be coming to your typical download spot shortly.