WoW:API LFGQuery: Difference between revisions
Jump to navigation
Jump to search
(part of a API redesign proposal, please don't change the layout for the next few days) |
(corrected event details (tested 12/27/06 - wow 2.0.1)) |
||
| Line 15: | Line 15: | ||
===Events=== | ===Events=== | ||
: Triggers | : Triggers UPDATE_LFG_LIST | ||
:: Triggered as soon as query results become available ( | :: Triggered as soon as query results become available (works, tested on Live client - Dec 27, 2006) | ||
===Details=== | ===Details=== | ||
Revision as of 02:47, 28 December 2006
Find all players who are looking for a group for a specified objective
LFGQuery(category, objective[, class])
Takes
- Number category
- Must be the index of one of the values retrieved with GetLFGTypes()
- Number objective
- Must be the index of one of the values retrieved with GetLFGTypeEntries(category)
- Number class (optional)
- You can probably specify which character class you are searching for (priest, warrior, druid, etc.), but exact usage is unknown
Returns
- Nothing
Events
- Triggers UPDATE_LFG_LIST
- Triggered as soon as query results become available (works, tested on Live client - Dec 27, 2006)
Details
- Use GetNumLFGResults() to retrieve the number of results and then iterate over them with GetLFGResults(index).
- This function, much like any other LFG function, has highly inconsistent code. Executing LFGQuery(nil) will tell you "Usage: LFGQuery(param1[, class])". That prototype is quite outdated but never has been changed, further supporting the assumption stated below.