Magi's Keywarden Hunt Continued - Last Updated: 03/17/2014

It gives me error when creating games using this plugin and profile! Anyone else? Any ideas? I'm using trinity 1.8.5 + beta build

 

just takes me to leorics. eventually bugs out and just stands somewhere random. watched it 10-15 runs and not once in any acts did it find a keywarden, seems to still want to farm the old 5x nephalem stack.

can someone please write a simple working keywarden profile, no counting keys etc just simply port directly to the area, run around till it detects keywarden, kill him, logout. i will pay. pm me!

thanks for trying though man, much appreciated

 

works fine, db beta .357 + trinity 1.8.7 + questtools 1.5.8 + keyrun 1.9.1

but the droprate sucks :/

 

Any way to block a keywarden so that the profile only goes to act 2 & 3? I have tons of act 1 keys from previous adventures, but lack 2 & 3.

 

Highly unlikely.

Yeah, it kind of does. 50% on Torment 6. 20 or 25 on Torment 1.

It definitely works. It works for everyone else. Most likely you mixed up the archives and installed one of the old profiles. Just remove all the profiles you already have as well as any old KeyRun plugin, then download the archive from the first post again (the name is "KeyHunt332.zip"), unpack it to your DB directory, start DB, enable the plugin and load the "A1-A3_START_HERE.xml" file from the "Profiles\KeyHunt" directory.

Make sure you have the required quests unlocked. They are listed in the first post.

Not necessary. The profile will ask the plugin how many keys you got and select the appropriate act accordingly. Only requirement is, that you actually have your keys in either your stash or the inventory of the character you do the run on, so the plugin can actually see them. Example:

Code:

[KeyRun] Key Counts: Act 1 => 0,  Act 2 => 0,  Act 3 => 16
[KeyRun] Loading act 1
[KeyRun] Loading new profile.
[KeyRun] D:\...\DB\Profiles\KeyHunt\act1_start.xml

I have 16 Act 3 keys already, so the bot will run act 1 and act 2 until both caught up.

 

That is awesome, thanks alot for the quick reply, and thanks for the work!

 

Demonbuddy crash everytime I try to config the plugin. Can you fix it?

P.S: Nevermind. It fixes itself.

Did 10 test runs and found 8 keys. Guess I'm lucky Thanks alot for the profile.

 

works great

 

[KeyRun] Moving to last known Keywarden Location to ensure item pickup...

Is there anyway to stop it from this behaviour? It kinda just lags around for 30s before finally leaving the game.

 

I second this too...sometimes I'll just be stuck forever and it's already been picked up.

 

I'm gonna add my two cents in

1. Thanks for the profile it works great but not 100%

2. In act 2 I've ran into a problem (once so far) that it explored almost the entire map never found the keywarden and tried to teleport out and restart but I stopped it and manually found it and started the bot again so it would kill it and then restart. The bot just sat there.

3. Its only done act 3 about 10 times now and act 3 once, in act 2 if you die you don't go right back to where you die, instead it starts to go around the map all over again where you have been already. Anyway to fix this?

4. Every time it starts a new game, it goes to the storage chest and sits there for a few seconds doing nothing then closes it. That could lead to a ban IMO

 

to 3.) same here. would be very nice, if he could simply "click" respawn at corpse or simply go abck to corpse.
to 4.) where is that from? I'm also doing this to check my mats when not botting^^

 

By far the best profile I have used so far. Only one request is it possible to have it salvage all the non legs it picks up?

 

Can u make it so the toon will ignore every mob untill it finds the key warden? killing stuff is a waste of time

 

go to your plugins tab and select keyrun plugin then hit the config button.
there is an option to ignore all until warden is found. it's not perfect but it does a pretty good job.

 

Here are the new level 70 key serial numbers for act 1-4, didn't verify the second key but it's running as expected.

key of bones:364694
key of gluttony: 364695?
key of war: 364696
key of evil: 364697


For the time being you can replace the keySNO line in KeyRun.cs (line 973) with this one to farm the new keys (act 1-3) as before.
keySNO = { 364694, 364695, 364696 };


You'll still need the fourth key, but you get that from the guy in Act 4. You need to be on torment, just as before. I hope this helps some, deeghs.

-edit-
Added fourth key SNO (will not farm it!)

 

^ Will they still drop keys if playing in any lower than torment?

I used to be able to do T3 and maybe T4 but after RoS's launch I can only play at Expert

 

Works very well but the droprate is horrible , i use this profile in tourment 4

 

Just by adding that it should work for A4? Even if there's no log for A4 in the profile folder :O
Will test it out ty

 

No, it will not farm act 4. The key array and it's functions need to be updated and new profiles need to be added. This was just a temporary fix to keep farming, you can still manually farm or use the Act4 profiles on the forum for the key of evil. I just wanted to help deeghs out by getting the appropriate keynumbers.