if i want to just pick up certain gems, is there a way to do that? thanks!
if i want to just pick up certain gems, is there a way to do that? thanks!
There is an issue with the script clicking the lamps in Sarks room. sometimes they match the color. odds are none dropped.
I swear this bot knows when i go to work. It will run fine all day for 6 hours. as soon as i leave the house it gets held up either "cant find resume button" (sitting in town) as of today or getting stuff on asking if i want to quit d3. I keep adding a few MS to w/e I think is causing the hold ups.
These advanced bot are so sick, but the oldest versions i could run for hours w/o issue
Last edited by qITIp; 06-17-2012 at 10:01 PM.
@notAres
Latest version I had 2 occurences where the mouse moves on the resume button but the script is still at "Opening Window" status. This gives the can't find resume button error on a loop since the image doesn't match anymore (resume button is lighted up, mouse over it, etc...) One way to fix this is to mousemove out before the mainmenu checkfor. Also it should be possible to limit the lootgear zone so it doesn't pickup the lamps but still picks everything that drops. Would probably remove fake legendaries.
Last edited by S|cK; 06-17-2012 at 10:16 PM.
Can you trade unidentified legendaries? If not, I need a lossless screenshot of one before and after identifying, so I can see why it's not stashing them (it's stashed multiple for me, of course)
Why do i keep getting random sleep times of 45 Seconds?
Last edited by JarellNewwin; 06-17-2012 at 10:34 PM.
It must have just been the lamp colour being detected as above. Do legendaries not get identified before stashing like rares?
;Variability ==NEW SETTINGS==
$Timer = "True" ;True and the bot will add random sleep intervals
Do you have that set to "False"
Found a set item while running for aout 3 hours. Very nice amount of features added to this.
hey notAres theres a way to shorten the attack time? doing overkill for a good couple seconds
mines always say set items but when i look theres nothing in inventory or stash. wierd?
So i double click Dh.au3 and the box comes up where it shows run time and found items and such.. I hit = and it takes a second and then the screen says it cannot find the RESUME button... Ive been running 1.3 without any problems and figured i would try the new one.. but i cant get it to work?
any ideas?
On the bot it says it cant find resume buttom.. i error my file to sat this..
$pngLoc = "C:\Diablo III\Pics\" ;Location of the .PNGs (NO SUBFOLDERS - ALL PNGS GO HERE)
and i also tried without the \
$pngLoc = "C:\Diablo III\Pics" ;Location of the .PNGs (NO SUBFOLDERS - ALL PNGS GO HERE)
then I copied the png images from the 1920x1080 to the Pics folder without any subtitle folders, just the images.. Did i do this right??
Last edited by JiveRook; 06-18-2012 at 12:18 AM.
this is running flawlessly for me now. i just upgraded my gear and im very very happy with the results now:
327% GF
110% MF
im getting like 360-370k/h. Also finding sometimes set and legendaries (almost all crap)
However, i think if notAres wants to make this script perfect, you just want to make some sort of automatic login/reconnect. this would be PERFECT. today i just saw, that diablo lost the connection and the bot didnt run for like 6 hours. maybe we could do something to prevent this sort of issue saving prescious time.
Im having the legendary issue aswell. I found one earlier but came and checked the script before it got to a stash run. Wouldit be possible to add a screenshot when the script detects a legendary on the ground to figure out if its selling them or just clicking the lamp. just checked it again and it has found 2 more and nother in my stash/inventory.
and is it possible to not identify rares/legendarys before stashing??
Last edited by abaddon88; 06-18-2012 at 12:46 AM.
Im running 1.9.1 and getting a fatal error stating that it cannot find the directory for the pngs. I went to the directory itself and copied its root name and pasted it directly into the code so I have no idea why this would be happening.