[Goldfarming] AFK 150k-200k Gold Per Hour [AutoIT Script] [1920x1080] [made for DH]

[Vulkii]

I have the problem that if the Cellar is closed, and I want to port back Mobs get at Me and kill Me.
I still logout but then it clicks Esc for whatever reason again and then Its trying to close Diablo.
I only made 300k with 260% GF this Night, just cause of that. Fast help would be nice^^

[wittekop]

Hi

First of all, thanks for all your work on this project.
I've been trying to edit the script in the very first post to make it work for my wizard. So far i got him to teleport and walk the last few steps to towards the cellar door, but then i get the problem detecting wether the door is open or not. I've been testing with many different color codes (I hovered my mouse over the door so it lights up, then took a screenshot, pasted it in paint and used autoIT window info to pick a pixel from the glowing light and use the given color code.)
With all the different color codes i tested it either detects the door to always be open (even when it's not) or always be closed (even when it's open..). I also reduced the area in which the program looks for the certain pixel so that it looks only in the area of the door. Keeps giving the same problem. Anyone know a solution for this ? or am i just running into a very long streak of bad luck and have to keep trying different color codes / reducing the area where the program looks for the pixel?

Also i'm confused about the Possibility of the warden detecting the script. Does it matter if i run the same script with the exact same mouseclick positions over and over again or not ? Or should i put some randomiser in this ? Because if i use a randomiser, the position of my char would change in relation to the cellar door and that could make the open/closed detection even worse... or is like a 3-5 pixel random difference enough for it not to be detectable ? that might be manageable imo.

thanks for your time


edit : I have 0 programming skills and just some minor editing experience from the old diablo 2 mmbot configs, but i think i understand what everything in the script does so far. I haven't looked at other people's scripts to keep me from getting confused / adding too much to my edited version.

[internalcumbustion]

I think this would be very, very difficult to detect since I personally don't believe they can track positions of click on screen. What I do though is compile the script into an exe and run that. If you run the script in it's au3 form it uses the autoit binaries to execute it and they may be looking for those loaded in memory. The exe is a file that just runs on it's own without having to have the autoit binaries installed on a machine. If you look at it like this everyone's exe is going to have a different checksum and exe name so all they might see is run.exe loaded in memory with nothing injected into the game session.

As with anything like this you are taking a chance running it and only Blizzard knows what they are really looking for. So don't bot on anything you can't afford to lose.

[jeffhakase]

is it possible to set the bot to pick up flawless square and square gems as well? it takes roughly 700 flawless square to make the highest quality, might as well make use of it here hehe

[fukker]

@ mackus101,
I ran your script at night and when i woke up it was just sitting dead in the cellar

@ notAres

i dont know why but if i die in the cellar sometimes it doesnt leave and tries to click on the lantern because red and yellow mixes and becomes orange so prolly looking for a legendary here's a screenshot

[CavedIn]

Repost from Blizzhackers:

I don't think a lot of people really understand what this autoit script is doing. From my limited, non-coder perspective, it is only doing the following: Timing a pause, moving a mouse to a specific grid location on your screen, and looking for a particular color. That's it.

Things like switching out pieces of gear, avoiding(or fighting) random mobs on the path there... These ideas are great, but they're really advanced, and would take a lot of time to set up, if they were even possible to set up.

Tweak what you can on the script. Even if you aren't a coder, if you managed to get it running, chances are you can figure out what to change to make it the way you want it to be. I know I managed it, and I'm nothing special.

[kallellkryptonite]

Haha, 'morning to you too fukker.

Seemed to run well most of the night. ~240k/hr +11 rares, 4 blues picked up.

Using notAres' script from ~9pm EST last night.

What kind of gear are you in>?

[kjsd33]

Decided to post my version of the script public in case anyone is interested in trying it. I appreciate both Mackus and notAres for posting their's, however Mackus' is fairly slow and I didn't have much luck with the features of Are's.

NOTE: If you don't include all the movespeed buffs I use, the move timers are going to be all screwed up. Adjust load timers as needed but I do not recommend lowering the leave timer below 12 seconds unless your character can survive the hits from the mobs easily.

Setup:

Mouse1: Mark of Death
Mouse 2: Elementral Arrow - Ball Lightning
1: Caltops: Torturous Ground
2: Smokescreen: Lingering
3: Prep
4: Companion: Ferrets

Boots: 10% or higher move speed
Pickup Radius: +5m
Passives: Hot Pursuit and Tactical Advantage, other is optional.

