CHAT_MSG_BG_SYSTEM_ALLIANCE
Fires when a battleground system message for the Alliance arrives. Blizzard's UI also shows it in the raid warning frame. · description by wowlua
declare event CHAT_MSG_BG_SYSTEM_ALLIANCE(text: string, playerName: string, languageName: string, channelName: string, playerName2: string, specialFlags: string, zoneChannelID: number, channelIndex: number, channelBaseName: string, languageID: number, lineID: number, guid: string, bnSenderID: number, isMobile: boolean, isSubtitle: boolean, hideSenderInLetterbox: boolean, suppressRaidIcons: boolean, discordInfo: DiscordChatInfo)Payload
| # | name | type | description |
|---|---|---|---|
| 1 | text | string | The message text. |
| 2 | playerName | string | |
| 3 | languageName | string | |
| 4 | channelName | string | |
| 5 | playerName2 | string | |
| 6 | specialFlags | string | |
| 7 | zoneChannelID | number | |
| 8 | channelIndex | number | |
| 9 | channelBaseName | string | |
| 10 | languageID | number | |
| 11 | lineID | number | |
| 12 | guid | string | |
| 13 | bnSenderID | number | |
| 14 | isMobile | boolean | |
| 15 | isSubtitle | boolean | |
| 16 | hideSenderInLetterbox | boolean | |
| 17 | suppressRaidIcons | boolean | |
| 18 | discordInfo | DiscordChatInfo |
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.