Magi's [A1 - A3 Inferno] Keywarden Hunt (Randomized)

Hello Everyone,

1. What is this?
This is a thread with a link to a file that has the A1-A3 Key Run profile/plugins that works as of 5-27-13. I see no reason for it not work in the future as well since it's mainly dependent on Trinity & KeyRun.
All this work is done by Magi, among others; and I take no responsibility or credit for it.

I apologize if I haven't given anyone credit for their hard work on the profile/plugins, etc etc...
I am merely providing a link to a working system.

2.Will I support this?
To be honest, I haven't even studied the code that much, and I don't really have an intention to. The profile works perfectly fine for me and there is no reason for me to support it.

3. Why did I create this thread?
I am creating this thread because I am kind of tired of replying the same message over and over again in Magi's original thread:
http://www.thebuddyforum.com/demonb...-a1-a3-inferno-keywarden-hunt-randomized.html

For more info on this profile, go to the link above.

4. What's in the file?
1. Trinity 1.7.2.13
2. Linked KeyRun plugin
3. A1-A3 Key Hunting 3.2 Profile created by Magi

5. Directions.
1. As always, upgrade to the latest version of DemonBuddy, including the betas.
2. Place the plugins in your plugins folder, and the profile anywhere you want.
3. Run the A1-A3_START_HERE.xml to begin the profile.
4. Should work without any hiccups.

6. Where's the file dude???
Down below awesome people.

View attachment KeyRun 3.2 (Keep Depths, Act 3).zip
View attachment KeyHunt.zip

UPDATE 5-27-13 5:49 PM PST
1. The KeyRun 3.2 (Keep Depths, Act 3) file above includes Keep Depths 2 & 3 for faster NV building in Act 3.
It's a blend of RRIX and FallenDev's profiles, so thanks to them!
2. If you are using KeyRun 3.2 (Keep Depths, Act 3), make sure you enable QuestTools plugin (included).
3. This is my first attempt at modifying a profile/adding in functionality. Expect things to not work perfectly, and please let me know the bugs.

 

Thanks for putting all the files together.

I have problem with this profile though. I only have the files you attach, nothing else.
My monk keeps dying esp. in FOM, i.e. standing on top of the acid clouds or fighting on top of them,
I played with the settings in the Trinity PLugins, under combat>monk, but nothing helps.

What did I do wrong?

 

This is an issue with your build/how Trinity handles combat, rather than the profile itself.
1. Try to increase your resists, I have 99 Paragon Monk now, with close to 600 all resists.
2. Increase the distance for the trees under Monk > combat. Play with the settings a bit more.
3. If the above 2 don't work for you. Dump the current Trinity plugin folder, download the new one, and try again:
http://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/119849-trinity-1-7-2-13-a.html

 

This problem was fixed by rrrix and will be released in a future Trinity build.

 

As i said in the other thread, the profile is actually working pretty good. There are still minor bugs, but as long as you lower the gold inactivity time to 120"max (my suggestion) there shouldn't really be any problems. The most annoyng thing i've seen happen is when the keyrun plugin crashes, stopping the game so you have to restart it manually. But it happens rarely. Other things, bot get stuck pretty often and can't always unstuck itself. Anyway thanks to guppysb for making the thread!

 

I see. Thank you all for the replies.

 

Thanks for this. However, for act 3, do you think you can add on Keep depth 2/3 for faster NV farming?

 

It's not my profile, but I'll give it a shot soon enough. Memorial day weekend is kinda busy, so in the coming days I'll try to put something together. I wouldn't get your hopes up though.

 

[01:13:59.373 N] [Trinity][TrinityMoveTo] Started Tag; x="2133,532" y="850,7025" z="0,09999888" name="FoM #15" questId="1" stepId="0" worldId="71150" levelAreaId="19952"
[01:14:04.382 N] [Trinity][TrinityMoveTo] Started Tag; x="1921,362" y="796,5828" z="0,1" name="FoM #16" questId="1" stepId="0" worldId="71150" levelAreaId="19952"
[01:14:17.561 N] [Trinity][TrinityMoveTo] Started Tag; x="2073,154" y="736,8131" z="0,1000029" name="FoM #17" questId="1" stepId="0" worldId="71150" levelAreaId="19952"
[01:14:22.642 N] [KeyRun] ========== KEYWARDEN FOUND ============
[01:14:23.594 N] [KeyRun] WARDEN HP: 668342,7
[01:14:23.594 N] [KeyRun] ========== KEYWARDEN OUT OF RANGE ============
[01:14:23.886 N] Profile completed
[01:14:23.886 N] Number of games completed:2

Then goes Afk, had 2 restart bot after some minutes after seeing "AFK" message in D3, happend 3 times today so far. I guess when Keywarden goes out of range and demonbuddy sets profile to completed he can't leave the game since Keywarden isn't dead or something. edit: This has happend in Act 1, Act 2 and Act 3 so no Act issue (just making that clear)

I have Keyrun and Trinity plugins installed with latest versions and the newest of this one. Any guesses how this can be fixed? Preferably with the bot trying to find keywarden again rather than just leaving if he teleports OOR (out of range)

Another weird thing is that every time i start the profile he enters the game, goes to the stash and leaves, >>>

