[15:37:37.262 N] [GilesTrinity] Fatal Error - cannot enable plugin. Invalid path: C:\Users\XXX\Desktop\DBKeyhunt\Plugins\GilesTrinity\ [15:37:37.262 N] [GilesTrinity] Please check you have installed the plugin to the correct location, and then restart DemonBuddy and re-enable the plugin. [15:37:37.262 N] [GilesTrinity] Plugin should be installed to \<DemonBuddyFolder>\Plugins\GilesTrinity\ Getting this error if I use your modded Trinity. What should I do?
That error was an issue with the new Diablo patch for me. I couldn't use the bot at all. I downloaded the latest DB Beta build and it fixed it. Might try using the DB beta build. I ran this profile last night, ran for 8 hours with no issues. Got 4 Destruction Keys, 2 Terror Keys, and 4 Hate keys. Was still running strong when I got up in the morning and I shut it down for a break. See if the DB Beta build helps.
Also, one thing I did last night was change the order of the "randomized" profiles since it doesn't like to pull Act 2...for example: They all currently end with this on the keywarden profiles Code: <!-- switch profiles --> <Continue profile="act1_start.xml, act2_start.xml, act3_start.xml" exitgame="true" /> Vary them up on each individual keywarden profile: Code: <Continue profile="act2_start.xml, act3_start.xml, act1_start.xml" exitgame="true" /> <Continue profile="act3_start.xml, act1_start.xml, act2_start.xml" exitgame="true" /> <Continue profile="act1_start.xml, act2_start.xml, act3_start.xml" exitgame="true" /> Trinity offers a random integer function which I may try instead. Again, that Continue profile is supposed to be randomized but sounds like it doesn't work too well. In the interim, switching them up a bit on the 3 keywarden profiles worked for me (got 4 Act2 keys last night). Lastly, Act 3 still needs some keywarden work. I fixed another problem area where it would see the keywarden, get stuck, then get out of range trying to get unstuck, think it killed the warden when it didn't, and leave. There are a lot of spawn points for the warden it seems so this will just take time to figure them all out. If you want, you can change the radius in that "while" statement from 150 to 100 or 75. The lower the value, the less likely it will spot the warden, but at least it will kill him and just go through the rest of stonefort. The other acts don't seem to be an issue for me.
The latest profile for Act3 has no warping on NV5, I removed it. Make sure you're running latest profile. Not sure what it's doing in the courtyard but post a log after you've ensured your using profile 1.2.4
Just remove "act2_start.xml" part from the last continueTo line on the Fields of Misery and Stonefort XML profiles.
Not sure how reliable this is unsupervised. Get some stucks that other people mentioned, but overall, it's finding a decent amount of keys in all 3 acts. Been working from home today, so I can keep tabs on it. I think an update to RadsAtom will be needed for some stuckage. Thanks for this script.
Yeah it's pretty AFKable for me, though at times the keywarden script I have doesn't always fire or fires but doesn't finish the job (usually A3). Actively fixing those situations. I don't think it will ever be perfect since there is no way to interrupt a bot action (like walking to a wavepoint and finding the warden in the middle of the walk) with using profiles alone. I can only perform the check once you reach the MoveTo area. You can get stuck if your character veers too off path fighting monsters, that can happen in virtually any profile. I only bot with my wiz/monk...not sure how the other chars perform. I believe I've fixed any death/spawn stucks. If you get permastuck, please provide version numbers of everything, a log, and make sure you enable your RadsAtom/Trinity plugin. I noticed the latest version disabled them on me which broke the town TP.
Magi, i still rarely do a2 and it almost always get stuck in a3 in town, running to the southern most corner.
Did you change up the order of those profile loads? I posted about it a page or 2 back on how to do it. Might help with the A2 problem. Not sure what's going on with A3 for you, I've never gotten stuck in the town once. Can you post a log? Sounds like RadsAtom is screwing something up. What you could try is copy the game param tag from the act3_start.xml and replace the other act 3 profiles (they are different). Not sure how that would screw anything up, but perhaps it is: Copy this: Code: <GameParams quest="101750" step="10" act="A3" difficulty="Inferno" resumeFromSave="False" isPrivate="True" numGames="-1" /> And replace the ones in skycrown/stonefort
Get's stuck in act 2, every time. not just some, every time. before a single stack. first profile. even tried skipping it. just getss stuck Now I remember why I didn't use this, never worked
Sometimes after getting 5 stacks in A2 it just sits at the town until you manually load the next profile; [18:37:51.204 N] ========== Grid segmentation resetting!!! ============ [18:37:51.757 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:37:51.757 N] [RadsAtom] - Resetting the deathcounter. [18:37:51.809 N] Profile completed [18:37:51.809 N] Number of games completed:1 [18:37:56.844 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:37:56.844 N] [RadsAtom] - Resetting the deathcounter. [18:38:01.901 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:38:01.901 N] [RadsAtom] - Resetting the deathcounter. [18:38:06.970 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:38:06.970 N] [RadsAtom] - Resetting the deathcounter. [18:38:12.052 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:38:12.052 N] [RadsAtom] - Resetting the deathcounter. [18:38:17.086 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:38:17.086 N] [RadsAtom] - Resetting the deathcounter. [18:38:22.105 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:38:22.105 N] [RadsAtom] - Resetting the deathcounter. [18:38:27.150 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:38:27.150 N] [RadsAtom] - Resetting the deathcounter. [18:38:32.187 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:38:32.187 N] [RadsAtom] - Resetting the deathcounter. [18:38:37.232 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:38:37.232 N] [RadsAtom] - Resetting the deathcounter. [18:38:42.252 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml [18:38:42.252 N] [RadsAtom] - Resetting the deathcounter. [18:38:47.342 N] [RadsAtom] - Loading next profile: C:\Users\Chris\Desktop\Demonbuddy\Profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml
[23:10:48.271 N] Creating new game, Params: <Act:A3 Difficulty:Inferno Quest:101750 QuestStep:10 ResumeFromSave:False IsPrivate:True Handicap:2> [23:10:49.596 N] [RadsAtom] - Error Dialog found, closing dialog [23:10:49.801 N] Stopping the bot. [23:10:49.803 N] Bot Thread Ended. Was this requested? [23:10:51.803 N] Failed to load profile: Path to profile element is not valid; file not found [23:10:57.087 N] Loaded profile [A3 - Inferno] Keywarden Hunt - Profile Starter! [23:10:57.088 N] [GilesTrinity] Note: Maintaining item stats from previous run. To reset stats fully, please restart DB. [23:11:21.294 N] Waiting 10.1 seconds before next game... [23:11:31.392 N] Creating new game, Params: <Act:A3 Difficulty:Inferno Quest:101750 QuestStep:10 ResumeFromSave:False IsPrivate:True Handicap:2> [23:11:32.901 N] Closing error dialog [23:12:04.409 N] Waiting 8.8 seconds before next game... [23:12:13.308 N] Creating new game, Params: <Act:A3 Difficulty:Inferno Quest:101750 QuestStep:10 ResumeFromSave:False IsPrivate:True Handicap:2> [23:12:14.815 N] Closing error dialog any idea about this >.<
Working on a new profile setup that doesn't require RadsAtom, it will use DB to warp on NV5. Just trying to get DB to launch a random game consistently after keywarden kill.
good cause when i ran this i kept getting stuck after i got a key it would warp to town and just stop and stay there.. Thanks for working on it.
