-
Notifications
You must be signed in to change notification settings - Fork 126
New error on 1.3.3 when watching stream #20
Comments
Just tried to watch the same ch and works fine for me.
|
It does it on every stream for me, and the drop is currently 50% on my drops page and it currently works fine in the old version. It takes about 2-4 minutes to get the error. Sykunno is only one with out a complete drop i have online currently. I have tried Cyr whos drop I have completed and same issue as below : I will try and a complete fresh start instead of using my old settings. |
Use the npm version and go into src/Pages and open Watchingpage.js and change in line 23 Also maybe restart ur pc this could fix the page not properly loading |
Basicly the Bot doesnt find and active drops on https://www.twitch.tv/drops/inventory |
Hm weird if u dont mind adding some code for debbuging you can go to src/functions and open mapdrops.js and add in line 75 just before |
Is it supposed to print the log into the cmd? as it didnt print anything. So if so its either not getting that far or I done it wrong. My code is `
` |
Open mapdrops.js and take the code from here https://pastebin.com/d4H1QmEX and replaced it just to ctrl +a and replace it with everything frome pastebin. This should log it in the cmd |
Ah okay found the issue its the nmplol chestplate it has 2 streamers linked to it and the bot doesnt know it has to look out for drops with two links to watch... |
Ah yes. Page attached. |
Hm i think the twitch folder is missing in ur download, usally chrome saves pages as twitch.html + "html name" files folder |
Ah yes, I downloaded to a larger folder so didnt notice the folder. Here is full archive. |
Hm okay seems that the twitch page cant be saved... Can you follow the steps like here https://streamable.com/a4qbxp and then take a screen of whats shown on the right. Would help a lot. Sry that i have to ask you to do it all but cant recreate the error cause can't get the drop because its offline sadly.... |
Oh and click on the nmplol twitch thing not like i did cyr |
The below should be it
|
okay try this https://pastebin.com/sqUnah3J in mapdrops.js. this should fix it. let me know if it does fix it |
Thanks, Fixed it! However I am now hitting Issue #21 lol. There appears to be an issue with it thinking Sykkunos drop is complete. |
Hm can u add |
Can u tell me if the |
The false trues are : Ludwig My claimed drops are : Trainwrecks Correct Falses : xQcOW Ludwig and Sykkunno I have previous drops for, but I am not sure if thats the issue as, I also have another Rust drop for xQcOW |
Trying to recreate the error formyself but even after setting everything as u have it i dont get all live channels claimed....
|
Output is as below : `Watching https://www.twitch.tv/Sykkuno... [ All live Channels claimed...` |
Okay finally recreated the error the bot acutally thinks that xQc Assault Rifle is Sykkuno Assault Rifle because its so similar, will have to fix it tomorrow as it already 4 a.m. For now use one of those fixes:
|
So for some reason when there is only live channels for ones I have the drops for, it still seems to want to wait for 3 trys. It then seems to hang waiting for a new stream. As below screenshot. Ludwig is now online and it hasn't picked it up. It has not changed for over an hour. Potentially Ludwigs was still false flagged as true though. I double checked and he had only been on rust for 26 minutes, so potentially I also did not wait long enough. However after a restart it now waits for about 20 mins then gets this error, Ludwig is currently the only live streamer so this is potentially related to the 1 streamer online issue again. The error looks identical.
|
I left it on overnight, and it got the NMP drop just fine. So I think the Ludwig one may have been a fluke due to it only being live 26 mins? not sure. The one stream bug still seems to be present but not 100% though which is strange. As when it was just Ludwig I got the above error. But now its just Nmp its working fine as below : |
Not quite sure if it is fixed in 1.3.3.1, would be nice if you could check on it. Added a Check if only one ch is live and it is already claimed/100% it will try to look every 10 mins for a new ch and it will loop thorugh the one ch which is live every 10 mins in this case nmplol because he was the only one live, im not quite sure wy it didn't watch ludwig after it was show as live have to look further into this bug |
Me and friend using the new version now. Will let you know if the issue reoccurs. Only Cyr streaming currently so good time to test. The new chrome detect feature worked to find my .exe and the program accepted my profile path now too. |
Not active anymore, if this still occurs you can reopen this issue. |
Firstly thanks and great work getting the issues fixed so quickly.
However currently 1.3.3 seems to be broken for me at least. Once you choose the channel to watch it gets below error, I have tried the npm and .exe compiled versions and they both do the same thing :
Setting Video Settings like Quality and Volume...
Watching https://www.twitch.tv/Sykkuno...
(node:35920) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read property 'startsWith' of undefined
at :57:33
at Array.filter ()
at :56:39
at ExecutionContext._evaluateInternal (S:\RustDropBot\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:218:19)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async ExecutionContext.evaluate (S:\RustDropBot\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:107:16)
at async MapDrops (S:\RustDropBot\src\functions\MapDrops.js:89:5)
at async CheckProgressCurrentPage (S:\RustDropBot\src\Checks\CheckProgressCurrentPage.js:14:5)
at async S:\RustDropBot\src\Pages\StreamPage.js:68:9
at async CurrentProgressEvent (S:\RustDropBot\src\Pages\StreamPage.js:66:5)
at async StreamPage (S:\RustDropBot\src\Pages\StreamPage.js:54:5)
at async intrust (S:\RustDropBot\src\Pages\WatchingPage.js:79:13)
(Use
TTVDropBot --trace-warnings ...
to show where the warning was created)(node:35920) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)(node:35920) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The text was updated successfully, but these errors were encountered: