Hey @darthn8ers and thanks for your thoughts and suggestion about it!
Actually it is like that:
As soon as you vote on the 3rd party website with your steam login, a database of them gets your vote. Letâs say 3. Then, it is a weird âper day basisâ logic. In fact it is âevery ~7AM it gets resettedâ.
Anyways, all I do now is: call the API (their database) and grab the vote count from you (=> 3).
Next day, their database gives me a 4 and so on, if you voted.
However, during the process of voting and claiming (each different database tables) there must be a delay. While I grab the information as soon as you click, their database must have some delay or so.
Hence you click on cliam and you still get the reward from day 3. But as soon as I reload their database for example it shows me a 4.
TL;DR: a claim request from a player seems like a database refresh on their end which is the worst.
To make it 100% bulletproof I either should be able to send a âfakeâ claim request to their database which does not count but updates their counter, so you can get the right reward OR they implement a new API Call to ONLY get the vote count, separated from the rest, which I requested but got a generic âthanks we will consider itâ response.
Both issues canât be fixed by you or us.
ONLY thing we might implement now: a command which checks your history.
If reward of today === same as day before ==> +1RP && +7000 credits