[Release] Demonbuddy - Glorious Monday build (#252)

Some profiles have their waypoint a bit too far from the door, and have a "pathprecision" set to 10 for the moveto directly before the useobject. This is *BAD*. It tells DB to consider the "moveto" as "successful" when it's 10 units away from the door - and some routines have set the waypoint to the door itself to already be "Only just in range".

Try finding any moveto points before the useobject commands, and if they have a high pathprecision, lower it to 1 or 2. The waypoints themselves may even need shifting to be further into the doorway entrance, but the pathprecision fix is probably going to fix most. This is generally just from getting a little too quick & easy on the copy-pasting, and who can blame anyone for that, those moveto commands get spammy fast!

 

Nesox,
Cleared the CompiledAssemblies Folder, started it again, walked right to door and opened. will keep testing but if everyone can delete the folder and try again
so we can get more accurate results.

 

I did post after that stating could it be box radius's as if u move it by hand closer it does actually go into the doors. fingers crossed

 

so how to fix that profile ?

 

Ctrl+f "useobject". You find this line;
<UseObject questId="1" stepId="1" actorId="176001" isPortal="True" destinationWorldId="81019" x="154.5878" y="457.2349" z="1.39289" />

Immediately above that, you see this line;
<MoveTo questId="1" x="158.6004" y="459.7886" z="0.2451034" pathPrecision="10" />

Change the 10 in pathprecision, to 1 or 2, save, reload profile - that should fix your problem!

You will need to do for skycrown, and battlefield - and any other profiles you find it happening on. Profile/routine makers need to ensure they do this themselves for any other routine/profile releases too - remind them to get close to the object before trying to use it, for safety. Pathprecision shouldn't be over-used

 

Nesox can you please add displaying paragon exp/hour please?

 

Giles,
yeah its not profile related. i think its to do with the navigation server. as i was nowhere near a door standing in the middle of nowhere with a movetotag and precision 1. can we add debug code so it shows if its unable to contact server or something?

 

After some looking i found the reason for the bot standing around, 250 and Giles Trinity Unstuck do not get on lol disabled Trinity unstuck and it instantly moved and finished profile

 

yea even though the db unstucker has some weird lag when requesting after being stuck.. it works better than trinity unstucker for now

edit: why does random dungeons always freeze/stutter?

 

Same issue as used to happen to the old Act1 profile trying to get through the door to the butcher area.

plugins Giles Trinity 1.5.2, RadsAtom1.2 DB .250 (fresh install into a new folder) profileset [A3 - Inferno]Champion-Hunting 1.2.5 GangnamStyle(ciggarc latest version)[Battlefields]

this test run completed the profiles up to killing cydea normally. Once it got to the Battlefields profile the MoveTo points normally take the bot through the arreat gate and onwards. However on this run the navigatio pathed it to the top of the orange door where it proceeded to stutter back and forward directly above the door, similar in appearance to the Butcher Door stuck in our old Act1 profile that was a random navigation problem.

Log attached (stuck occurs around timestamp 23:14)

EDIT: some further investigation. I think this is actually an addon problem and not a DB problem. Profile works fine with a different profile switcher and also works fine with standard DB xml tags and only GilesTrinity enabled. *not* a DB issue, but really odd nonetheless.

EDIT EDIT: Now I can't reproduce this at all. Maybe a nav server quirk that has resolved itself (?)

 

Another bugged version... wtf...?

 

What the fuck are you doing with this?

 

Sticking to 246, lol

 

Wow, every time there comes a new version of DB something is going wrong.
I am running the same two or three profiles for over about two months now, and with any new DB version - there are problems.

Now my BOT sells all the items - the best rares and even legendarys, and it doesn?t loot gold !!
Can anybody tell me why, because my rules and settings are correct and he should do it right.

Any ideas, or is it the new version ?
Thx for the help in advance.

 

I'm not sure how I can accurately say this but the random dungeon is kinda dumb, he explores all the areas but if he misses something he never goes back to it often leading him just stand somewhere in the corner because he couldn't find his way out. Is there anyway to put a time limit like if he doesn't finish a zone in 5 minutes portal to town and move to the next profile?

 

does anyone have a link to 146 because this just sucks. Keep stucking all the time on this version

 

This build seems to be running solid for me so far, running latest Trinity, RadsAtom, and latest Ciggarc Profiles.

Hopefully the crashing issue I was having with the last few versions has gone away, so far so good.

 

Its nice that the bot goes into doors now, but there is something wrong with either the nav server or pathing as my bots stopping in the middle of open areas and not moving
logs out and repeats the process.

Iv attached my log right at the bottom you will see it logging out.

 

WTF is this shit? My bot wont even walk through a fucking door now.

 

turn giles unstucker off.