[A1 Inferno] Keywarden Hunt

[A1 - Inferno] Keywarden Hunt - modified version of ciggarc's Champion Hunt


What does it do?

1. Leoric's Manor and Courtyard
2. Leoric's Hunting Grounds (if you don't have NV2)
3. Festering Woods
4. Fields of Misery

As soon as you receive NV5, it will warp to Fields of Misery to hunt for the Keywarden. Kills warden and restarts game.

Required Plugins

- Linked KeyRun Plugin v1.4 for Trinity CE v1.7.1.3+ users
- Unified Trinity CE Download

Run the act1_start.xml to begin the profile.

Please make sure you have the latest version of DB

Thanks to the ciggarc's team for this original profile. Happy hunting!

******************
Changelog:

Code:

v2.5
- Updated KeyRun to v1.4 for added support of Trinity CE, as well as Infernal Key detection!
- Will now only do Hunting Grounds if you do not encounter 2 elites in Leoric Manor/Courtyard.
  Once you kill 2 elites, it will immediately warp to festering woods. Quicker than hunting grounds to find elites.
- Fixed game restarts if you DO NOT find warden
v2.4
- Updated KeyRun to v1.3 - UPDATE YOUR PLUGIN!
- Additional Trinity Checks and forced refresh of monsters/items for improved loot collection and premature warps
- Preventative hooks for reloggers
v2.2
- Uses new KeyRun plugin for better key warden handling
- Added town warp fallback for reduction of possible stucks

Recent Notes:

Code:

I will provide LIMITED SUPPORT for the individual profiles, I suggest you move to my A1-A3 Keywarden Search which I more actively maintain:

 

Ill try this one tonight! Ill let you know how it worked out for me!

 

where can i got the RadsAtom (1.5.1

 

Updated the original post with a link to RadsAtom and Guiles.

 

Does it have the stuck in field of misery like Radonic's current one?

It is a 100% stuck rate in the field where the key warden is. It just stands still and doesn't do anything till the inactivity timer is tripped

 

how do you add a code to pick up the key - i ran a modified act 3 profile that just basically go to 3 places to get valor and then last place is stonefort, bot did ok on that part - but when the warden is dead and a key dropped - it wasnt getting picked

 

I don't believe so, I haven't gotten stuck like that once and I've run through this profile many times (and it clears Misery every time).

 

I believe Trinity is still working through that. There is some question of all the key names so hopefully that will be fixed for all keys soon. He is looking for logs of keydrops and things not picking up so he can fix. Check his plugin page for more details on it.

 

FYI, looks like Trinity posted an update 1.6.3.2 which I am NOT running...sound like it requires a DB Beta build so keep that in mind if you need to update Trinity. I imagine there will be a number of updates to these plugins the next few days with the new 1.0.5 release so stay on top of it.

 

i will test this then.

Ty for post

 

Thanks for this profile. Just wondering what code you used to TP at NV5 and continue with the Fields of Slaughter profile??
Could this also be used to make a Key Run act 2,3 and perhaps a recipe run act 4?

Anyway, thanks again

 

Yes, I plan to make version for the other acts too. The XML code is this:

Code:

<Keyrun profile="insert your profile here" />

Place this after the <Order> tag. It will enable keyruns on that specific profile as soon as you hit NV5. I put this on all profiles except for the profile where the keywarden exists. The "insert your profile here" should link to the profile you want the keyrun to occur..so for A1, Fields of Misery, A2, Oasis, A3, Stonefort, A4 Silver Spire 1.

 

Giving this a test now.

 

FYI make sure you are running GilesTrinity 1.6.3.1...I noticed the latest version (1.6.3.3) is having trouble picking up keys. I was able to get a key using the earlier version, but not the newest. Hopefully they will have this fixed soon.

 

I noticed there's a potential Keywarden spawn in the very southern part of the Fields that might get missed. It's to the east of the path coming out of the Cemetary, before the map opens up to the wide field.

In this picture: http://www.diablowiki.net/images/f/f2/Fields_of_misery_map1.jpg
the spawn is pretty much straight south from the T in Cemetary of The Forsaken

 

I noticed that even after killing the warden it runs around for another good 3-4 minutes killing random things. After a bit it will tele back and leave game.

Otherwise it works great.

 

Got a problem when the inventory is full, it does a town run then goes back into the TP to pick up whats left and just stands there afterwards doing nothing.

 

Yeah not sure if there is a way to detect when the warden is dead...I'll look into it. Until then, it just finishes off the Fields of Misery and restarts.

I haven't encountered this, verify you've got the latest DB and plugins except trinity (keep that at 1.6.3.1 for now). I've made many town runs as I collect pretty much all rares to sell and it works fine. I've seen it get stuck maybe once or twice on other profiles or if I've been messing with it. If you continue to have an issue, the quick remedy is to simply only pick of i63 rares and legends...probably will take a few runs to fill up. I did that when DB broke the identify earlier today.

Got it, I'll take a look and see about adding a map point. I'm testing Act 2 keywarden run now. Should have that posted tomorrow.

 

does this profile exceed number of games limit

 

Negative. I supposed if you used this at MP0-1 and were doing 200K+ dps, you might burn through all these places, but if you're hunting for keys, you want to get that MP level up.