Enhanced Raid Frames

Enhanced Raid Frames

940k Downloads

Concatenate nil value error casting spell from a macro

CosmicCleric opened this issue ยท 1 comments

commented

Issue description:

Targeting a training dummy, and call a macro that calls the (Affliction) Warlock spell "Mortal Coil" (while having a Felhunter pet out) generates an "attempt to concatenate local 'charges' (a nil value)" error.

Note that I am not in a party or raid at the time of the error.

Here is the macro ...

/cast Mortal Coil

I've confirmed that the macro does succeed, and the target dummy gets the debuff generated by the casting of the Mortal Coil spell.

How to reproduce:

  1. Create a macro with one line in it, "/cast Mortal Coil".
  2. Put the macro on an action bar (I used bottom-right bar).
  3. Target a 'Training Dummy' NPC (I used the one in The Royal Armory in Zandalar/Dazar'alor).
  4. Start combat by pressing the button that has the macro placed on it.
  5. Error happens immediately (its an instant cast spell).

Technical info:

  • Addon Version: 3.3.2
  • Client: Retail
  • Client Patch Version: 9.0.2.36949

Additional context:

List of active addons when the error condition happens ...

Details (DetailsRetail.9.0.2.8097.144)
Enhanced Raid Frames (3.3.2)
GTFO (4.57.1)
MoveAnything (18.0.4)
PetTracker (9.0.6)
Scrap (9.0.1)
TellMeWhen (9.0.3)
TomTom (v90002-1.2.0)

All addons were installed via the "Ajour" (version 0.5.4) Windows app (as discussed here).

Screenshots:

N/A

Lua error log:

Message: ...\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:877: attempt to concatenate local 'charges' (a nil value)
Time: Sun Dec 20 16:19:23 2020
Count: 5
Stack: ...\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:877: attempt to concatenate local 'charges' (a nil value)
[string "@interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua"]:877: in function SendCooldownUpdate' [string "@Interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua"]:760: in function ?'
[string "@interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua"]:469: in function `TriggerEvent'
[string "@interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua"]:509: in function <...\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:508>

Locals: spellId = 6789
cooldownTimeLeft = nil
charges = nil
(*temporary) = "U"
(*temporary) = ","
(*temporary) = 6789
(*temporary) = ","
(*temporary) = nil
(*temporary) = ","
(*temporary) = nil
(*temporary) = "attempt to concatenate local 'charges' (a nil value)"
CONST_COMM_COOLDOWNUPDATE_PREFIX = "U"
raidStatusLib =

{
GetPlayerSpecId = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:54
GetPlayerTalents = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:87
commHandler =
{
}
IsInGroup = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:182
IsCommAllowed = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:139
gearManager =
{
}
specAttribute =
{
}
UnpackTable = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:149
TCopy = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:104
playerAlive = true
playerInfoManager =
{
}
cooldownManager =
{
}
publicCallback =
{
}
PackTable = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:112
RegisterCallback = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:409
internalCallback =
{
}
CanReceiveComms = false
UnregisterCallback = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:421
inGroup = false
UpdatePlayerAliveStatus = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:64
mainControl =
{
}
Schedules =
{
}
isNearlyEqual = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:133
}
diagnosticComm = defined @interface\AddOns\Details\Libs\LibRaidStatus\LibRaidStatus.lua:47

commented

I don't believe this bug applies to Enhanced Raid Frames. Your error says the bug comes from "LibRaidStatus" which is not a library that we use. In fact the error appears to be from the addon Details. I would suggest reporting this bug there.