@Jesterpizza: The profile right now is kinda limited. If you get to the keywarden without being in combat, it should be able to detect it, kill it and then restart the profile. Most of the times, the keywarden finds you when you're in combat, so the profile doesn't detect it and it will clear Spire Level 1 before restarting the profile. @yogh: Use either Giles Trinity v1.6.3.4 or Trinity CE v1.7+. Don't use the versions in between.
I'm disappointed. I tryed this profiles, run what he have to do, change the plugins and routines, and everythings i got is : Incapacity of farm machine plans + all my others profile are fucked up and i dont know why.
What did you do? Running this for the first time is as easy as installing Trinity CE (toggling it active in DB) and loading the profile... Once done just disable Trinity and you shouldn't have problems with any other profile.
Uhh... You mean we're supposed to uncheck (disable) trinity after loading the profile but before we click the Start button of DB and run the bot?
No, Trinity must be active. The first time you install a plugin and load DB, it should be disabled by default (that why I said to toggle it).
This profile runs pretty good for me . I have found 3 plans in about 3 total hours of runs , but sometimes I check in with my little buddy and he is just making games and waiting for the inactivity timer to run out. Like I said though it works pretty good . Three plans is better than no plans!!! Thanks and good job.
This starts out fine for me but after a couple of minutes running it just stops moving and stops combat. If the unstuck routine attempts fail, I manually move it around a bit it usually starts moving on it's own for a while before it stops again. Usually at the same spots every time. My character is Monk class and I'm using Trinity v1.7.2.10 plugin and a Trinity routine that I believe are the most up to date versions. Log is included. View attachment 3652 2013-03-27 03.03.txt
I got exactly the same problem, just with my Barb. do any have some suggestions to solve the problem ?
Okay, I got this working by lowering diablo 3's priority in the windows task manager. I lowered the priority from high to normal and it seems to be working correctly now. Funny thing is that I have to load wow at highest priority when I use hb in order to avoid terrible lag, so I just assumed that diablo would need the same so I always used a .bat file to start it with high priority.
I have been running this profile just fine for a few days now. I have not tracked the number of runs, but I have not gotten the plans yet. After watching a few runs I noticed something. Here is my log: [18:40:45.247 N] Got 5 stack NV, loading keywarden profile. [18:40:45.631 N] Loaded profile [A4 - Inferno] AzureusPT - Infernal Machine Plan [18:40:45.650 N] ToggleTargeting, new values: Looting:True LootRadius:70 Combat:True KillRadius:40 [18:40:45.757 N] Using town portal [18:40:51.987 N] Townportal successfull, we are in town! [18:40:52.310 N] ========== Grid segmentation resetting!!! ============ [18:40:55.481 N] Using Waypoint Waypoint-28945 Number:5 [18:40:56.821 N] ========== Grid segmentation resetting!!! ============ [18:41:09.340 N] Interacting with object g_Portal_ArchTall_Orange-29150 [18:41:15.445 N] ========== Grid segmentation resetting!!! ============ [18:41:34.561 N] Interacting with object a4dun_spire_Elevator_Portal-29441 [18:41:37.764 N] ========== Grid segmentation resetting!!! ============ [18:41:40.665 N] ========== Grid segmentation resetting!!! ============ [18:49:36.962 N] ========== Grid segmentation resetting!!! ============ [18:49:36.974 N] Keywarden found! [18:49:55.311 Q] [Trinity]Player is dead [18:49:55.343 Q] [Trinity]Player is dead [18:49:55.435 Q] [Trinity]Player is dead [18:49:55.482 Q] [Trinity]Player is dead [18:49:55.561 Q] [Trinity]Player is dead [18:49:55.605 Q] [Trinity]Player is dead [18:49:55.696 Q] [Trinity]Player is dead [18:49:55.739 Q] [Trinity]Player is dead [18:49:55.827 Q] [Trinity]Player is dead [18:49:55.862 Q] [Trinity]Player is dead [18:49:55.963 Q] [Trinity]Player is dead [18:49:55.987 Q] [Trinity]Player is dead [18:49:56.086 Q] [Trinity]Player is dead [18:49:56.109 Q] [Trinity]Player is dead [18:49:56.210 Q] [Trinity]Player is dead [18:49:56.239 Q] [Trinity]Player is dead [18:49:56.330 Q] [Trinity]Player is dead [18:49:56.360 Q] [Trinity]Player is dead [18:49:56.449 Q] [Trinity]Player is dead [18:49:56.480 Q] [Trinity]Player is dead [18:49:56.572 Q] [Trinity]Player is dead [18:49:56.601 Q] [Trinity]Player is dead [18:49:56.704 Q] [Trinity]Player is dead [18:49:56.730 Q] [Trinity]Player is dead [18:49:56.836 Q] [Trinity]Player is dead [18:49:56.859 Q] [Trinity]Player is dead [18:49:56.960 Q] [Trinity]Player is dead [18:49:56.985 Q] [Trinity]Player is dead [18:49:57.083 Q] [Trinity]Player is dead [18:49:57.107 Q] [Trinity]Player is dead [18:49:57.205 Q] [Trinity]Player is dead [18:49:57.231 Q] [Trinity]Player is dead [18:49:57.328 Q] [Trinity]Player is dead [18:49:57.353 Q] [Trinity]Player is dead [18:50:00.337 N] Player died [18:50:00.337 N] ProfileOrderManager.OnPlayerDied, Resetting caches. [18:50:00.340 N] Clicked revive button [18:50:03.610 N] Keywarden killed! [18:50:03.834 N] Using town portal [18:50:10.284 N] Townportal successfull, we are in town! [18:50:10.500 N] ========== Grid segmentation resetting!!! ============ [18:50:10.963 N] Run done! [18:50:11.302 N] Loaded profile [A4 - Inferno] AzureusPT - Infernal Machine Farm START [18:50:11.302 N] Leaving game, reason: Profile loaded After reviving, it says the keywarden is dead, and starts all over again, without killing him. I don't have the log from a previous run, but after detecting the keywarden, my bags were full and did a town run. Then the bot proceeded to say keywarden is dead and left the game to start a new one. Im wondering if this is just problems with how demonbuddy runs, or with the actual script. Thanks.
15+ runs.. i maybe had to use the mouse to unstuck char 8 times?? its stable, good, loved it... thank you
My farms 5 NV fine, but at a certain point, suddenly delcares *keywarden has been found*, *keywarden has been killed" without actually killing the KW.
this profile is having trouble with getting stuck for me, often it will make it to the keywarden, kill him, then aimlessly walk around when the whole area is cleared without restarting the profile
