[A1 - A3 Inferno] Keywarden Hunt [A1-A3 - Inferno] Keywarden Hunt What does it do? Act 1 Act 2 Act 3 Required Quests Act 1 - The Imprisoned Angel Act 2 - Lord of Lies Act 3 - Siegebreaker As soon as you receive NV5, it will warp to appropriate location to hunt for the Keywarden. Detects Keywarden and warps out on keywarden death. Will check how many keys you have collected and select appropriate profile based on what keys you still need. Required Plugins (Trinity Community Edition v1.7.1.16+ users) Unified Trinity Community Edition Download KeyRun Plugin v1.8.2 Run the A1-A3_START_HERE.xml to begin the profile. To install the plugin, ensure it is located in it's own folder like so: [DB Folder]/Plugins/KeyRun/KeyRun.cs Make sure to enable the plugin before starting. Happy hunting! ****************** Changelog: Code: v3.2 -------------------------------- - Updated KeyRun plugin to 1.7 which should fix the town bug from the new patch - Will now force walk to the Keywarden again - Minor updates/bug fixes v3.1 -------------------------------- - Reverted back the forced path to Warden when in range...need to do some further tweaking. Works beautifully for death handling though! v3.0 -------------------------------- - I'm back! - All MoveTo's have been upgraded to TrinityMoveTo's for reduced backtracking - Most maps have been entirely re-worked and optimized to accomodate new movement tags - Updated KeyRun plugin for latest Trinity, includes some new tags and features: + Will now generate a path to KeyWarden once in range (100 feet) + Will generate a direct path to KeyWarden upon death vs restarting whole profile if found + Additional check to ensure Trinity is done doing what it needs to do before warping out on NV5 (this still isn't perfect but seems to have helped a bit. I'll continue to tweak) rrrix edited: attached keyrun 1.8.2; (the "Trinity free" version.. )
Nice setup, but Act 2 doesn't have nearly enough areas to get 5 stacks. My bot went through Mine, Alcarnus, and Winds and only got TWO somehow. Add Howling Plateau instead of Sweeping Winds and Desolate Sands just in case.
Looks promising. Testing it right away. Wonder if it gets stuck in Fields of misery like the original I will let you know. Good work.
It keeps skipping act1 forever. Creates game, leaves and goes to act2. PS. Sorry, didn't read carefully.
Thanks, it works great! But... [02:17:58.349 N] Clicked revive button [02:17:58.382 N] [RadsAtom] - Released at: 10/19/2012 10:17:58 PM [02:17:58.382 N] [RadsAtom] - Deathcount at: 3 [02:17:58.382 N] [RadsAtom] - Resetting the deathcounter. [02:17:58.382 N] [RadsAtom] - Leave game, died too much. This problem (leaving game on 3 deaths) ruins everything. Can anyone please help to somehow disable this terrible function?
This is a RadsAtom setting. Just open the config for RadsAtom > General Tab > Death Handling > Set it to what you want.
Yeah I saw the same thing one time as well...normally I can grab 4-5 NV prior to Oasis and usually end up finding 2-3 elites in Oasis before the keywarden, but I will see about adding the other areas as well.
I'm unlucky or i made an error but 3 times he does Act 1 ^^' PS : nevermind, i think the bot do the same act untiel he got a Key
It can happen, I'm not certain how "random" DB is with their profile loads but I've watched this enough to know it will play through all 3 acts eventually. Mine has tended to start off in Act 3 lately and play that a few times. I'm having a statistical drought with the keys however. I've probably made 12-14 keyruns at MP3 the past day with not a single keydrop. Not nearly as bad as slaughtering 3 ubers and seeing nothing! Luck of the draw unfortunately.
My first run started with Act 2, farmed up 5 stacks and then it searched most of the map, but not all, then he quit without finding the keywarden. Anyone else experiencing this?
I thought it explored all the possible spawn areas of the warden, but I know it doesn't explore every inch of the map since there are some randomized portions of that map that could get it stuck. If someone manages to encounter this issue again, perhaps you can pause the bot and manually search the unexplored areas to see where the warden is hiding. A screen shot on the map where you find him would help as well.
Cool, OK I'll look into. There is a spot in Act 1 I caught as well I think...sometimes he sees you but you don't see him and he follows you up to a certain point while your character continues moving. Sometimes ending up in an area would wouldn't normally explore. I'll see what I can do.
I'd like to request 1 thing into this profile, just to save some manual game play, if it's possible I would like that Act 1 start quest is instead of 9.3 it would be 10.1, and again if it's possible that is. if it starts on 10.1 and the bot is up to 5 nv so I could just abort the botting and go straight to the ?ber bosses instead of making a new game and farm the nv's or kill the butcher, I would change it myself if I could, but hey, I'm a user not and maker
That's a good idea. Let me see if I can get it to go. For some reason, I was having troubles getting the final quests to launch in Act 2. I was attempting to pull Leia and her mother from the Belial quest and bring them along for the keyhunt to help draw some enemy firepower. I've done that manually and it helps quite a bit. We'll see what happens.
That's a good idea. I'll do it up for you. I'm also going to change the start game of Act 2...got a little trick to help people tank That to come shortly after my bot kills the A3 keywarden and gets me a damn key!
Great work on the randomization. I've attached a screenshot of an area where I manually found the keywarden after the bot was about to exit the game without finding him.
Who needs some help in Act 2? I gave you some helpers For some reason it wouldn't TP back to town, so I made it walk there quickly. In any case, you now have a few friends to tag along while you hunt for the keywarden. Just replace the XML file with this one, game on.
