That's funky. Not much in terms of API, just using the xml schema for DB, and trinity's dungeon explore. I'll try to see if I can reproduce the error.
The way DB handles KD2/3 is terrible. For a real person, sure, it is the way to go. Doing a Core of Arreat, TP, Rakki's Crossing, TP, Tower of the Cursed level 1 -> Stone Fort is probably the best way to bot quickly for Act 3.
I guess I'll have to implement that then, lol. Let's see, maybe in the next few days I can do this. Work has been keeping me real busy as of recently.
Hope this is still working for everyone. I haven't made many changes to the files or the acts since everything seems to work fine. Life has been real busy lately so I don't get much time to dedicate to D3 or games. If there are any issues, I am still alive, so post them on here.
16:23:45.882 N] ========== NEPHALEM VALOR 5 ACHIEVED ============ [16:23:45.911 N] ========== WARPING TO KEYWARDEN ============ [16:25:55.674 N] Inactivity timer tripped! Leaving game It didnt want to tp i guess Act2
The Keyrun plugin doesn't work with Trinity 1.7.3.1 anymore. Are there updates to the Keyrun plugin? thanks
Hmmmm that sucks. I never even checked out the keyrun plugin, just the xml profiles using it. I doubt I'll be able to fix the plugin issues this week, but someone else more experience is more than welcome to take a look at it.
thx for updating i test it now how can i change the profile to start oasis at nv 4 ? i changed the xml files that he non stop run a2 a3 a2 a3 its becaus i have 70 a1 keys and only need a2 and a3 keys runnig my barb at mp10 edit: i need help , the bot stops and wait till inactivity timeout after warden is death can u add a xml file for runnig only a1 or a2 or a3 ? edit2: ok now i use keyrun plugin and hope he only run a2 and a3 no bugs for me
Glad you figured out the problem. There are plenty of profiles on this site that run individual keywardens (although they might not be named as such). This profile/setup only exists so that all keywardens can be farmed without requiring much intervention.
Hmm for some reason, the bot teleports to any area in act 3 and stucks, he keeps running in circles, or he ports to any wp, then he ports back to town, and he doesnt leave the game... any way to fix this? He does act 1 and 2 just fine.
This is the same problem I am running into Using latest DB, Trinity and keyrun 1.8 anyone know a fix?
Am i the only one who not getting any key after 5-6hrs run? 1. It gets stuck a lot and it just moves back and forth back and forth in attempt to stuck (not by objects or anything it just stay in the middle of the floor and the bot would says it is stuck) 2. It keeps restarting over and over and over when there's not enough NV, or keep dying too many times? 3. It doesnt even bother to start act 1..Mine just open stash > head to act 2 any idea? help please!
[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 The problem is here, loads the keeps 2 warps. instantly loads keeps 3 and then the grid segment happens (im guessing because its not in the right zone - sitting in keeps 1 warp point instead of being in keeps 3) no idea how to fix it