[sirinsidiator]

Originally Posted by ZOS_ChipHilseberg What kind of functions would you like to see added?

A few suggestions that have gathered in my head over time:

1. SetTradingHouseFilter currently accepts up to 8 filter arguments.
   In order to be able to implement an "all" subcategory for crafting mats in AwesomeGuildStore I would need to pass 19 arguments to get all the item types.
   A few possible solutions:
   • add 11 more arguments (sounds as bad as it probably is)
   • remove all but one and allow a table to be passed with up to 19 filter arguments (sounds equally as bad)
   • add an EQUIP_TYPE_CRAFTING for crafting items (ugly hack, but probably the easiest solution)
   • add new meta item types that allow to search for item categories (e.g. ITEM_CATEGORY_WEAPON, ITEM_CATEGORY_CRAFTING, etc.) (might be the cleanest solution but probably requires some work in the backend)
2. New filter types for:
   • item name
   • set name
   • set boni
   • known state (for recipes and motifs)
   • per unit price range
   • stack size range
3. New sort flag to allow sorting by per unit price.
   
4. GetSearchResultPageCount()
   Returns how many pages the current search offers.
   
5. GetSearchResultItemCount()
   Returns how many items are found overall with the current search.
   
6. SetPendingItemPurchase and GetTradingHouseSearchResultItemInfo only accept a local index within the last searched page.
   If the search results had indices that are independent of the current page it would allow us to locally cache pages and still be able to purchase items regardless of which page of the current search we are requesting.
   
7. Increase the search result limit from 100. It would save a lot of time that we loose because of the search cooldown if we could just request more at once.
   Maybe even add a function (SetSearchResultLimit) so we can set it ourselves to any value below a certain hard limit.
   A limit of 5000 results would allow downloading all items in most guild stores in 1-2 request and filtering them locally afterwards.
   This could potentially save a lot of processing power on the server and allow for much faster user interaction.

Would be nice to see any or all of them in the future