You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've used this bot nearly 24/7 for months without issue, but as of January 31st at around 10pm, the bot stopped making predictions or placing bets.
Watching the F12 Console while it runs, it seems to still be recording match data AFTER each fight, but it makes no predictions prior to the fight, and afterwards will always say "Predicted Incorrectly" in the match results Prediction field, regardless of who wins.
I have no idea what changed. The browser did not crash, and to my knowledge no updates were installed, it was just like a switch was flipped. Despite restarting my browser, then my entire computer, the issue hasn't changed.
The text was updated successfully, but these errors were encountered:
I don't believe this to be a duplicate issue, I believe this is different. When my machine runs slowly, as #481 describes, the predictions still appear in the console, they just don't get typed before betting closes, and the Match Results still record whether or not the prediction was correct.
That isn't what's happening here. Here, the bot isn't even making predictions, hence why 100% of Match Results say "Predicted Incorrectly." The bot isn't running slowly, it's skipping steps entirely.
I would appreciate if we could re-open this issue.
I've used this bot nearly 24/7 for months without issue, but as of January 31st at around 10pm, the bot stopped making predictions or placing bets.
Watching the F12 Console while it runs, it seems to still be recording match data AFTER each fight, but it makes no predictions prior to the fight, and afterwards will always say "Predicted Incorrectly" in the match results Prediction field, regardless of who wins.
I have no idea what changed. The browser did not crash, and to my knowledge no updates were installed, it was just like a switch was flipped. Despite restarting my browser, then my entire computer, the issue hasn't changed.
The text was updated successfully, but these errors were encountered: