Quote from: dooglus on November 21, 2016, 06:22:03 AM

Quote from: seuntjie on November 17, 2016, 07:24:58 AM

It's possible he's using dicebot and the bot failed to connect for some reason and tried to unsuccessfully reconnect a few times, or he might have written his own bot or used another bot that runs on jdcapi (like tigers bot) that handles disconnects/reconnects incorrectly or tries to log into a whole bunch of accounts too quickly.

I just had another player complaining that the bot had lost all his balance, and that the same numbers were being rolled several times. Turns out the bot is showing the same bet multiple times:

Not sure what's going wrong, but it also seems to be skipping some bet sizes, and resetting on loss sometimes. Maybe it's user error, but it's odd how the same bet shows up multiple times.

It looks like there's an error in JDCAPIs reconnection logic. It seems like the socket gets a disconnect message or experiences an error, so the bot tries to reconnect, but the socket stays connected. Meaning a bet is placed via the newest socket but the messages are received from both sockets, so the bet is shown twice in the bot. This will cause issues (as shown in the screenshot above). This is a very recent issue

I'd suggest people avoid using dicebot on JD until I get this fixed.