Chest run bot

[Raizen1989]

this is from last night in more than 10 hours also woke up to a disconnect screen and i don't know the actual run time

[jinxderp]

Noticed the bot didn't pick up 2 legs. had to pause it and go pick them up. Had the same issue with GG bot. Can you offer something i can look at to fix?

[Raizen1989]

Noticed the bot didn't pick up 2 legs. had to pause it and go pick them up. Had the same issue with GG bot. Can you offer something i can look at to fix?

Are u sure u dont have any gamma correction ingame ir in your display driver settings ?

this problem is from your side not the bot side the bot doesn't recognize the color of the legendary item cause its not the default one like mine

[sillybearito]

I unequipped my fire walkers thinking they would interfere, I didn't realise I lost 12% move speed. Woke up this morning and the bot didn't pick up a single thing. It had also stopped responding at some point during the night. This seems to happen when I tinker with the delay timer. I'll run it more today with proper run speed.

[sillybearito]

Oh man this leg buff is nuts. Found 11 in 2 hours... I left delay off and haven't received the 42002 error. Bot is doing 2 runs per min very efficiently

[Raizen1989]

Oh man this leg buff is nuts. Found 11 in 2 hours... I left delay off and haven't received the 42002 error. Bot is doing 2 runs per min very efficiently

to be honest i dont think the came creation limit is calculated at an hour cause everywhere i searched it was like "games created in an amount of time " so you will probably get the error eventualy

[straaand]

to be honest i dont think the came creation limit is calculated at an hour cause everywhere i searched it was like "games created in an amount of time " so you will probably get the error eventualy

this is the biggest and most annoying problem, cant you configure the bot to idle in menu for 10 minutes like every 45 min or somethhing like that?

can be worth a try.

[straaand]

or could you make the bot check for the 42002? error every run and if it detects it it will wait 20 min and try again?

[Raizen1989]

or could you make the bot check for the 42002? error every run and if it detects it it will wait 20 min and try again?

Or you could use the delay buttons and put in enough delay so that you never get the error we already established that the error is trigered somewhere between 40 and 60 seconds per run .

[hUi33]

cannot even run it for more than 30mins b4 its stuck at the resume button.

[jinxderp]

Are u sure u dont have any gamma correction ingame ir in your display driver settings ?

this problem is from your side not the bot side the bot doesn't recognize the color of the legendary item cause its not the default one like mine

100% sure. I woke up with 2 legs after running the bot for about 8 hrs..

[Raizen1989]

cannot even run it for more than 30mins b4 its stuck at the resume button.

I will fix it with next upgrade I know what the problem is

[Raizen1989]

100% sure. I woke up with 2 legs after running the bot for about 8 hrs..

Was the bot still running ? Or was it stuck ?

[jinxderp]

Bot was still running but didnt pick anything up. Closed it out started it again and ran for another 3 and nothing. Going to switch to over to my main pc tonight and try that. I had the same issue with the other bot and i tried everything to fix it. Just dont know.

[Raizen1989]

Bot was still running but didnt pick anything up. Closed it out started it again and ran for another 3 and nothing. Going to switch to over to my main pc tonight and try that. I had the same issue with the other bot and i tried everything to fix it. Just dont know.

Well the oroblem seems to be that pixel search doesnt work right for you some other people have the same problem it seems the colors that the bot searches are just diferent or else I can't imagine why the bot picked my legendary items and yours not this must be a matter of settings : gamma corection , RGB distribution , brightness and so on . If the shade is slightly off the bot wont read it , if I let to much room for error the bot will read it everywhere that is how it is .