What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[A2 - Normal] Leoric's Signet Farming w/ 5 NV Stacks

Is this profile intended to be used with a non-elite radius of zero or very large? (i.e. should we bother killing any trash, or only for farming elite packs?)

Thanks for the update! Works well for me so far.
 
Nice thanks for the Update !

But i got now a new problem, my bot everytime stucks at the same place in the oasis (with 1.4 dont) - It also doesnt trigger the unstucker there, and i dont know why :(

[22:56:13.989 D] Generating path to UNKNOWN - <3202.857, 4453.867, 98.65264>
[22:56:13.989 D] Waiting for path request to finish...
[22:56:14.085 D] Generating path to UNKNOWN - <3202.857, 4453.867, 98.65264>
[22:56:14.085 D] Waiting for path request to finish...
[22:56:14.085 D] Exception while receiving length!
[22:56:14.086 D] System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei (Object , IAsyncResult )
bei Zeta.Navigation.DefaultNavigationProvider.(IAsyncResult )
[22:56:14.103 D] Generating path to UNKNOWN - <3202.857, 4453.867, 98.65264>
[22:56:14.123 D] Waiting for path request to finish...
[22:56:14.227 D] Generating path to UNKNOWN - <3202.857, 4453.867, 98.65264>
[22:56:14.228 D] Waiting for path request to finish...
....
....
....
Click to expand...

stuck.webp

Everytime the same place, with Barb and DH ...

Maybe u can help me with this ?


*edit*
Second problem : If the run is finshed - He starts over and over profile 6 in Oasis everytime in the new game and not from beginning to collect NV stacks. Why ?


*edit 2*
ok solved both problems at my own :-)
Everyone else with this problems (stuck at that position which i meaned and loop oasis after finish run) can download here the updated version :

View attachment [A2 - Normal] Leoric's Grinder 1.5a - MEEKI Update.zip

Now it runs perfectly with DB .259 / Gilles 1.6.2 and RadsAtom 1.4.1
 
Last edited:
evoxtasy2010 said:
Hey guys,

So after some newbish modification, I altered the scripts to start at act2 quest 8. Make sure when you're going to start your bot thread that you have Normal mode quest 8 selected. The attached file will only run through the following:

Black Canyon Mines
Road To Alcarnis
Stinging Winds
Dahlgur Oasis

and repeat.

This helps avoid bot issues in the sewers that are randomized. Still have 5stacks before oasis. The original profile was great but I think this will increase the amount of runs therefor increase leoric's signet drops. Both the sewers area's do have good leroic's drops but from most my research the oasis is the best and has the highest probability to drop a high percentage ring. Best of luck, hope it helps!

Cheers,
-Evo :cool:

PS.
I am still running this on GilesTrinity_v1.4.9.1 as per my long tutorial. I am also using the most current DB release (Demonbuddy 1.0.1049.273). The fact that all the ashera bullshit was removed may make this run okay with the latest Giles but I have yet to test it.

View attachment 59988
Click to expand...

Nice one dude . This is what we need to increase the efficiency. Less stuck less down time . more chance to get the ring . Well done !!
 
Fully AFKability is much more important than finding every little place where the ring can drop. I agree with Nagag.
 
Meeki said:
Nice thanks for the Update !

But i got now a new problem, my bot everytime stucks at the same place in the oasis (with 1.4 dont) - It also doesnt trigger the unstucker there, and i dont know why :(



View attachment 60057

Everytime the same place, with Barb and DH ...

Maybe u can help me with this ?


*edit*
Second problem : If the run is finshed - He starts over and over profile 6 in Oasis everytime in the new game and not from beginning to collect NV stacks. Why ?


*edit 2*
ok solved both problems at my own :-)
Everyone else with this problems (stuck at that position which i meaned and loop oasis after finish run) can download here the updated version :

View attachment 60063

Now it runs perfectly with DB .259 / Gilles 1.6.2 and RadsAtom 1.4.1
Click to expand...

Glad you got it working for barb and demonhunter on that setup however, I stated previously that I was using giles 1.4.9.1 which did not support DH's at all. I am also just using rads profile manager from the 1st post and the last optional release there, not an updated or latest. Also the latest release of DB is Demonbuddy 1.0.1049.273... If you loaded the profile as i instructed it should have never come across ashera because it bypass' that entire part of it. You're loading a later part of the quest line so that whole part is not necessary. More potential hang ups and like the other guy said previously, this is about efficiency. So again, glad you got it working but, my release was for my setup and the one I suggested earlier.

