There is not enough sleep between two bet. This is a performance issue and could be improved.

getting this error when betting is found.

When using a ctrl+c the program is badly ended without any clean. Checking for KeyboardInterrupt can patch this issue.

Log every data into a well-formed CSV, this allows us to analyse data and find the best bet strategy for each stream.

A debug file is always created and I don't know why. It have something to do with Windows and ChromeDriver.

Every time a chest is collected print a message with the new balance.

This can improve output spamming, and data analysis

Not one strategy work for every stream, so starting the script with the bet strategy within a config file or just as input would be really helpful.

In other language than english - for example in Polish i received ValueError when i collect more than 1000 coins, because Twitch always shorten '1000' for '1tys' in my language.

and screenshoot from Twitch:

maybe could you collect 'skulls' value instead of discovered value

"Current status" target sometime the good status in the user menu, but sometimes a random twitch name.

Project renamed to : TwitchAutoCollect-AutoBet, need to update the readme.

"cote" is odds in French and need to be replaced

How to fix it?

In the bet placing method, the slip take too much time so the order can't be made.

In other language than english - for example in Polish i received ValueError when i collect more than 1000 coins, because Twitch always shorten '1000' for '1tys' in my language.

and screenshoot from Twitch:

maybe could you collect 'skulls' value instead of discovered value

Add a GIF to improve the project description, this will help to have a good demonstration and proof of work.

Starting the script with the stream name in param make it easier to run it on multiple streams.

When the stream is down it shouldn't bet checking for bet or chest.

By using the TWITCH API, a waiting feature can be patched and work 24h/24h.

Add a bet win/lose capture with point Update

Currently we aren't checking if a bet is won or lost, we are just printing the score. Even if there is a function for this, it needs to be tested and improved to post a message when a bet is lost or won