PET_FORCE_NAME_DECLENSION
Fires when the player must enter the declined forms of a pet's name, on clients with declensions. Blizzard's declension frame opens for the pet. · description by wowlua
declare event PET_FORCE_NAME_DECLENSION(name: string, petNumber: number?, declinedName1: string?, declinedName2: string?, declinedName3: string?, declinedName4: string?, declinedName5: string?)Payload
| # | name | type | description |
|---|---|---|---|
| 1 | name | string | The pet's name. |
| 2 | petNumber | number? | The pet's number. |
| 3 | declinedName1 | string? | A declined form of the name. |
| 4 | declinedName2 | string? | A declined form of the name. |
| 5 | declinedName3 | string? | A declined form of the name. |
| 6 | declinedName4 | string? | A declined form of the name. |
| 7 | declinedName5 | string? | A declined form of the name. |
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) (PetInfo system, camelot 1.60.1). Description: written by wowlua where no documentation describes the entry.