Last edited by zEEneXx; 07-05-2012 at 04:22 AM.
Did a little hotfix for guys with no working gold counter (maybe especially for you murdock84?) - the bot waited every run 1,5 seconds before he starts to run if $StartGold = 0 (defect goldcounter = always 0) - now he checks for the $Runs variable instead of the $StartGold
Just want to say awesome job on this, and thank you for getting changes out in a timely manner....You rock
Script is working really well, although I have one problem. After my WD has a full inventory, he uses town portal, sells to the vendor, and then salvages. After salvaging my WD goes to the right of the stash and does not stash items.
If I disable salvaging, my WD has no problems stashing. Has anyone else ran into this issue yet? -Thanks
I have no lag, 50fps, not virtualized.
I have computer lag set to 400, and movespeed set to 200.
Infoupdate to memory reading If the bot reads the memory to detect if the cellar is open or closed we can get about 2 seconds for closed cellar runs. some math:
1500 runs -> 50% closed -> 750 closed -> 750x2 seconds = 3500 seconds (about one hour)
average run time = 15s closed and 38s open = 26,5 seconds -> 3500 / 26,5 seconds = 132
that would make 1632 instead of 1500 runs. 50% open cellar of 132 = 66
66 open cellar runs * average 7000 gold per run = 462.000 gold (+66 x average 2 blue items = 122 items * average 750 sell gold = another 91.500 gold)
hope my math is correct
edit: and not to forget: if the bot know earlier that the cellar is open than i can make a new route which would give another second for open runs
Mhh you are the first with this problem :/
try to change in line 1950
to$SalvageLocation[0] = Random(1557, 1562, 1)
$SalvageLocation[0] = Random(1537, 1542, 1)
Last edited by zEEneXx; 07-05-2012 at 01:59 PM.
Im wondering why i got a legendary crafting material (fiery brimstone)? Did the bot salvage a legendary or is this a pick up?
Edit: The log says <18:53:38> Legendary found.
I suppose it salvaged the legendary^^
Maybe because it wasnt lvl 63?
Last edited by jannism; 07-05-2012 at 02:33 PM.
Do you really want memory reading? Would Blizzards hack detection not pic that up?Also wonder if terradata.exe is not picked up by that.
Btw, rename your exe's to like services or something inconspicous.
memory reading will be optional - a setting in the config to enable it - its for those who aren't scared by warden / know better how warden works
as far as i know warden dosen't scans for processes (not tesseract at least) and also "allows" memory reading, memory writing is dangerous and i won't include that
Amazing - the new route will also save about 2 seconds for open cellar runs - memory reading will increase gph about 50-100k
Last edited by zEEneXx; 07-05-2012 at 04:12 PM.
Memory reading, no matter how much more gold per hour it would provide seems like a very very bad idea. Even if you could quadruple your gold per hour, its just not worth the massive increased risk to my account
This is exactly what i was afraid of when the Tesseracts started getting added. Its just exponentially increasing your chances of getting banned, for near useless features
I personally feel if you want to include read memory, it shouldnt be an option in the script (we have seen how many people can barely figure out the current options). You should make 2 independent scripts, so no one gets banned because they forgot to disable an option, or accidently turned it on.