Key Bot - Infernal Keys farmer

[dbmaz]

1. What RADIUS do I have to increase? Is it Trigger range for Trash combat?
2. 2.6.5 bugs out when trying to use WP in act 3.
3. But now it gets stuck when there is a lot of monsters blocking it.

1. Demonbuddy bot settings -> Kill Radius.
2. You are sure, you got updated KeyBot.xml in your KeyBot/Profile folder from here?
3. Illusory boots.

 

[kuskner]

1. Demonbuddy bot settings -> Kill Radius.
2. You are sure, you got updated KeyBot.xml in your KeyBot/Profile folder from here?
3. Illusory boots.

1. its set to 50 never touched it
2. Yeah I got both of them
3. dont got.

Thx for the help tho

 

[dbmaz]

Install from scratch, use only required plugins, do not use unsupported ones, like trinity 2.6.x.

 

[oktogo]

After going through all the settings I am still getting issues with the bot not picking up the A3 KW keys after kill. I am going to assume it is a trinity issue or a profile reloading issue since I have tried almost all combination of setting changes.

I am using Trinity 2.5.2 (w/ your modified profile and recommended changes) and QT 3.3.12. This is a fresh install only running Trinity/QT/KB.

 

[BuddyMe]

omg dbmaz you rock
i will update the first post soon with your changes and maybe some improvement to the plugin logic

 

[gerardiablo]

sometimes i get this after bot kills a warden

[QuestTools][<MainCoroutine>d__1] Reloading profile D:\Downloads\Demonbuddy 1.1.2232.400 - Trinity 2.7\Plugins\KeyBot\Profile\KeyBot.xml Act="OpenWorld" questId="312429" stepId="2" levelAreaId="409512" worldId=409510
Loaded profile KeyBot
ToggleTargeting, new values: Looting:True LootRadius:50 Combat:True KillRadius:50
[KeyBot] Looking for next step
[QuestTools][<MainCoroutine>d__1] Profile loading loop detected, counted 15 reloads
Profile completed
Number of games completed: 1

keeps looping that same error message and bot just stands there

 

[dbmaz]

try this one https://www.thebuddyforum.com/demonbuddy-forum/210799-beta-demonbuddy-beta-builds.html

 

[Acps]

Which one will work with fork 1.0.1 dbmaz?

 

[gerardiablo]

Bot also sometimes explores the whole map in act 1 after killing keywarden...anyone else have this happen to them? Im guessing that sometimes it kills the warden in 1 shot and it doesnt register it as a kill

[KeyBot.SafeMoveToListTag] ReachedAllDestinations!
ToggleTargeting, new values: Looting:True LootRadius:50 Combat:True KillRadius:50
[KeyBot] KeyWarden not found

after it killed the warden it spent about 10 mins exploring the whole map, did this about 5 times in 25 runs

as you can see here, it registered the key dropping, but did not register it for act 1 dropping...hence the bot kept going after killing the keywarden.

It doesn't log it in DemonBuddy window that the keywarden was found like this

This is not just in act1, it happens on all acts, not registered the keywarden being killed, thus wasting time exploring the whole map

Used both Beta and Latest Stable demonbuddy with 2.7 Trinity and Latest Questtools

 

[hkme]

thanks dbmaz for update, it works fine with Trinity 2.7.0

 

[CalifRHCP]

It wont loot any key drops for me..

Using QT 3.3.11 w/ trinity 2.7.0

Installed keybot as per instructions on first page and replaced the keybot profile with the 2.6.3 trinitry profile (since there didn't seem to be a 2.7 one)

If a key drop it sits like an idiot waiting and then eventually just teleports away.


Edit* Not sure whart the deal is, I messed with trinity settings, i had unchecked "Pick up low level items". I rechecked it and it seems to pick up keys now. Don't know if it was due to that, or something unrelated however.

 

[eroticpastry]

Fresh Install, Trinity 2.5.2 QT 3.3.11
Loots keys fine

Issues I have found:
In act 3 the bot refuses to teleport to waypoint 27 aka Stonefort.

Will try with Updated Trinity

 

[ikbenpro]

Fresh Install, Trinity 2.5.2 QT 3.3.11
Loots keys fine

Issues I have found:
In act 3 the bot refuses to teleport to waypoint 27 aka Stonefort.

Will try with Updated Trinity

search for <UseWaypoint waypointNumber="27" questId="1"/> in the profile (Keybot) and then change the 27 to 28 it worked for me.

 

[dbmaz]

In act 3 the bot refuses to teleport to waypoint 27 aka Stonefort.
Trinity 2.5.2 QT 3.3.11

update for 2.2 patch:
https://www.thebuddyforum.com/demon...y-bot-infernal-keys-farmer-3.html#post1922645
update QT btw.

 

[Xenetron]

Mine won't attack mobs - not sure why? I'd like non-zerg version to work, tried editing the first Combat = True but no luck, anyone help?

 

[dbmaz]

Enalbe "trinity support required log" and upload log here when you face such issue next time.

 

[oktogo]

Any ideas why I am getting profile loading loops whenever I try to do A4? Do I need to use a different profile for A4? It basically kills the RG once then going into an infinite spam of profile load looping. I don;t get this issue on any other acts.

 

[dbmaz]

Enalbe "trinity support required log" and upload log here when you face such issue next time.

 

[cianny]

mee too have problem in act 4, somtimes dont pik a key and sometimes dont kill a boss i try varius profile and varius version of trinity but nothing

 

[Acps]

Had an issue with Bot finding keywarden then never engaging in combat. Just stood there. It was like it was still trying to zerg. Has anyone got this working with Fork 1.0.1?