We don’t like limiting our service and do consider fair and reasonable as the best way for all of us.
We don’t like users that are trying to walk around our caching in our API gateway, not respect certain error-responses or exorbitant hammering of certain endpoints.
But sometimes things happen that shouldn’t, which then leads to the collective of tibiadata-users to suffering as of the release with v4.2.0.
What happened?
Due to some heavy use of the highscores endpoint (around 150.000 requests on a 10 minutes period), the creators of Tibia have asked us to implement limitations.
The changed behaviour did create an increase of traffic over 100% and due to the short period of time, it created issues on their side.
What endpoints are effected?
Currently the restriction-mode is only enabled on the highscore-endpoints, which were subject to the large change in request behaviour.
You can still use the highscore-endpoint itself, but you the option to use the vocation filtering is removed and you can only use all as filter.
Will this be permanent?
Not sure about that yet, but hopefully not. We are still in communication with CipSoft about this.
Still want some filtered highscores?
Contact us (preferably on Discord) if you have some low amount of highscore-requests and we can try to figure out a way forward.
Kind regards,
Tobias
