Gingerbread
New Member
- Joined
- Jul 29, 2012
- Messages
- 171
- Reaction score
- 3
OP now updated with version 1.12 Desolate sands is now less stucky.
So what is the general consensus of Act 2 compared to Act 1 for champion farming?
I did a couple of days comparison between the 2 and it seems to me that due to the higher density of elites in Act1 I fill up with 62/63 rares a LOT faster in Act 1. I didn't seem to die at all in Act 2 so I don't think it's a gear/dps issue. Is it really all about luck and getting some level 62 legendaries that make it worth it? I don't think the higher level 63 drop rate for Act 2 offsets the lower density of champs.
I am still getting a lot of stucks in Oasis (the fifth profile)
I would post a screen grab, but I am usually not around when it happens. I see it in the log though. usually the inactivity timer is triggered.
I was also wondering, other than some pathing, what is the difference between this one and the original gardetto thread?
It doesn't seem to have any randomization as of yet. Please correct me if I am wrong
So what is the general consensus of Act 2 compared to Act 1 for champion farming?
I did a couple of days comparison between the 2 and it seems to me that due to the higher density of elites in Act1 I fill up with 62/63 rares a LOT faster in Act 1. I didn't seem to die at all in Act 2 so I don't think it's a gear/dps issue. Is it really all about luck and getting some level 62 legendaries that make it worth it? I don't think the higher level 63 drop rate for Act 2 offsets the lower density of champs.
[18:17:44.644 D] Waiting for path request to finish...
[18:17:44.738 D] Generating path to UNKNOWN - <1909.145, 705.0721, 158.806>
[18:17:44.753 D] Waiting for path request to finish...
[18:17:44.862 D] Generating path to UNKNOWN - <1909.145, 705.0721, 158.806>
[18:17:44.878 D] Waiting for path request to finish...
[18:17:44.909 D] Generating path to UNKNOWN - <1909.145, 705.0721, 158.806>
[18:17:44.925 D] Waiting for path request to finish...
[18:17:45.018 D] Generating path to UNKNOWN - <1909.145, 705.0721, 158.806>
[18:17:45.034 D] Waiting for path request to finish...
[18:17:45.159 D] [Stuck Handler] We're stuck at <1855.603, 578.8358, 158.829>
[18:17:45.174 D] Navigator.Clear
[18:17:46.698 D] Generating path to UNKNOWN - <1909.145, 705.0721, 158.806>
[18:54:20.374 N] Path with 2 hops received (partial: False)
[18:54:20.390 D] Generating path to UNKNOWN - <980.0387, 3971.514, 110.1>
[18:54:20.405 V] Path with 2 hops received (partial: False)
[18:54:20.405 D] Nav Service path generated.
[18:54:20.405 D] Generated path to <980.0387, 3971.514, 110.1> () with 2 hops.
[18:54:22.184 D] [Stuck Handler] We're stuck at <968.8872, 3972.028, 110.1784>
[18:54:22.199 D] Navigator.Clear
[18:54:23.744 D] Generating path to UNKNOWN - <980.0387, 3971.514, 110.1>
[18:54:23.759 D] Waiting for path request to finish...
[18:54:23.868 D] Navigator.Clear
[18:54:23.900 D] Generating path to UNKNOWN - <980.0387, 3971.514, 110.1>
[18:54:23.931 D] Waiting for path request to finish...
[18:54:23.978 N] Path with 2 hops received (partial: False)
[18:54:24.024 D] Generating path to UNKNOWN - <980.0387, 3971.514, 110.1>
[18:54:24.040 V] Path with 2 hops received (partial: False)
Got a stuck here in the lost caravan
I seem to have a problem with this Act 2 profile. Yes I have the needed plugins, the problem I am running into is that the profile when it reaches the last profile of the complete run it will leave game as it should and remake the game and go right back to that spot in this case Kulle and just kill him then leave the game again. Anyone know a reason for this, I removed Kulle and changed the second last profile to leave game instead I'll see if that works. I have ran Act 1 and 3 profiles the exact same way and they do not have this problem. Thanks in advance.
Edit - Expecting this to be asked, yes I start the profile from START this happens when the run makes a new game it did not reset the profile order or how ever it does this.
how dare you answer my question before i got the chance to ask it!
Serious answer: It sounds like you know what you're doing since you say you've ran A1/A3 before. All three sets of profiles use the exact same tags to continue profiles, and RadsProfileManager handles them in an identical fashion.
So, if you're having this issue there are only a couple potential problems.
1. You've recently started using Anti-idle or some other profile manager which is interfering.
2. The bot somehow got stopped and restarted on the Kulle profile
3. Something is wrong with your Demonbuddy installation, or it didn't compile a setting correctly. Try a fresh DB install and install the plugins from scratch. (this is the most likely problem).
Also the edit on Kulle removal so for is working for me ( only tested for an hour now ) and if anyone else has this problem removing the Kulle profile and making the profile before Kulle leave game once finished.
Thank you for the fast reply with lots of info, it sure made me double check if I missed anything good luck.![]()
It's just a perplexing issue, I'm currently running this profile on my A2 bot and he just killed Kulle and remade the game without any problems.
Another individual posted a similar issue in my FAQ thread (but with A1 profile!) and after going through all the same steps what eventually fixed his problem was restarting his computer.
So, I'm glad you fixed it but I have no idea why what you did worked! (there's no issue with the actual Kulle profile) ;P
It shouldn't enter the ancient waterway at all.just got stuck trying to enter the "ancient waterway"