Before You Begin

• I confirm that I have downloaded the latest version of the addon.
• I am not playing on a private server.
• I checked for an existing, open ticket for this issue and was not able to find one.
• I edited the title of this bug report (above) so that it describes the issue I am reporting.

Describe the Issue

I have been randomly getting this message when in Devastation spec using WoWhead's "leveling" build at L70. This has been going on for a number of months now through multiple WoW and Hekili updates

`2x Hekili/UI.lua:2548: attempt to index field 'empowerment' (a nil value)
[string "@Hekili/UI.lua"]:2548: in function <Hekili/UI.lua:2547>
[string "=[C]"]: ?

Locals:
self = Hekili_Primary_B1_Cooldown {
0 =
_occ_priority = 1
_occ_show = false
_occ_gcd = true
noCooldownCount = false
lastDuration = 1.300000
_occ_kind = "default"
_occ_duration = 1.300000
_occ_settings =

{
}
_occ_start = 95373.877000
lastStart = 95373.877000
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index field 'empowerment' (a nil value)"
b = Hekili_Primary_B1 {
Overlay = Texture {
}
Empowerment = Hekili_Primary_B1_Empower {
}
Highlight = Texture {
}
Keybinding = Hekili_Primary_B1_KB {
}
PixelSnapDisabled = true
lastAction = "fire_breath"
Targets = Hekili_Primary_B1_Targets {
}
Text = false
Image = 4622458
0 =
Action = "fire_breath"
targetShown = false
glowing = false
Icon = Texture {
}
Texture = Texture {
}
index = 1
Caption = Hekili_Primary_B1_Caption {
}
unusable = false
Keybind = "SW"
DelayText = Hekili_Primary_B1_DelayText {
}
KeybindFrom = 1
Backdrop = Hekili_Primary_B1_Backdrop {
}
texCoords = {
}
glowStop = defined @Hekili/UI.lua:2479
Ability = {
}
DelayIcon = Hekili_Primary_B1_DelayIcon {
}
EmpowerLevel = Hekili_Primary_B1_EmpowerLevel {
}
display = "Primary"
ExactTime = 95375.177000
Cooldown = Hekili_Primary_B1_Cooldown {
}
Recommendation = {
}
}
conf = {
primaryWidth = 45
rel = "CENTER"
numIcons = 4
queue = {
}
y = -371.086884
x = -72.657486
primaryHeight = 45
}
state = {
swing = {
}
FindPlayerAuraByID = defined @Hekili/Utils.lua:516
summonPet = defined @Hekili/State.lua:1188
role = {
}
IsKnown = defined @Hekili/State.lua:7007
UnitGUID = defined =[C]:-1
purge = {
}
stat = {
}
ptr = 0
off_hand = {
}
floor = defined =[C]:-1
essence = {
}
tonumber = defined =[C]:-1
SetWhitelist = defined @Hekili/State.lua:6722
holds = {
}
display = "Primary"
prev_off_gcd = {
}
SetDefaultVariable = defined @Hekili/State.lua:4494
mainhand_speed = 3.121000
channelSpell = defined @Hekili/State.lua:1251
equipped = {
}
gain = defined @Hekili/State.lua:1559
TimeToReady = defined @Hekili/State.lua:7364
setStance = defined @Hekili/State.lua:1162
history = {
}
varPaths = {
}
args = {
}
UnitAura = defined @Blizzard_Deprecated/Deprecated_10_2_5.lua:34
AddToHistory = defined @Hekili/Events.lua:1082
SetupCycle = defined @Hekili/State.lua:796
print = defined @Hekili/State.lua:570
GetSpellCount = defined =[C]:-1
ClashOffset = defined @Hekili/State.lua:7581
azerite = {
}
offset = 4.870000
QueuedCastRemains = defined @Hekili/State.lua:6280
ApplyCastingAuraFromQueue = defined @Hekili/State.lua:6304
TargetBuffUp = defined @Hekili/State.lua:5819
pvptalent = {
}
rawGain = defined @Hekili/State.lua:1566
GetItemGem = defined =[C]:-1
UnitIsFriend = defined =[C]:-1
action = {
}
addStack = defined @Hekili/State.lua:1036
HasRequiredResources = defined @Hekili/State.lua:7327
TargetDebuffUp = defined @Hekili/State.lua:5824
UnitCanAttack = defined =[C]:-1
rawSpend = defined @Hekili/State.lua:1579
script = {
}
IsUsable = defined @Hekili/State.lua:7185
GetItemInfo = defined =[C]:-1
GetPlayerAuraBySpellID = defined =[C]:-1
health = {
}
`

How to Reproduce

Start attacking as Devastation spec evoker following the recommended Heili rotation. Randomly but quite frequently the error occurs.

Player Information (Link)

https://pastebin.com/EYzR19f6

Error Messages (Link)

https://pastebin.com/V3brDZPP

Additional Information

No response

Contact Information

No response

I think this is already fixed in 1.0.3; I could not replicate it. Can you confirm after updating to the latest release?

Thanks it does seem to finally be behaving now, but it didn't always do it either. I'll re-open if it shows back up again, or create a new ticket whichever is better.