Files 2
Downloads 83,234
Favorites 146
View Bug Report
Error when switching guilds
Bug #: 906
File: Price Tracker
Date: 06/29/14 06:00 AM
By: Sephiroth018
Status: Fixed
When the scan tries to switch to another guild, there is an error saying "Too many searches in rapid succession". This comes from the fact that switching guilds now also is affected by the delay between searches. It can easily be checked by manually doing a search and then trying to switch the guild while the search button is inactive.
I would recomend to use GetTradingHouseCooldownRemaining() to get the required delay and then using zo_callLater to delay switching the guild by the value returned from GetTradingHouseCooldownRemaining(). Then you would have to again use GetTradingHouseCooldownRemaining() to get the required delay before doing the next search.

RSS 2.0 Feed for Bug CommentsNotes Sort Options
By: Barvazon - 06/30/14 12:24 AM
Hi Sephoroth018,

I tried using the new function, without success. You are correct that the bug occurs when you change the guild. However, using GetTradingHouseCooldownRemaining() has absolutely no effect -- the error still appears. In fact, waiting more than 3 times the required cooldown will also generate the bug. I am trying to come up with a workaround for the problem, but I think this API is fundamentally broken.
By: Barvazon - 07/04/14 08:34 PM
Should be fixed in v1.6
This appears to have been a problem with the function that switches between guilds. As I understand it, that function started returning an error when executed too quickly, just as the search function returns an error. This is a new behavior in the latest API version. I added a delay, so that guild switching will no longer return an error. Please let me know if you still see the error when scanning items.