Cuhbert Posted January 31, 2023 #1 Posted January 31, 2023 So I have bet hundreds of thousands of bets on keno and for some reason last night when i typed .66 it auto assigned the decimal point a value of 0 and inputted my bet as 066 and I set it to auto bet and tore through my balance. This seems like it could be a major issue that needs to be addressed. When the decimal point is entered it should maintain the value of a decimal point followed by the numbers entered (which by the way has always worked this way in the past for me up until last night). I know a few other players it recently happened to now. Live chat says there is nothing wrong. I agree I should verify before starting autobet what the amount is but when you are in the heat of the moment it is a very easy hiccup to occur. Now I at the very least would hope stake staff and team would make sure when someone presses the decimal point that it inputs a decimal point and NOT a 0. I have a attached stakes response to this problem as a picture. Apparently .66 is a value of $66 and I am the person that is wrong. Quite a delusional stance from the support team whom I respect a great deal. @Eddie @Stefan
youcheckibet Posted February 1, 2023 #2 Posted February 1, 2023 2 hours ago, Cuhbert said: So I have bet hundreds of thousands of bets on keno and for some reason last night when i typed .66 it auto assigned the decimal point a value of 0 and inputted my bet as 066 and I set it to auto bet and tore through my balance. This seems like it could be a major issue that needs to be addressed. When the decimal point is entered it should maintain the value of a decimal point followed by the numbers entered (which by the way has always worked this way in the past for me up until last night). I know a few other players it recently happened to now. Live chat says there is nothing wrong. I agree I should verify before starting autobet what the amount is but when you are in the heat of the moment it is a very easy hiccup to occur. Now I at the very least would hope stake staff and team would make sure when someone presses the decimal point that it inputs a decimal point and NOT a 0. I have a attached stakes response to this problem as a picture. Apparently .66 is a value of $66 and I am the person that is wrong. Quite a delusional stance from the support team whom I respect a great deal. @Eddie @Stefan I really think this is just a lesson is double checking. Also you could have won and you'd be happy about it. I agree it is worth them checking if it is an issue definitely.
Cuhbert Posted February 1, 2023 Author #3 Posted February 1, 2023 1 hour ago, youcheckibet said: I really think this is just a lesson is double checking. Also you could have won and you'd be happy about it. I agree it is worth them checking if it is an issue definitely. 1 hour ago, youcheckibet said: I really think this is just a lesson is double checking. Also you could have won and you'd be happy about it. I agree it is worth them checking if it is an issue definitely. I don’t care about the money. It’s the fact that something is wrong and it needs to be fixed.
malikxxx Posted February 1, 2023 #4 Posted February 1, 2023 Same issue i have been facing too although avoided the mistake by carefully typing the amount
N8erade91 Posted February 1, 2023 #5 Posted February 1, 2023 Yes! This happened today to me and did a $44 bet, I only ever do 1 or $2 bets. This fucking pissed me off but figured what will support do. Kept trying and had same issue your describing
Mintyx77 Posted February 1, 2023 #6 Posted February 1, 2023 Il put my expirience in here cause what got me thinking is the fact that i raised ticket to support about this same problem in less than 24h ago... I wanted to do 0.05$ bets on keno yet it happened me more than 3 times that input was 005... refreshed cleared cache and still it happened ... ( . )Was not even registered... I know its our responsibility to check before betting and our own fault but still seeing post in forum raised me some questions If Its one time or fast typing its coincidence but to happen to many players in same day makes u wonder... Anyhow be carefull what u type in and check it triple times cause it is really our own fault somehow :)
Cuhbert Posted February 1, 2023 Author #7 Posted February 1, 2023 6 minutes ago, Mintyx77 said: Il put my expirience in here cause what got me thinking is the fact that i raised ticket to support about this same problem in less than 24h ago... I wanted to do 0.05$ bets on keno yet it happened me more than 3 times that input was 005... refreshed cleared cache and still it happened ... ( . )Was not even registered... I know its our responsibility to check before betting and our own fault but still seeing post in forum raised me some questions If Its one time or fast typing its coincidence but to happen to many players in same day makes u wonder... Anyhow be carefull what u type in and check it triple times cause it is really our own fault somehow I agree it is on us to confirm bet before betting but they won’t acknowledge the fact that they changed how it works and it is affecting many people. Also a decimal inputted should not result in the value of 0 this is a mistake they need to correct.
Selsleed Posted February 1, 2023 #8 Posted February 1, 2023 Hold on! I think that I was using ".xx" also and it was considered as "0.xx" a while ago! Is it some kind of a new change or smthing?
Cuhbert Posted February 1, 2023 Author #9 Posted February 1, 2023 12 minutes ago, Selsleed said: Hold on! I think that I was using ".xx" also and it was considered as "0.xx" a while ago! Is it some kind of a new change or smthing? Yes they changed it
Fimo Posted February 1, 2023 #10 Posted February 1, 2023 i got that same bug today homie, feelsbadman
Cuhbert Posted February 1, 2023 Author #11 Posted February 1, 2023 Just now, Fimo said: i got that same bug today homie, feelsbadman Yup
Featured Comment
Archived
This topic is now archived and is closed to further replies.