worked fine for me till yesterday I'm using same script i used 3 days ago but now ill run it and come back hours later to find diablo 3 closed ill open diablo 3 and log my character to find one gem in my inventory and that's all.
worked fine for me till yesterday I'm using same script i used 3 days ago but now ill run it and come back hours later to find diablo 3 closed ill open diablo 3 and log my character to find one gem in my inventory and that's all.
Dropped 11 leg (3 set) in 6-8 hours
Still works really well
Hello GG-Bots,
Is it possible to implant a sell system 4 blue and yellow items ? I think its better and easy solution to sell the blue items then search how to slove the massive Blue item pickup problem.
Making it sell blues/rares would be a big waste of time, it doesn't gain you anything and will make the run take longer.
I've decided to just take out the picking up of gems which should in return make it stop picking up as many blues/rares if any at all.. (If you want to continue picking up gems, I've only commented out that part of the loot function. Just uncomment them to fix it.)
UPDATED: First post download links have been updated, try that!
Last edited by GG-Bots; 05-01-2014 at 07:20 AM.
One more add from me:
Select the character you want to run with, enter game
Unequip every item except boots (or whatever gives you movspeed) + get movespeed from paragon
Set "auto equip new items" or something like that
You get +8-10 slot for "blues", this should be more than enough to last for 12 hours+
Ran into this issue this morning (or at least that's when I first noticed it). There seems to be something going on that confuses the bot when checking the first chest when it is not there that will cause it to miss the second chest. I watched this happen 3 times in a span of 10-12 minutes.
This happened with the most recent version of the bot and the previous version that I modified to take out gem pickup.
Any ideas as to what is going on?
I ran into the same problem. It's a problem with the pixel color search. He used a color that appears on the chest as well as the environment on occasion. Which basically means, every game whether there is a chest or not on the top, the bot acts as though there is indeed one.
The Fix: Open up AutoIt3 Window Spy, and join a game till you find the first chest. Take a sample color from the chest. Place that sample color on line 232.
By default the value is AA9BAA, which works if you leave that value for Chest2, atleast for me it does. And for Chest1 I used the value D7CCE6 which works fine. Yours may vary depending on your video settings, which is why you'll need to use AutoIt3 Window Spy.Code:$Chest1 = PixelSearch(580, 219, 1342, 880, 0xD7CCE6, 2) ;Check for Chest
It seems that mine is also missing the second (bottom) chest. It recognizes the first one perfectly, when the first chest isn't there, it walks down halfway then teleports home.
Well It started working for me after i changed my desktop wall paper from a dark image to white. But still it skips the second chest occasionally.
I ran it for 6 hours I got 5 legs and no blue or yellows.
http://www.ownedcore.com/forums/diab...ml#post3040083 (Battlefields T6 Chest Run Bot)
It doesn't necessarily "skip" the second chest, it just thinks that the first chest is there a lot of the times, which it is in fact not. A simple change in the PixelSearch function within the script should fix that problem.
Last edited by jpitty; 05-01-2014 at 03:42 PM.
It seemed to work for a while but it still does it on occasion. I will keep testing from time to time and see if i can find that "sweet spot".
Out of curiosity, has anyone tried (or is anyone capable of) making the search terms for the chest based off more than one pixel? Maybe like sample color 1 within a given proximity to sample color 2.
Also, what's the longest you guys have let this run for?I ran for about 14 hours between last night and today. 9 hour session today after the maintenance net me 8 legends 4 of which were set items lol (IK helm, travelers and compass, and blackthorne pants).