its freezes i have emc, notificationclick & msfix
I tired many times, even used the previous setting & version of DB & plugins before the day I started crashed, Im pretty sure its the bot itself crashed diablo, not any profile or pluginsIf i were you, i'd delete my DB install and just start over fresh. Pain in the ass yes, but it could alleviate some issues.
1) Setup your skills as follows - Skill setup for me (40 disc, 0 ms) is as follows: Hungering arrow (devouring), Cluster arrow (Loaded for bear), Caltrops (Carved Stakes), Vault (Rattling roll), Preparation (Invigoration), Companion (ferrets). Passives should be grenadier, sharpshooter, tactical advantage
There are some slight variations you can use, depending on how much disc you have. Less than 40, you should be using Vault (Tumble) to be able to tumble the entire way. Over 40 disc, you can adjust your Caltrops to use either (hooked spikes) or (Tortuous Ground) if you'd like.
"Q: Why isn't it summoning Ferrets?
A: Find the lines:
<!-- Summon ferrets -->
<UsePower questId="1" powerId="133695" />
and add:
<WaitTimer questId="1" waitTime="50" />
<!-- Summon ferrets -->
<UsePower questId="1" powerId="133695" />
If that doesn't work, increase waitTime="50" to waitTime="200". Also, although obvious, make sure your DH has Ferrets on your hot key bar."
Those lines don't appear at the demonhunter.cs file.
Using EMCBehaviour and version 1.3, it kills everything on the way to the cellar. With version 1.4, it just keeps dying.
Testing 1.4 with EMC.. so far is working. .. just a question.. if i die fighting sarkorth what will bot do ?
return to finish him or logout?
and if some nasty popup msg appear .. EMC clicks on it ? or should i download notifyclick as well ?!
thx =)
Working great, running 1.4 and EMC
Gold/hour: 580624
Games/hour: 128
Deaths/hour: 0
\Whats ur GF? I had to go back to 1.3 because 1.4 was wasting too much time after killing zombies near fail tp out. Couldnt go over 350k gph : /
Btw, just a suggestion for future scripts, would it work if you made bot to cast smokescreen with the 1,5 secs duration rune while hes about to tp out in a failed run? That may actually save time, just wondering.