Cheers,
-Evo :cool:
 
Thanks Meeki!
Its running flawless now ;)
Running on my Mage 1 run = 10min
100% AFKability

Keep it up
celloc
 
Thanks Meeki!
Its running flawless now ;)
Running on my Mage 1 run = 10min
100% AFKability

Keep it up
celloc
 
Giving Meeki's profile a good test drive today. Been running for two hours straight. Found two legendaries so far in the Oasis, but the ring is still eluding me. :cool:

Demonbuddy 1.0.1049.273
Giles Trinity 1.6.2
RadsAtom 1.4.1
 
Still worth the effort to farm this ring after patch 1.05 ?
 
any 1 can edit the latest version 1.5a . so we can bot on normal MP10 . can have 100% Magic find more :D. thanks
 
Last edited:
You're right about MP not factoring in. Tony posted on another forum that they are adding it in. I downloaded Demonbuddy 1.0.1073.27 BETA and manually set MP to 10. Started bot and it's churning away. :cool:
 
Last edited:
I ran Meeki's update for a couple of hours to test the new blacklist entry. I found two legendaries, but not the ring.


When I initially ran this with MP0, my toon was getting stuck attacking Sokahr The Keywarden. After testing on MP10 (via GUI and via DB beta's slider), I could kill it. I went back to MP0 and found I could attack and kill it still.

If you run into a problem where your toon gets stuck attacking Sokahr The Keywarden, edit "7_HandBananna_Oasis_Meeki-Update.xml" and add the TargetBlacklists section just above the <Order> tag. Beware, if the bug clears, he could start attacking you. I'm not 100% sure, but wanted to make everyone aware of this just in case.

Code: 
<Profile>
<Name>[A2 - Normal] Champion-Hunting and Questing 1.4a HandBananna Profile 6</Name>
<GameParams quest="57337" step="26" act="A2" difficulty="Normal" resumeFromSave="False" isPrivate="True" numGames="-1" />

[B]  <TargetBlacklists>
    <TargetBlacklist actorId="256000" name="Sokahr The Keywarden" />
  </TargetBlacklists>
[/B]  
<Order>



Regarding monster power, the new Demonbuddy 1.0.1073.27 (BETA) has a MP slider under the settings tab. I tested it out with 0 and 10 and found it adjusted it accurately.



Demonbuddy 1.0.1073.27 (BETA)
Giles Trinity 1.6.2
RadsAtom 1.4.1

A2 - Normal] Leoric's Grinder 1.5a - MEEKI Update
 
Last edited:
Interesting update regarding Sokahr The Keywarden. When I initially was running it on MP 0, my toon attacked, but could not kill it. On MP 10 I noticed that my companion was able to kill him. With NV 5, I got 2 yellows and 6 blues.

Might need to blacklist this guy based on MP level. Investigating...


After investigating, I found I could kill it regardless of the difficulty. Updated my previous posts accordingly, just in case someone runs into the same quirky bug.
 
Last edited:
Nosh said:
Interesting update regarding Sokahr The Keywarden. When I initially was running it on MP 0, my toon attacked, but could not kill it. On MP 10 I noticed that my companion was able to kill him. With NV 5, I got 2 yellows and 6 blues.

Might need to blacklist this guy based on MP level. Investigating...


After investigating, I found I could kill it regardless of the difficulty. Updated my previous posts accordingly, just in case someone runs into the same quirky bug.
Click to expand...

Testing today with Meek's revision of the profile, with giles 1.6.3.1 and radsatom 1.4.2... and latest DB release Demonbuddy 1.0.1073.276... I'll let you know how it goes.
 
First run completed flawlessly with everything up to date... I am curious though if this was a Diablo patch change, DB revision change or a plugin change?! My Diablo windowed and smallest possible used to be allowed to run in the background now every move the bot makes it it making it my focus window (sound and resources allocated to it). I used to be able to run diablo on my primary monitor and be doing other things on my secondary. I can still do this however the sound is being played as if I have enable sound in background option enabled. Anyone else experience this?

Edit: avoided most of this by just turning off the sound. The Profile works very well with everything up to date. Got to love the Monster power 10 too.
 
Last edited:
You must log in or register to reply here.
Back
Top