What steps will reproduce the problem?
1. Load AdiCCMonitor (version below) & StopAddonMessage v1.6.2-beta.
2. Join a party. Or log on when in a party. Or zone into an instance or another zone while in a party.
What is the expected output? What do you see instead?
Expected: no issues.
Instead: 100% consistent error occurs.
What version of the product are you using?
Do you have an error log of what happened?
["message"] = "StopAddonMessage-1.6.2beta\\core.lua:293: attempt to index local 'type' (a nil value)\n(tail call): ?:\nAdiCCMonitor-1.0-beta-1-11-gbceddbe\\Alerts.lua:143: in function `SendMessage'\nAdiCCMonitor-1.0-beta-1-11-gbceddbe\\Alerts.lua:148: in function <Interface\\AddOns\\AdiCCMonitor\\Alerts.lua:147>\n(tail call): ?:\n(tail call): ?:\n<in C code>: ?\n<string>:\"safecall Dispatcher\":9: in function <[string \"safecall Dispatcher\"]:5>\n(tail call): ?:\nAceTimer-3.0-5 (Ace3):166: in function <Interface\\AddOns\\Ace3\\AceTimer-3.0\\AceTimer-3.0.lua:138>\n\n ---", ["type"] = "error", ["session"] = 1590, ["counter"] = 1, }, -- 
Please provide any additional information below.
AdiCCMonitor_Alerts is listed in StopAddonMessage in its "??" section (something it doesn't recognize). By default, have it so it lets through comms it hasn't seen before. Thus, AdiCCMonitor_Alerts had full comm capabilities.
The previous v1.0-beta-1-8-gc0b9b4e may or may not have also had this issue, but for sure v1.0-beta-1 did not.
- 2 comments