Oh yeah he did. I missed that completely, sorry.
On JD in the alpha versions, the stop is deliberate. It sometimes happens that the bet is executed but gets stuck on the server or lost on in the internet somewhere. So the bot stops betting instead of retrying the bet for a very good reason. Imagine the following scenario. You Martingale with a base bet of 1 clam.
1:L
2:L
4:L
8:L
16:L
32:L
64:L
128:L
256:L
512:L
1024:L
2048:L
4096:W, but bet gets lost.
4096:L Bot Retries the last bet
8192:L
You Bust.
So while it is annoying, It is in the best interest of the user/player that the bot stops in this case.
It would be ideal to have the bet method return the bet result, but unfortunately, that's not how JD socket is set up, so while i can change the api to return the object, it would not be any more reliable than it already is. Instead, it would just complicate things in the api and slow it down as a whole.
the reset stats button is a bug in b10, it's been fixed in b11.
Starting a thread for the programmer mode has been suggested to me before. I have no intention of starting one myself, but feel free to do so yourself and post the link to it in this thread. I'll probably keep an eye on it.
I understand what you are saying about its better that the bot stops than to possibly double a bet or skip a win. Running the bot for just a day I can tell it's not really usable with JD currently, unless you are sitting there watching it and refreshing the page after every hang. I'm using the latest stable build, but if the alpha is better I will try it. What would be ideal, would be for the bot to automatically refresh JD if it hasn't received a response after X seconds, check the bets to match up the last, then continue. If you are worried about the delayed bet issue, you could mitigate that in two ways... have a minimum time to wait between placing a bet, waiting for response, then re-attempting. If you wait 30+ seconds, it would seem pretty safe to assume the previous bet did not go thru. Secondly, you could have a setting that does not re-attempt betting automatically above a threshold. I don't care if the bot doubles a .00001 clam bet by mistake if it means the bot will run and not wait for 4 hours until I get to my PC to see it stuck. But if its up to 50 clams, sure I don't mind waiting on me.
Hope that makes sense!
I agree with your frustration. I have yet to see a bet not go through. Every time I check the bot I can see it made a bet and is waiting for a response. When I check my bets on JD I can see the result of bet the bot is waiting on. For a straight martingale you might be able to just lose the bet, but for most of the stuff I'm playing around with I would rather get the correct info.
For myself it doesn't sound to difficult. I could imagine an API call to get result passing in a nonce. Then the bot could check and see if thats the one it's waiting for. Or a get last result call.
How easy it is to make suggestion when you don't know what the hell your talking about....
<-- that's directed at me...
I'm sure Seuntjie will figure it out.