AdiCCMonitor

6 - Latest alpha produces error in combo with another mod

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?

1.0-beta-1-11-gbceddbe

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[1]\":9: in function <[string \"safecall Dispatcher[1]\"]: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,
		}, -- [997]

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.

User When Change
Adirelle Feb 19, 2011 at 10:31 UTC Changed status from New to Fixed
Zidomo Feb 17, 2011 at 20:14 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 2 comments
  • Avatar of Adirelle Adirelle Feb 19, 2011 at 10:31 UTC - 0 likes

    There is indeed a small typo at that line in Alerts.lua, that prevents to pass the right “type” parameter. I’ll fix it.

    However, passing “nil” as the type for SendAddonMessage is perfectly allowed by Blizzard API. So I suggest you to also report a bug for StopAddonMessage.

    By the way, if StopAddonMessage prevents AdiCCMonitor from sending messages and other players in the party/raid also use AdiCCMonitor in “chatty” settings (e.g. announcing to party or raid), it will result in several messages from diferent players for the same events.

  • Avatar of Zidomo Zidomo Feb 19, 2011 at 09:17 UTC - 0 likes

    This error still happens consistently in the same circumstances with the current 1.0-beta-1-12-g8dab38b, so can't use it. Testing, it does not happen with the two-versions-prior 1.0-beta-1-8-gc0b9b4e.

  • 2 comments

Facts

Last updated
Feb 19, 2011
Reported
Feb 17, 2011
Status
Fixed - Developer made requested changes. QA should verify.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
0

Reported by

Possible assignees