[Act 2][Inferno]Champion hunting from CIGGARC

How does it work with Drelog without manually choosing profile every time or else it won't load next file =( please help

 

i ran it over night and this is what i logged:

Code:

9/15/2012 7:12:25 PM: Original Destination=<1420.755, 4012.192, 110.2273>. Current player position when stuck=<1216.138, 4058.632, 110.2119>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part6)
9/15/2012 7:40:35 PM: Original Destination=<3109.62, 4552.182, 100.1>. Current player position when stuck=<3200.377, 4643.355, 97.89358>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/15/2012 8:01:55 PM: Original Destination=<1114.889, 1427.6, 184.4915>. Current player position when stuck=<1153.131, 1446.34, 184.5675>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part2a)
9/15/2012 8:26:31 PM: Original Destination=<1420.755, 4012.192, 110.2273>. Current player position when stuck=<1216.135, 4060.318, 110.2119>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part6)
9/15/2012 8:51:27 PM: Original Destination=<472, 467, 0.4586937>. Current player position when stuck=<468.172, 476.3507, 0.3773427>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/15/2012 9:57:34 PM: Original Destination=<4215, 4465, 94.06491>. Current player position when stuck=<4168.392, 4519.933, 100.5042>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/15/2012 10:05:37 PM: Original Destination=<2778.765, 4398.195, 100.1>. Current player position when stuck=<2715.131, 4464.274, 101.6243>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/15/2012 11:44:09 PM: Original Destination=<1420.755, 4012.192, 110.2273>. Current player position when stuck=<1216.167, 4058.607, 110.2119>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part6)
9/16/2012 12:02:38 AM: Original Destination=<1649.207, 562.4968, 158.8059>. Current player position when stuck=<1667.314, 605.9636, 158.8059>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part4a)
9/16/2012 1:18:01 AM: Original Destination=<1842.671, 836.5759, 169.8601>. Current player position when stuck=<1953.555, 832.9456, 170.1289>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part1b)
9/16/2012 2:18:58 AM: Original Destination=<2074.029, 1456.919, 207.6511>. Current player position when stuck=<1981.178, 1506.216, 204.519>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part7)
9/16/2012 3:21:31 AM: Original Destination=<3833.902, 4520.234, 100.1>. Current player position when stuck=<3868.823, 4599.044, 100.0591>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/16/2012 3:26:26 AM: Original Destination=<3110.202, 4551.176, 100.1>. Current player position when stuck=<3200.309, 4639.688, 97.92368>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/16/2012 3:28:33 AM: Original Destination=<2778.997, 4398.655, 100.1>. Current player position when stuck=<2715.2, 4464.657, 101.6243>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/16/2012 3:33:52 AM: Original Destination=<196.8874, 3846.79, 110.1>. Current player position when stuck=<151.2747, 3738.601, 110.2182>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part6)
9/16/2012 3:38:12 AM: Original Destination=<1420.755, 4012.192, 110.2273>. Current player position when stuck=<1273.746, 4131.376, 110.1491>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part6)
9/16/2012 3:42:35 AM: Original Destination=<500.9792, 287.9905, 0.04028055>. Current player position when stuck=<491.1311, 286.254, 0.04028055>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part7)
9/16/2012 3:47:13 AM: Original Destination=<462, 257, -0.05968857>. Current player position when stuck=<488.3022, 283.2671, 0.04028228>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part7)
9/16/2012 4:31:10 AM: Original Destination=<1845.495, 836.7813, 169.8601>. Current player position when stuck=<1956.135, 828.3318, 170.3415>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part1b)
9/16/2012 5:03:49 AM: Original Destination=<122, 77, 1.045043>. Current player position when stuck=<116.6043, 143.1592, 0.3859835>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part8)
9/16/2012 5:05:34 AM: Original Destination=<1843.258, 834.0792, 169.8601>. Current player position when stuck=<1938.711, 819.047, 172.4345>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part1b)
9/16/2012 5:25:14 AM: Original Destination=<472, 467, 0.4586937>. Current player position when stuck=<468.1852, 476.2541, 0.3773427>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/16/2012 5:39:44 AM: Original Destination=<2033.937, 1051.028, 170.4123>. Current player position when stuck=<1033.873, 3582.527, 110.0196>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part7)
9/16/2012 6:04:30 AM: Original Destination=<2777.88, 4398.979, 100.1>. Current player position when stuck=<2715.373, 4464.556, 101.6243>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/16/2012 6:39:20 AM: Original Destination=<3109.473, 4552.039, 100.1>. Current player position when stuck=<3216.115, 4659.23, 97.34128>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/16/2012 6:48:04 AM: Original Destination=<1420.755, 4012.192, 110.2273>. Current player position when stuck=<1216.271, 4060.29, 110.2119>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part6)
9/16/2012 6:54:09 AM: Original Destination=<1843.171, 837.4866, 169.8601>. Current player position when stuck=<1938.403, 819.0061, 172.443>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part1b)
9/16/2012 7:02:09 AM: Original Destination=<1389, 960, 174.4399>. Current player position when stuck=<1387.584, 928.6268, 183.0867>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part3b)
9/16/2012 7:08:50 AM: Original Destination=<4168.785, 4563.433, 100.1>. Current player position when stuck=<4158.785, 4563.433, 100.1>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/16/2012 7:12:56 AM: Original Destination=<472, 467, 0.4586937>. Current player position when stuck=<469.6237, 474.5863, 0.3882667>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part5a)
9/16/2012 7:26:53 AM: Original Destination=<1420.755, 4012.192, 110.2273>. Current player position when stuck=<1216.591, 4058.461, 110.2119>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part6)
9/16/2012 7:41:20 AM: Original Destination=<1337.263, 686.1482, 174.5399>. Current player position when stuck=<1269.983, 579.5401, 174.5399>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part3b)
9/16/2012 8:30:34 AM: Original Destination=<986.7629, 3646.21, 110.1>. Current player position when stuck=<1064.431, 3690.719, 110.1542>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part6)
9/16/2012 8:41:03 AM: Original Destination=<2259.514, 1448.932, 207.4762>. Current player position when stuck=<2361.239, 1331.412, 207.8036>
Profile Name=[A2 - Inferno] Champion-Hunting 1.12 Elderberries(part7)
9/16/2012 8:47:08 AM: Original Destination=<322, 290, 0>. Current player position when stuck=<1796.313, 786.3806, 173.1594>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part1b)
9/16/2012 9:24:23 AM: Original Destination=<1813.004, 1394.422, 170.1791>. Current player position when stuck=<1831.021, 1261.142, 170.8809>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part1b)
9/16/2012 10:10:23 AM: Original Destination=<1315.614, 1037.258, 174.5399>. Current player position when stuck=<1216.198, 931.1991, 174.5399>
Profile Name=[A2 - Inferno] Champion-Hunting 1.2 Elderberries(part3b)

 

