CHAT_MSG_ADDON_LOGGED
Fires when an addon message sent with C_ChatInfo.SendAddonMessageLogged arrives under a prefix the player's client registered with C_ChatInfo.RegisterAddonMessagePrefix. · description by wowlua
declare event CHAT_MSG_ADDON_LOGGED(prefix: string, text: string, channel: string, sender: string, target: string, zoneChannelID: number, localID: number, name: string, instanceID: number)Payload
| # | name | type | description |
|---|---|---|---|
| 1 | prefix | string | The prefix the message was sent with. |
| 2 | text | string | The message payload. |
| 3 | channel | string | The chat type the message came through, such as "PARTY", "GUILD" or "WHISPER". |
| 4 | sender | string | The name of the sender. |
| 5 | target | string | The name of the target, for whispered messages. |
| 6 | zoneChannelID | number | The ID of the zone channel, for channel messages. |
| 7 | localID | number | The channel's number in the player's channel list, for channel messages. |
| 8 | name | string | The channel's name, for channel messages. |
| 9 | instanceID | number |
Blizzard's documentation marks the event as synchronous.
In wowlua's emulated client
not implementedFor an event, not implemented means the emulated client never fires it by itself. Fire it from a test with
mock.fireEvent, or mock.fireUnitEvent for a unit event. The event must be one the flavor documents, and its payload is checked against the documentation. what the statuses meansources
Name, payload and flags: Blizzard's API documentation (Blizzard_APIDocumentationGenerated) (ChatInfo system, camelot 1.60.1). Description: written by wowlua where no documentation describes the entry.