Battlefields T6 Chest Run Bot

[jpitty]

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).

You would add *N* variation to the PixelSearch function. It's a number between 0-255. For example, if you have the line:

$Chest1 = PixelSearch(580, 219, 1342, 880, 0xD7CCE6, 2) ;Check for Chest

The 2 represents your variation. So in this case the PixelSearch will find the color D7CCE6, and 2 shades of variation. You could try increasing this number and see if that works better for you.

[EverRage]

Thanks! I'll try that.

[pinkpanther]

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).

Hi, one of the reason the bot make mistake is the 'storm thing in the map' there is like snow particle moving that can mess with the color pixel.
The other is performance, MS but I think u dont have issue with this.

For me if it still around 10% mistake it still acceptable since this is not like checking the actual chest but only the color, I still got 1++ leg per hr anyway.

Btw got about 12Leg including 1very usefull set class and 3useless set i dont need to mention, [10 hr run]

[SATANourSAVIOR]

This is excellent.
Works like charm.
Thank you!

[Namesuxx]

Maybe im wrong but it seems fixed on EU, running 6,5 hours and no leg. q6 MF 101.

[Fulkol]

Maybe im wrong but it seems fixed on EU, running 6,5 hours and no leg. q6 MF 101.

It's not fixed
Just "harvested" this from 8+12 hours of running (stashed once, identified at once)


btw
Mf doesn't count when farming chests

[munkki666]

YUP, its NOT fixed. Just got 14legs last nigth.(~9h)

[alastor2262]

Hi, one of the reason the bot make mistake is the 'storm thing in the map' there is like snow particle moving that can mess with the color pixel.
The other is performance, MS but I think u dont have issue with this.

For me if it still around 10% mistake it still acceptable since this is not like checking the actual chest but only the color, I still got 1++ leg per hr anyway.

Btw got about 12Leg including 1very usefull set class and 3useless set i dont need to mention, [10 hr run]

for me there was 2 reason why I was missing the first chest in about 10% of the case
first was the pixel in the center of the screen that appear sometimes( I reduce size of the searchbox to the right)
and second was when the chest is in the top most position (I increase size of the searchbox to the top)

by changing slightly the size of the box I solve all of these case as far as I can tell.
here is my parameter for chest1 :

$Chest1 = PixelSearch(380, 159, 1142, 880, 0xAA9BAA, 2) ;Check for Chest

[Robman]

Seems for me chests r dropping less loot

[DecardCain]

4 Hours, 1 set 5 legs.

[Pommimies]

you should add to all teleportations a pixel recognize so the bot wouldn't do teleportations while in loading screen.

[tangerines]

I only started running this last night with good results. But now I am being disrupted with Error 42002 which does not allow the bot the automatically resume game after exiting right away - so the bot stops working. Any advice? Should I stop as Blizzard might have found a pattern with my botting?

[qoodoo]

Man I dunno...I must have terrible RNG the last day. Last night I let it run for 5 hours and I woke up to 3 legs. Today after going out during the afternoon I came back after another 4 hours and I only had 2 legs. I'm gonna see what happens tonight.

Seriously the first few nights I ran this in 5 hours I had 10 or so legs each time.

[womd]

I was having issues with the bot not finding second chest as well and figured it was rng with the snow or some other variance so i did a messy workaround that seems to be working

$Chest2 = PixelSearch(580, 219, 1342, 880, 0xAA9BAA, 2) ;Check for Chest
	If Not @error Then
		MouseClick("left", $Chest2[0], $Chest2[1] + 24, 2, 1) ;Looting Chest
		Sleep(Random(2200, 2400, 1))
		Loot()
		Sleep(Random(400, 600, 1))
		Send("{B DOWN}")
		Sleep(Random(100, 120, 1))
		Send("{B UP}")
		Sleep(Random(7100, 7300, 1))
		Send("{ESC DOWN}")
		Sleep(Random(100, 120, 1))
		Send("{ESC UP}")
		Sleep(Random(1000, 1200, 1))
		MouseClick("left", 253, 479, 1, 0)
		Sleep(Random(6300, 6500, 1))

	ElseIf @error Then
			Sleep(Random)(200, 250, 1))
			PixelSearch(580, 219, 1342, 880, 0xAA9BAA, 2) ;Check for Chest again
	If Not @error Then
		MouseClick("left", $Chest2[0], $Chest2[1] + 24, 2, 1) ;Looting Chest
		Sleep(Random(2200, 2400, 1))
		Loot()
		Sleep(Random(400, 600, 1))
		Send("{B DOWN}")
		Sleep(Random(100, 120, 1))
		Send("{B UP}")
		Sleep(Random(7100, 7300, 1))
		Send("{ESC DOWN}")
		Sleep(Random(100, 120, 1))
		Send("{ESC UP}")
		Sleep(Random(1000, 1200, 1))
		MouseClick("left", 253, 479, 1, 0)
		Sleep(Random(6300, 6500, 1))

	ElseIf @error Then
		Send("{B DOWN}")
		Sleep(Random(100, 120, 1))
		Send("{B UP}")
		Sleep(Random(7100, 7300, 1))
		Send("{ESC DOWN}")
		Sleep(Random(100, 120, 1))
		Send("{ESC UP}")
		Sleep(Random(1000, 1200, 1))
		MouseClick("left", 253, 479, 1, 0)
		Sleep(Random(6300, 6500, 1))
	EndIf
	EndIf
	EndIf

I basically nested the pixel search in the if/else statement a second time with a small delay. more or less it will check twice now. idk if there is a more elegant way to do this, but from a couple runs it did not miss :P

[tangerines]

Can something help or direct me as to rescripting (increasing) the time delay for resuming game? I think I am creating too many games so blizzard has possibly flagged me for error 42002. Any help will be appreciated.