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
For now it seems to be working, browser runs the stream and bot detects progress.
While this might not be working headless, it could be a way to keep using the bot with visible/active chrome. In my case it is on a small linux VM.
Maybe this could be implemented as an option to provide the Port (9222 in my case) in the config and the bot getting the ws url from the json endpoint.
The text was updated successfully, but these errors were encountered:
After a long time i got back to farming drops.
As claiming drops with this bot is broken, i was using the twitch autoclaim addon for chrome. But that still requires to have a proper stream open.
I just tested to start my already working (logged in + auto claim via extension) chrome and let the watching be controlled by your bot.
Here is how i did it:
--remote-debugging-port=9222
http://127.0.0.1:9222/json/version
webSocketDebuggerUrl
puppeteer.launch
withpuppeteer.connect
(see below)For now it seems to be working, browser runs the stream and bot detects progress.
While this might not be working headless, it could be a way to keep using the bot with visible/active chrome. In my case it is on a small linux VM.
Maybe this could be implemented as an option to provide the Port (
9222
in my case) in the config and the bot getting the ws url from the json endpoint.The text was updated successfully, but these errors were encountered: