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

New Release

R

raivin

Member
Joined
Aug 4, 2012
Messages
74
Reaction score
0
i think its not the DB that is causing stuck..

maybe we need a new profile


cause the old profile we're using is no longer compatible with the new release...
 
Last edited:
.250 is now working fine..

i like the new change that it stays away from the molten explosion before looting items :)
 
raivin said:
.250 is now working fine..
i like the new change that it stays away from the molten explosion before looting items :)
Click to expand...

Just for clarity sake, that "change" is - well, let's just say - I guess you're using the Trinity plugin right? It waits for avoidance to vanish before looting within the avoidance zone after a fight ;)

You can see a full list of everything Trinity is doing for you here;
[url]http://www.thebuddyforum.com/demonbuddy-forum/plugins/giles-plugins/71709-why-use-trinity-feature-list.html[/url]

If you're a little bit bored, it's worth taking 5 minutes to read through, rather than just blindly using plugins without knowing what they do! :D
 
Guys this is some nav servers issue. I am using older version, 2.22 db and 1.4.4 trinity. Worked great till last night. Tonight they get stuck in bfields. Its problem with the nav servers afaik, had nothing todo with db/trin version.
 
agreed. I am using .246 and fully updates act 3 champion profile with giles trinity and it gets stuck / idles in battle fields. I believe something is going on with DB itself. we'll have to wait and see what devs say or update.
 
The Battlefields profile has a set of moveto's that are over 330 distance apart, forcing very large nav-server hits. It needs far more waypoints. If it had more waypoints (shorter distances between the waypoints), it would not be relying on the nav-server. Here's a sample log from my test-Trinity version that is monitoring these nav-server causing moveto's;

Profile Name=[A3 - Inferno]Champion-Hunting 1.0 Silhouettes - Battlefields
'From' Waypoint=<3959.794, 851.3557, 0.1000001>. 'To' Waypoint=<4209.848, 621.9036, 0.1>. Distance=340.1581

^^ Those two waypoints need more waypoints inserted inbetween to avoid the large nav-server hit there. There is also a nav-server hit at the top of a staircase in Rakkis crossing, caused by pathprecisions being too high for such a narrow area. I have posted a fix for that staircase here;
[url]http://www.thebuddyforum.com/demonbuddy-forum/plugins/giles-plugins/71845-request-nav-server-idling.html#post738336[/url]
 
Bot doesn't move at all when it uses waypoint and there are moves around him
 
GilesSmith said:
The Battlefields profile has a set of moveto's that are over 330 distance apart, forcing very large nav-server hits. It needs far more waypoints. If it had more waypoints (shorter distances between the waypoints), it would not be relying on the nav-server. Here's a sample log from my test-Trinity version that is monitoring these nav-server causing moveto's;

Profile Name=[A3 - Inferno]Champion-Hunting 1.0 Silhouettes - Battlefields
'From' Waypoint=<3959.794, 851.3557, 0.1000001>. 'To' Waypoint=<4209.848, 621.9036, 0.1>. Distance=340.1581

^^ Those two waypoints need more waypoints inserted inbetween to avoid the large nav-server hit there. There is also a nav-server hit at the top of a staircase in Rakkis crossing, caused by pathprecisions being too high for such a narrow area. I have posted a fix for that staircase here;
http://www.thebuddyforum.com/demonb...845-request-nav-server-idling.html#post738336
Click to expand...



i agree with this..
another way is to put more waypoint in between your profiles...
 
pretty sure they know about it - hope it can be fixed in a timely manner - still have plans on buying more bots so dont stop the good work!
 
babosasa said:
+ battlefield is causing lots of afk and stuck
Click to expand...

For those having trouble with .250 and battlefield..

look for
Code: 
			<MoveTo questId="1" x="126.4189" y="358.7215" z="0.1824233" pathPrecision="1" />
			<UseObject questId="1" actorId="176001" isPortal="True" destinationWorldId="95804" />

change it to
Code: 
			<MoveTo questId="1" x="126.4189" y="358.7215" z="0.1824233" pathPrecision="10" />
			<UseObject questId="1" actorId="176001" isPortal="True" destinationWorldId="95804" interactRange="20" />

That is only if you get stuck in the outer town part not taking the "portal"..
 
You must log in or register to reply here.
Back
Top