What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[A3 - Inferno] Champion Hunting (Updated Post)

Attachments

  • Безымянный.webp
    Безымянный.webp
    26.4 KB · Views: 59
I see a problem here:
After Cydaea ports out directly after killing the heart and starts next profile. I don't know how it is supposed to do Azmodan then later, without getting the Arreat Waypoint before porting out.
 
Last edited:
saved it over the file, got stuck again, didnt work :/


EDIT: Dont think i reloaded DB after i changed it, just reloaded and it ran battlefields fine and tele'd out and started next part, so think your fix worked.

Thanks again :)
 
Last edited:
devious21 said:
Post a screenshot with the DB window again if you can (using the new profile i posted)
Click to expand...

edited my last post, didnt reload DB after i changed it, just ran battlefields fine now (after reloading DB) worked fine, ill keep you posted though :)
 
funker said:
any idea with my screenshot?
Click to expand...

No idea, Giles should have unstucked you there easily.
I just ran through tower of the damned like 9 times without getting stuck there so I'm not sure what caused it.
 
funker said:
i woke up at 7 am and bot was standing there like 4 hours >_<
Click to expand...

That doesn't make much sense, an inactivity timer *should* have kicked you.
If it didn't, it means you're were in one of the "client-side nav blackspots" meaning DB is trying to use client-side navigation, but there is a hole in the map it's using, so it does nothing. And DB built in NO safeguards, and plugins cant even pulse. I've heard that it's fixed in the new DB test version but who knows
 
funker said:
i have inactivity timer zero (0) its wrong? :D
Click to expand...

You should have DB inactivity timer set at 0, ONLY IF you are using radsatom inactivity timer.
If you're not using radsatom inactivity, i'd put the DB one to 2 or 3
 
i also have 0 at radsatom
fail?
should i make 2 or 3 min in radsatom? :D
 
Last edited:
so for absolutely clearence

inactivity timer will kicked me of current game because of doing nothing ( buffs refresh every 3-5 mins)

and bot will start new game right?
there are a lot of information to know for botting right ugh...
 
funker said:
so for absolutely clearence

inactivity timer will kicked me of current game because of doing nothing ( buffs refresh every 3-5 mins)

and bot will start new game right?
there are a lot of information to know for botting right ugh...
Click to expand...

the DB inactivity timer will kick you out of the game

RadsAtom inactivity timer will load the next profile in the set (so you at least stay in the same game!)

both of them get tripped if you're chillin' in the same spot for whatever you set them to
 
Im not sure if you read my post since it got burried on page 7 so im going to quote myself :P

wascina said:
After watching my bot run for 2-3 days and getting stuck several times everyday i think i know whats the main problem. Almost everytime my bot was stuck is when he was chasing a goblin or some other priority mob and then he tried to get back on the path. Except instead of navigating like before the chase, the bot was just clicking in the last "standard" checkpoint without cheking where he is/was or should go next.
Click to expand...

Happened again few minutes ago, bot chases goblin then after killing him he tries to get back on the path by moving directly to the last "checkpoint" on the path. Im not sure if simple fixes can remedy that and also running your test profiles will rarely reproduce the same situation since the goblin spawn is so random.
 
My bot got stuck on the top of the fort @ battlefields, where the resplendent chest spawns or the guards who get attacked by reviled are.

Since radatom inactivity timer is broken I disabled it and DBs inactivity timer. And gile's unstucker didn't trigger. So I stood there fore a good 5 hours.

The log says the following over and over.

[10:58:52.598 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:52.618 D] Waiting for path request to finish...
[10:58:52.638 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:52.658 V] Path generation failed! Couldn't find valid start point!
[10:58:52.658 D] Could not generate path!
[10:58:52.698 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:52.698 D] Waiting for path request to finish...
[10:58:52.738 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:52.738 D] Waiting for path request to finish...
[10:58:52.798 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:52.818 D] Waiting for path request to finish...
[10:58:52.838 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:52.858 D] Waiting for path request to finish...
[10:58:52.898 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:52.898 D] Waiting for path request to finish...
[10:58:52.938 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:52.938 D] Waiting for path request to finish...
[10:58:52.998 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.018 D] Waiting for path request to finish...
[10:58:53.038 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.058 D] Waiting for path request to finish...
[10:58:53.098 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.098 D] Waiting for path request to finish...
[10:58:53.138 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.138 D] Waiting for path request to finish...
[10:58:53.198 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.218 D] Waiting for path request to finish...
[10:58:53.238 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.258 D] Waiting for path request to finish...
[10:58:53.298 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.298 D] Waiting for path request to finish...
[10:58:53.338 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.338 D] Waiting for path request to finish...
[10:58:53.398 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.418 D] Waiting for path request to finish...
[10:58:53.438 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.458 D] Waiting for path request to finish...
[10:58:53.498 D] Generating path to Stairwell above Foundry-03 - <3991.993, 590.3889, 20.1>
[10:58:53.498 D] Waiting for path request to finish...
Click to expand...
 
wascina said:
Im not sure if you read my post since it got burried on page 7 so im going to quote myself :P



Happened again few minutes ago, bot chases goblin then after killing him he tries to get back on the path by moving directly to the last "checkpoint" on the path. Im not sure if simple fixes can remedy that and also running your test profiles will rarely reproduce the same situation since the goblin spawn is so random.
Click to expand...

If this happens, Trinity Unstucker or another unstucking program will help to jar your bot loose to (hopefully) the next spot. If not, then RadsAtom will kick in and the inactivity timer will be hit and the next profile loaded. If you're still unhappy with that, Giles Trinity has a setting for Goblin priority. If you set it to "Ignore" you'll just walk past the buggers.
 
I'm having an issue with the inactivity too. my bot stops running when it's tripped
 
You must log in or register to reply here.
Back
Top