[Goldfarming] notAres' Sarkoth DH Gold Script [AutoIT Script] [1920x1080]

[notAres]

Sorry, PMs cleared

[SpyOrbit]

I don't think the script makes a difference, its the time taken between each quest and starting new ones that is determining if your input limit is reached.

[fukker]

I don't think the script makes a difference, its the time taken between each quest and starting new ones that is determining if your input limit is reached.

well i have no problems

[robble]

I'm getting the the input limit error with the script as well. US server.

[pigjai]

can i get it with donate gold???????

[SpyOrbit]

The script isn't working, I've tried several versions, unless this is a "server issue" and random people are getting it, this has been fixed via patch from Blizzard. However, I cant see why they would do this when you can manually farm this same spot faster if you did the input yourself. Either way, highly annoying.

[cyboirette]

I would like to know how many times we can redo the quest per hour, and how long a cellar run with the door closed last.

Anyone wanna test this?

[fukker]

I would like to know how many times we can redo the quest per hour, and how long a cellar run with the door closed last.

Anyone wanna test this?

well now i start to think its Server issue why because i used one version was getting msg every 3 runs then i used another version for over an hour with different sleep times but now i started to get msg after each cellar so **** knows what is happening

[Shimizoki]

well now i start to think its Server issue why because i used one version was getting msg every 3 runs then i used another version for over an hour with different sleep times but now i started to get msg after each cellar so **** knows what is happening

I just dont know anymore... I can reliably reproduce it, its consistent. I can do several runs with no issues, then I get the error every run from that point forward. I can then wait 10 minutes and run several times again before I get the error... I dont have any idea whats going on. I'm kinda flipflopping on thoughts. Either its working as intended to stop rapid farming, or its a bug... Either way its hurting both botters and legitimate players.

[fukker]

I just dont know anymore... I can reliably reproduce it, its consistent. I can do several runs with no issues, then I get the error every run from that point forward. I can then wait 10 minutes and run several times again before I get the error... I dont have any idea whats going on. I'm kinda flipflopping on thoughts. Either its working as intended to stop rapid farming, or its a bug... Either way its hurting us.

well its not even that that annoys me, its this:

1. you logout to go to AH
2. you resume to whatever u bought to pick up from stash
3. you logout to your friends game to give him something
4. you logout from his game to resume your game and u get that msg ; \
5. lol

[Angrycoder]

I did 42 runs straight, with my script. Average time per game = 46 seconds. Never got the lockout. Im sure its just a server load issue.

[Shimizoki]

Well this is lame, I had a thought of how to implement random pathing.... but I cant test it when I keep getting this error.

[Brigantaggior]

I have a trouble.. (I've used it for 2 days)
Now it does not work at all. Both versions (the new one and the old one, with pixelsearch instead of imagesearch)

It tries to click at a white circle instead of resume button.. and other clicks are wrong too

How can I fix it?



P.S. I did not change my resolution settings, game settings etc

[Goldfox420]

Is it just me or does this not even come close to clicking the cellar anymore?

I am running the newly patched US server. 1920x1080, Fullscreen Windowed, no other problems ever,

Did they move the location of the cellar with the new patch? I have copied and pasted the script a few times now with no results and I even manually added the click for the cellar and the bot hovered over it saw it said dank cellar and still left the game.

[greenxeyezz]

moving the cellar a few pixels is NOT a fix they would waste their time on, simply adding maybe another move command or changing where it looks would fix that issue, a 30 second fix. it would be stupid for blizzard to do that. Implementing xlogs/hour or something like that would fix EVERY botting issue.