Jump to content

*Error* what really happens with : 'failed to fetch error'


Tokai2021

Featured Comment

  • Moderator
Posted
30 minutes ago, Tokai2021 said:

its noticeble that when these errors occurs, the next bet always laggs and becomes a losing bet.

Lag true, but "always becomes losing bet" is false, due that's not how Stake Originals work (Provably Fair). You can verify results for your past spins and upcoming spins with client and server seed. You will get unhashed server seed after you change your seeds. 

 

30 minutes ago, Tokai2021 said:

he marketing team push out a message that the games run better then ever before.

is this really the truth? cause i keep generating all these errors for over a year, and never ever have a green session on a day when these errors occur.

"the games run better then ever before" is not same thing than "you're guaranteed to win now". Mostly that means they (/provider) has done some improvements on their servers, so games should work generally better (less laggy etc)

 

30 minutes ago, Tokai2021 said:

I kindle request stake-team to give some explaination about what this error means and what the affects are on the gameplay.

what a player could possible do to prevent errors popping up?, but these errors generated are over multiple accounts on same time (see stake chat go wild, after errors), its less likely a single player is at fault when these errors pop up.

Seems to me like all that it does is fail to fetch a winning result.

Failed to fetch/GraphQL error/etc occurs most likely due Stake servers can't handle all requests it's getting, which could be happening, because poorly coding or bad servers.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

Privacy Policy Terms of Use