Wild stab in the dark that might fix this issue. (Fwiw this problem is not caused by the profile, and I can't reproduce it so dunno what causes it) Try the following steps in order. *exactly as written* i) create a new folder on the C: drive called db. Then download version .222 of DB and extract it into this folder. (In the past issues are sometimes caused when db is installed in a folder that's lots of folders deep) ii) create a dir in the db folder you just made called plugins, install a new copy of radsprofilemanager 0.9.0 into the plugin folder. iii) create a dir inside the db folder you just made called Profiles, and d/l and extract an Elderberries Act2 profile set into this folder DO NOT INSTALL ANY OTHER PLUGINS (no not even trinity) iv) start a new game using the belphegor combat routine that comes with db and the bog standard default loot rules and run If this works OK then great, now install Trinity and try again. If this doesn't work then it's a problem with RadsProfileManager, he's currently rewriting it and will hopefully solve this problem. Your other alternative is to use the other profile switcher plugin instead. Beyond this I can't help you with this problem, sorry. I have no clue what is causing it, and I can't reproduce it. The profile is 100% not to blame.
can anyone post a screengrab for this stuck: 13.9.2012 14:42:23: Original Destination=<3454, 3932, -1.02845>. Current player position when stuck=<3456.306, 3933.531, 98.98067> Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a) that looks like a Nav server issue, or some other weirdness, note that it's trying to go to a point that's -1 on the z axis - and there are no points in the whole profile close to those co-ords. Might be DB's built in unstucker causing the problem maybe (?) Edit: I've also just spent about 3 hours running an Oasis test profile to stuck test it. My test hasn't actually got stuck, it has however generated a bunch of stuck positions in the Trinity log, so the logger seems a bit sensitive. If my test run continues to not actually get stuck I'll update the whole profile later tonight.
i think the anoying part is when it always for me it walks in duhlgur oasis. its around x="3318.813" y="4267.752" z="100.2496" (new Vector3(3318.813f,4267.752f,100.2496f)) always get stuck there, walks arround the plant but takes a few xtra seccond. in need i got screenie
I found a problem in most of the files in this profile! After death, we are not teleported to the city - making the bot gets lost.
What exactly is happening to your bot. Sometimes the bot is able to resume from a checkpoint, and does not need to be teleported to town. It shouldn't be getting "lost" though
Maybe this will help? PHP: [11:50:53.388 N] Loaded profile [A2 - Inferno] Champion-Hunting 1.2 Elderberries Profile Starter! [11:50:58.431 N] [RadsProfileManager beta] Been asked to load a new profile, which is Elderberries_MineB.xml [11:50:58.705 N] Loaded profile [A2 - Inferno] Champion-Hunting 1.2 Elderberries(part1b) [11:50:58.705 N] [RadsProfileManager beta] Reset death count to 0. [11:51:00.355 N] Using Waypoint Waypoint-25 Number:2 [11:51:05.129 N] ========== Grid segmentation resetting!!! ============ [11:51:45.608 N] Player died [11:51:45.608 N] [RadsProfileManager beta] You died, reload profile so you can try again. [11:51:45.608 N] [RadsProfileManager beta] Deathcount: 1 [11:51:45.883 N] Loaded profile [A2 - Inferno] Champion-Hunting 1.2 Elderberries(part1b) [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.883 N] Player died, Resetting caches. [11:51:46.884 N] Player died, Resetting caches. [11:51:46.884 N] Player died, Resetting caches. [11:51:46.884 N] Player died, Resetting caches. [11:51:46.884 N] Player died, Resetting caches. [11:51:46.884 N] Clicked revive button [11:51:50.130 N] Player died [11:51:50.130 N] [RadsProfileManager beta] You died, reload profile so you can try again. [11:51:50.130 N] [RadsProfileManager beta] Deathcount: 2 [11:51:50.407 N] Loaded profile [A2 - Inferno] Champion-Hunting 1.2 Elderberries(part1b) [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches. [11:51:51.407 N] Player died, Resetting caches.
You'll have to excuse Dookiepie, he's a little slow and doesn't know what he's talking about. Can you explain your issue to me again? All I see from the log is that you died. I don't know what your bot actually did.
Lets try narrow this down: 1. So you died, and ressurected at a checkpoint 2. Instead of trying to move on from the checkpoint, the bot teleported to town. 3. Did the bot then take the waypoint and re-start the area you died in? 4. Or did something else happen? (the getting "lost" you mentioned?)
1. Died 2. Ressurected at a checkpoint 3. DB thinks, thinks, thinks, thinks,... 4. Stary walking (I think it unstuck started) Do not teleported to the city.
Sounds like DB/the nav server just got confused. My bot is able to die and resume without any real issues, so I think what you experienced was just a fluke.
Maybe you're right. Your other profiles function normally Act 1 and Act 3 (I've never had a problem with them). Here (Act 2) something began to fail in.
Need a bit of help, not with the profile but with the Belp combat routine.. I am DH and need to have my Gloom cast a little earlier then set 0.5% of HP. Any advice, tried to change the 0.5 to 0.7 but didn't seem to work.
devious21, again.... But now i record screen. https://vimeo.com/49504835 <- pass "Champion hunting from CIGGARC" What's going on?
I removed the If Not in town TP to Town and then take waypoint back to the same place you started from from most of the profiles in Act2. It doesn't need it and slows the whole run down by quite a bit. I tested it a bunch before I released it and my bot didn't get lost. My bot rarely dies in act 2 though and it looks like I have messed up with some formatting when I recompiled everything at about 2am last night, sorry. Attached is the 1.2beta zip with all the profiles fixed, they should all work now and recognise where they are when you revive after dying. I've tested Oasis to make sure that works as designed, and made similar edits to all the other profiles. I'll fix all the variants in the whole pack shortly and update the OP with a working version. Edit - OP udpated with 1.2.1beta release, bug should be fixed now.
Hello all, I just purchased the demonbuddy and am a complete noob when it comes to this stuff so I am sorry if I'm missing something obvious; when I am running this and an arcane beam is thrown directly below my feet, my character makes no attempt to move out of the way whatsoever and dies. Also, if there is a pack of 2 or 3 with firechains and they have surrounded me and/or I am standing in the chain, the bot also just stands there until dead, or some other effect causes it to move out of the way. If there is any way to fix this I'd really appreciate the help, if not, oh well this is still awesome! edit: Only very rarely does he stand in fire chains, it only seems to be a problem with fast mobs. I guess once it gets surrounded there isn't much it can do.