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

[Ahiro]

Well for the program, it won't identify it if you don't want. But the programm can missread something or you can have a lag spike during the programm is running which can cause a missclik (the identify) and a second one (which replace your weapon for example) to sold it after...

[Kalimanbb]

Can you tell me where i can dl Windows iso plz? (I only got a VMWare with Linux )

I dont know if its ok to give address but I usually download movies apps etc from warez-bb.org
You will find latest vmware windows 7 etc there.

[Kalimanbb]

Well for the program, it won't identify it if you don't want. But the programm can missread something or you can have a lag spike during the programm is running which can cause a missclik (the identify) and a second one (which replace your weapon for example) to sold it after...

Where do you change to NOT to identify rares? I dont want them stashed nor identified.

[belowme81]

Where do you change to NOT to identify rares? I dont want them stashed nor identified.

You don't. Just stash them ID'd.

[Ahiro]

You don't. Just stash them ID'd.

Of course we can! Look at notAres script 1.9.2, there are 2 variables called $StashLoot and $VendorLoot, put them to False and it wont (one more time : it wont for the program but it can missclick or something else which can cause the prob).
For the identify problem, i think it's line 287, just delete line Call("Identify") (not sure about the line number)

[internalcumbustion]

You don't. Just stash them ID'd.

ID'ing to me seems to be the problem. When it right clicks an item, if for instance it is already ID'd or a blue that it thinks is a rare, the bot equips it when it does the right click. I have seen it do it in an older version to my shield. That was what helped make up my mind to just farm gold and not bother with the other stuff.

[belowme81]

Of course we can! Look at notAres script 1.9.2, there are 2 variables called $StashLoot and $VendorLoot, put them to False and it wont (one more time : it wont for the program but it can missclick or something else which can cause the prob).
For the identify problem, i think it's line 287, just delete line Call("Identify") (not sure about the line number)

hmm I didn't see it as a variable so I didn't see Identify as an option. Wasn't looking for it in the code structure though. Stashing / Vendor is in there, I just missed the Identify.

[cw30000]

Sorry to hear that.

I think the best solution, for me anyway is not to ID them and stash them all.

[xlifer]

not sure why, but script isnt updating after i changed some values (such as vendoring,scripting,stash/vendor #) ??

[Fgega]

Can someone help me creating a $var to close the game and stop the macro after X runs?

sometimes i have to go afk for 10hours (let say)and i don't want do goldfarm all this time, so if i can add a function to stop the macro after X runs, or X minutes would be nice!



__
about the name of the script windows, it was randomized so warden can't detect the name...

I Also changed the AutoIT3_x64.exe name to "blabla.exe"

[loofer]

Argh, I can never get this thing to run for more than like 2 hours maximum. Diablo always crashes and gives an error for some reason. This never happens any other time but if I run this then go to work or sleep it runs for about two hours and after that I get some kind of stupid error message and Diablo shuts down.

[Soulcorrupt]

Hello,

First of all I'd like to thank both Mackus and notAres for this sweet script. Mackus for making it and notAres on improvising on it incredibly.

I have a small issue I am running into. Since 1.9.1 sometimes after resuming game and before discovering that I am in Old Ruins the bot/script assumes that the run is over and starts to teleport back to town and leave game or just leave game right there (Status - Returning back to town).

While the first scenario isn't all that bad other than skipping a run, the second one takes 10 seconds and I end up dying pretty easy coz it takes 10 seconds to leave game. It may not be a major issue now but once 1.0.3 patch is released and repair bills go high this is gonna hurt.

So I tried to add more sleep time before it check for old ruins. Increased it from 200 to 2000 and even upto 40000 but it din't help. It would still go to Status - "Returning back to town", before even entering the game. I assume this is probably coz of my latency and/or slow loading time.

This is where I made changes:

;Make sure we are in the right area before beginning run
If CheckFor("OldRuins", "Area", 1500 * $x_ratio, 0 * $y_ratio, 1920 * $x_ratio, 80 * $y_ratio, 6, 120) Then
Sleep(200)
GUICtrlSetData($lblLocation, "Location: Old Ruins")
Call("CheckRepair")
;Start Run



Would appreciate if someone could help me out with this.

Thanks in advance.

[Angrycoder]

How do you get it to not mess up when your stash is full or do you not stash items? What about Yellows? My problem is it ran flawless for 8 hours but then stopped because the stash was full

The GUI random thing is so I think Warden cannot detect window titles?

I have it set to stash legendarys and sets. I dont pick up yellows (too many problems with stashing / selling / id'ing) etc. Its just not worth the hassle to grab yellow items if you are gonna run the bot for an extended period of time.

When patch hits, (if this place isnt nerfed), and good yellows have a chance to drop, i will just stash yellows unidentified. Ofcourse you wont be able to go longer than ~8 hours.

[Dellymoar]

Hey guys, I can't seem to get this to work. When I click "=" the mouse moves a bit down and does nothing else after. Could someone help me out?

[internalcumbustion]

Argh, I can never get this thing to run for more than like 2 hours maximum. Diablo always crashes and gives an error for some reason. This never happens any other time but if I run this then go to work or sleep it runs for about two hours and after that I get some kind of stupid error message and Diablo shuts down.

I was having problems and I turned on the random sleep feature and last night it ran 100%. It seems to me if it runs too fast that you can sometimes lose communication with the server. The random sleep feature lets it sleep for about 4-5 seconds after looting around every 10 runs or so. I am excited to get home tonight and see if it is still going strong.