[04:47:30.561 N] [Trinity]ItemRules loaded a total of 292 Soft rules!
[04:47:30.592 N] Waiting 3.1 seconds before next game...
[04:47:33.736 N] Creating new game. Params: [Act:A1 Difficulty:Inferno Quest:72801 QuestStep:36 ResumeFromSave:False IsPrivate:True Handicap:2]
[04:47:38.790 N] Loaded profile [A1 - A3 Inferno] Keyhunting - Choose an Act
[04:47:38.973 N] [KeyRun] New Game Started, Reset Variables
[04:47:38.973 N] GameChanged. Clearing actors
[04:47:39.072 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[04:47:39.384 N] Loaded profile [A1 - A3 Inferno] Keyhunting - Choose an Act
[04:47:39.384 N] Game joined, Resetting profile caches.
[04:47:39.388 N] ========== Grid segmentation resetting!!! ============
[04:47:39.474 N] [Trinity]Starting up Generic Cache Manage thread
[04:47:39.475 N] [Trinity]Starting up Generic Blacklist Manager thread
[04:47:45.204 N] Interacting with object Player_Shared_Stash-12
[04:47:46.267 N] [KeyRun] Act 1: 1
[04:47:46.267 N] [KeyRun] Act 2: 0
[04:47:46.267 N] [KeyRun] Act 3: 0
[04:47:46.267 N] [KeyRun] Loading act 2
[04:47:46.267 N] [KeyRun] Loading new profile.

Made this in the old thread so thought i'd give it a try here instead since you may not respond in the old one (sorry if you look at is as spamming)

 

Hey,

Issue #1:
I left my monk on mp5 key hunt last night for about 9 hours, and I could not reproduce your issue. Are you able to even successfully kill the keywarden at least once? See if you can do a bit more testing/debugging. Also, if you can post a detailed log, that'd be great, instead of what you just see on the DB console.

Issue #2:
The reason your character goes to the stash at the beginning/end of every profile is to see how many keys you have. It says it in your log above. Based on the keys it sees in your stash, it does that corresponding act.

 

nr1:
It works perfectly like 90% of the time, perhaps I should had mentioned that, but the other 10% this happends, it seems to be when keywarden teleports out of range from him that he doesn't try to find him again. instead says it will load the next profile but just sits afk in the game doing nothing untill i restart him.

nr2: ok nice, didn't know that

 

Ok, I'll see if I can fix this in the near future.

Update.
I have included Keep Depths 2 & 3 for Act 3, in KeyRun 3.2 (Keep Depths, Act 3). This is my first attempt at trying to modify a profile, so expect problems. But if no problems, great!

 

Man, 855 views, and not even 1 reply to the new profile settings in Act 3.

Someone let me know if it works ok, lol.

 

The previous profile (Core & Tower, etc) farmed NV much faster for me, or so it seems. But that's alright, because after all it could be mostly luck.
None the less thank you for your work and I'll make sure to keep you updated if I run into any issues.

EDIT:
The bot all of a sudden now manages to get stuck in Stonefort, ends the game but doesn't really end it. Interesting.

 

I didn't even touch the StoneFort profile....it's shouldn't be getting stuck there, at least no more than compared to last time.

 

don't works with r-yar ...

 

I don't use reloggers, so I would not know how to implement them. You're more than welcome to give it a shot

 

now with the kickstart seems to works ... not 100% sure bc sometimes get stucked again ^^

(i'm testing now ... was at work )

 

btw in act 3 when enter in keep depts 1 it get stucked after the teleport...

[00:18:58.256 N] [KeyRun] New Game Started, Reset Variables
[00:18:58.541 N] Loaded profile Keep Depths 2 by rrrix
[00:18:58.556 N] Using Waypoint to Keep Depths 1 for Keep Depths 2 Portal
[00:19:01.064 N] Using Waypoint Waypoint-103 Number:2
[00:19:01.601 N] Now loading Keep Depths 3.
[00:19:03.774 N] ========== Grid segmentation resetting!!! ============
[00:19:04.010 N] Loaded profile Keep Depths 3 by rrrix
[00:19:04.134 N] ========== Grid segmentation resetting!!! ============
[00:19:04.348 N] ========== Grid segmentation resetting!!! ============
[00:19:04.872 N] ========== Grid segmentation resetting!!! ============
[00:19:05.350 N] ========== Grid segmentation resetting!!! ============
[00:19:05.858 N] ========== Grid segmentation resetting!!! ============
[00:19:06.367 N] ========== Grid segmentation resetting!!! ============
[00:19:06.870 N] ========== Grid segmentation resetting!!! ============
[00:19:07.372 N] ========== Grid segmentation resetting!!! ============
[00:19:07.872 N] ========== Grid segmentation resetting!!! ============
[00:19:08.396 N] ========== Grid segmentation resetting!!! ============
[00:19:08.883 N] ========== Grid segmentation resetting!!! ============
[00:19:09.388 N] ========== Grid segmentation resetting!!! ============
[00:19:09.889 N] ========== Grid segmentation resetting!!! ============
[00:19:10.401 N] ========== Grid segmentation resetting!!! ============
[00:19:10.902 N] ========== Grid segmentation resetting!!! ============
[00:19:11.418 N] ========== Grid segmentation resetting!!! ============
[00:19:11.906 N] ========== Grid segmentation resetting!!! ============
[00:19:12.397 N] ========== Grid segmentation resetting!!! ============
[00:19:12.930 N] ========== Grid segmentation resetting!!! ============
[00:19:13.422 N] ========== Grid segmentation resetting!!! ============
[00:19:13.914 N] ========== Grid segmentation resetting!!! ============

 

and another thing on every
TrinityMoveTo
i get a little froze...

i think is an old command and the right way is like that
<TrinityUseOnce id="225">
<SafeMoveTo questId="1" x="2909.772" y="4623.869" z="100.0591" pathPrecision="8" />
</TrinityUseOnce>

but i don't know where see the API of this bot... is really hard to try to do something without documentation....