GARRISON_MISSION_COMPLETE_RESPONSE
Fires when the server answers a request to complete a garrison mission. Blizzard's mission complete screens play the result. · description by wowlua
declare event GARRISON_MISSION_COMPLETE_RESPONSE(missionID: number, canComplete: boolean, success: boolean, bonusRollSuccess: boolean, followerDeaths: GarrisonFollowerDeathInfo[], autoCombatResult: AutoCombatResult?)Payload
| # | name | type | description |
|---|---|---|---|
| 1 | missionID | number | The mission. |
| 2 | canComplete | boolean | Whether the mission could be completed. |
| 3 | success | boolean | Whether the mission succeeded. |
| 4 | bonusRollSuccess | boolean | Whether the bonus roll succeeded. |
| 5 | followerDeaths | GarrisonFollowerDeathInfo[] | The followers who died on the mission. |
| 6 | autoCombatResult | AutoCombatResult? | The combat log of an adventure mission, if any. |
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) (GarrisonInfo system, camelot 1.60.1). Description: written by wowlua where no documentation describes the entry.