BONUS_ROLL_RESULT
Fires with the reward of a bonus roll after BONUS_ROLL_STARTED. Blizzard's bonus roll frame slows its spinner and shows the reward. · description by wowlua
declare event BONUS_ROLL_RESULT(typeIdentifier: string, itemLink: string, quantity: number, specID: number, sex: number, personalLootToast: boolean, currencyID: number?, isSecondaryResult: boolean, corrupted: boolean)Payload
| # | name | type | description |
|---|---|---|---|
| 1 | typeIdentifier | string | The kind of reward, such as "item" or "currency". |
| 2 | itemLink | string | The reward's link. |
| 3 | quantity | number | How many were won. |
| 4 | specID | number | The loot specialization the reward was rolled for. |
| 5 | sex | number | |
| 6 | personalLootToast | boolean | Whether the reward came from personal loot. |
| 7 | currencyID | number? | The currency won, if the reward is a currency. |
| 8 | isSecondaryResult | boolean | Whether this is a secondary reward of the roll. |
| 9 | corrupted | boolean | Whether the item is corrupted. |
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) (Loot system, camelot 1.60.1). Description: written by wowlua where no documentation describes the entry.