thanks for the logs, but none of those are actual stucks. Trinity creates stucklog txt everytime the built in Trinity unstucker code is used. It gets used often as Giles has set the trigger to be very sensitive (it has to be because of the way DB works) Everytime your character bumps into a chest or has a minor pause in a route anywhere Trinity unstucker leaps into action.

If you see very similar co-ords crop up very often in these logs then that's probably a stuck, and I ask people to post the stuck log when reporting a stuck as it's easier to copy the last couple of lines of Trinity Stuck log than it is to make a screengrab. I am 95% sure at this point that there are no profile stucks in the 1.2 Act 2 code. These logs have mostly different co-ords listed, which is normal.

Try observing your bot running any profile for an hour to see if it gets stuck, and then after that hour go read the stucklog Trinity has created, it'll be longer than you think.

 

Nope, no bugs this time. Just read through the des sands code and it's doing what it's supposed to. Just run a test and died, mid map, my monk respawned and continued like it should. Working as intended.

 

If you look in the config settings for RadsprofileManager you'll see two sliders you can set. The top slider is how many times to reload each profile after dying. The bottom slider is how many times a profile reloads before it gives up and logs out and starts again from the beginning. If you hit "Recommended Defaults" it sets the top to 2 retries and the bottom to 3. Just make the bottom number bigger than the top number and it should be fine.

 

No idea sorry. The profile code is fine. At the start of the Kulle profile section there is a <While> Loop that says if the questID is x and the StepID is y then use the waypoint to go to kulle. Once you get there the quest StepID advances and there is another <While> loop that says walk to here, skip the cutscene, and turn on combat (to Kill Kulle).

Whats happening is that DB for some reason isn't recognising that it's at questID x and StepID y when it loads the profile in (it should do the START HERE profile tells it to load a game at that specific quest/step (which happens to be the "soulstone chamber" quest from Act2)) so it wonders aimlessly looking for these co-ords (x="95.97552" y="56.55413" z="0.1000037") when those correspond to the ZK map and it's currently in Town.

While I'm pretty sure this is what's happening to you, I do not know how you can fix it. Re-installing DB into a different folder, (ideally C:\db ) is the best advice I can offer.

 

Thank you.

 

Desolate sands... It does a big loop, goes back to start and does it again.

 

Act 2 - release 1.22 is now finished - download from OP

Edit: OP updated with minor improvement to pt 3b to try to reduce stucks caused by avoiding bees and spot a potential extra champ pack on this map.

 

Gonna give 1.22 a test run before leaving for work. Will leave it on for probably 16 hours or so, if anything major happens ill let you know.

 

great job really appreciate how you edited code, will help so some of us can get an understanding of how the scripts work so we can write our own

 

New DB .227 supports "Exploring random dungeons and dumping minimap markers should work again". This gives support random dungeon navigation?

 

Has anybody counted on average how many elites there are on this act 2 run?

 

try it and see for yourself - use the VOA experimental set. If you don't want to watch your bot for all that long just load in the DesSands part and as soon as your hero finds VoA he'll go and try and explore it (and likely get stuck within it inside of 6 minutes.

tl:dr - no it's still broken, it's being worked on I'm told and there will be another DB update "soon". How soon is anyones guess.

 

I haven't but you normally get 5 NV by the time you hit part 3. If you want density of elite packs and speed and ease of farming keep running act1. However you get more ilvl 63's in act 2 and you get higher level legendary items.

Act 2 is better than Act1 Act 3 is better than Act 2. When we can run the ZK random areas - then we're talking...

 

I have some issues when Dieing at ZK when he spawns hes in the terminus and gets lost.... he never goes back and kills ZK or ports out.... I was stuck running back and forth for 7 hrs last night...


was using 1.22

 

Anyone know why my bot seems to dc after 2-3 hours of running this profile? Should i be using a certain relogger? thanks for any help in advance

 

I notice for the Desolate Sands this profile occasionally goes back to the beginning and starts over completely. I've seen it happen 2x when it wasn't stuck and one time when it was. Otherwise pretty flawless profile from what I've seen. Definitely an upgrade from the previous one. Donating now. =)

 

For some reason after the first run, it kills kulle and then load again the kill kulle profiles in endless loop. Any1 experiencing the same issue?

 

In all the time I've been running this I must have never died at ZK :7

Just added in an extra While loop to ZK profile to catch the times you do die and walk back to kill Boss for another attempt. Will update OP zip soon.

Replace Elderberries_Kulle.xml with the file attached and it should all work fine.