Changes:
*SOMEWHAT IMPORTANT: I changed to ball lightning (so I recommend against nether tentacles) and made the script fire to the right slightly longer than it needs to in order to destroy the desk that spawns there. I found that the desk and chair were causing pathing issues for the ferrets and I would miss sometimes 1000+ stacks of gold lying on the ground because my ferrets couldnt get there. I would suggest adjusting your "fire right" timer as needed so that you fire at least 1 more ball to right than is necessary to destroy that desk.
*I changed the first waypoint slightly to avoid monsters much more often and get stuck less
*Most wait timers are generally shortened. I retained the "greater than death" leave game timer. I tried Ares' code for death detection but I found that sometimes it wouldn't work properly and the script would get jacked up.
*I changed repairs to occur every 10th game instead of on detection. In the long run this amounts to very little time, but I had found occasionally that the pixel detection would malfunction and my script would loop indefinitely with no gear.
*I implemented rare/legendary/set detection. Once again I tried Ares' but I think the default pixel detection just wouldn't work on my PC. I'm sure Ares' works, but on my PC I watched it completely ignore a legendary lying on the ground and move on.
*I changed the rune on caltrops, and changed it so you drop one around yourself as you TP. This seemed to reduce my deaths while townportaling significantly.
*I slightly modified the smokescreen times to avoid dying just before entering the cellar just in case a mob spawned right there.
*I modified the pick up pathing to be shorter and more natural.

Mackus' Gold Farm [Mod: Jakesmurf] - Pastebin.com

Nice script, works good. The only issue I'm having with it is that it keeps accidentally picking up blue items after sarkoth dies when it runs along it's path, as a result if the inventory gets full it wont have space for potential rares/legendaries.

[fukker]

yo zubiq, did u change Calibrate Gamma or using default ?

[wittekop]

I think this would be very, very difficult to detect since I personally don't believe they can track positions of click on screen. What I do though is compile the script into an exe and run that. If you run the script in it's au3 form it uses the autoit binaries to execute it and they may be looking for those loaded in memory. The exe is a file that just runs on it's own without having to have the autoit binaries installed on a machine. If you look at it like this everyone's exe is going to have a different checksum and exe name so all they might see is run.exe loaded in memory with nothing injected into the game session.

As with anything like this you are taking a chance running it and only Blizzard knows what they are really looking for. So don't bot on anything you can't afford to lose.

thanks for this info, very helpful

Question to anyone : When the program is looking for "the blue pixel" does it look during the sleep period defined after the move mouse command to hover above the door ? or only at the exact moment at the time the command is given ? Since the light shimmers and slightly changes color over time, creating the glowing/waving effect. This could make the program miss the blue pixel since the color code might not be on the screen at the time the program looks for the pixel.

[zubiq]

yo zubiq, did u change Calibrate Gamma or using default ?

Default in fullscreen windowed mode.

[fukker]

Default in fullscreen windowed mode.

i ran it like 50 times in FULLSCREEN mode also works

[[Soul Eater]]

Got a problem with this script, every time I run it all it does is clicking some random points and then press T > ESC > Leave game, then it resumes the game and rinse and repeat. Anyone knows the solution to this?

[tochybaja]

Got a problem with this script, every time I run it all it does is clicking some random points and then press T > ESC > Leave game, then it resumes the game and rinse and repeat. Anyone knows the solution to this?

Same problem here

[kjsd33]

I ask that folks keep in mind that these are AutoIt scripts - and while they CAN become very advanced, they are essentially working with very basic tools. It is very likely that some of you are going to have to tweak these scripts for yourself and that they will not work out of the box. I have especially noticed this with the pixelsearch functions, and I would assume this is because your PC is interpreting the colors differently.

Also keep in mind that these scripts are running using only two parameters to guide them - Time elapsed, and occasionally - What Color is This Spot? Those are two very primitive data pieces and nobody can guarantee you an error free script. You are going to, occasionally, TP out when the cellar is open and ignore it, or miss a rare, or something to that effect.

If you have problems with pixel detection, I may not be able to help you. I would suggest taking a screen shot of whatever it is you're trying to detect (Highlighted Cellar Door, Rare on Ground, Legendary On Ground, Set Item on Ground etc) and use a program that will pick the hex color code for you for the pixels from there. This is the only way to make sure that my PC and your PC don't render the color a little differently and thus throw off the entire search.

------------------------------------------------------------------------------------------------------------

As for picking up magic items in my script - The FindItems() func isn't doing this intelligently, its just accidentally clicking on them sometimes when they happen to be where the bot wants to go. I may try to find better coordinates for avoiding this at some point but thats not very high on my priorities right now. At the moment, I'm working on modifying the script to remove blues from your inventory to make room for rares and above when it finds them - but I wouldn't expect to see that tonight or expect it to be intelligent about how it accomplishes this.

-------------------------------------------------------------------------------------------------------------

The number at the end of this pixelsearch string indicates how sensitive the search is. Generally, if you don't keep this at least mildly low, you're gonna false alarm a lot. Try tweaking it if you're having color detect problems.

Sounds good, thanks for the info. With your script I'm making a little over 300k/hr.