Project

General

Profile

Bug #1396

Navigation Issue

Added by LostOne over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
vbulletin_issue_id:

Description

Been trying to get Bilgewater Falls quest file to run reliability.  After spending some time on this I’ve started to see some consistency with a navigation “bug” that I first noticed in The Hidden Caldera. When the quest bot is in the middle of a navigation path it will call for a full stop due to aggro detected in the CheckForCombat function. Ogrebot takes over and kills the aggro. Now it is time to resume the current navigation path. This is the point that I see the issue. The very first move to resume the current navigation path will point in the correct direction but the bot will overshoot the location. Usually I end up in the water or humping a wall. It will eventually stop but you will be off target by a good 15-30 meters.

Observations that might help….

I only see this happen when navigation is stopped due to aggro in the middle of a path. This zone file has lots of short individual navigation moves. If I get aggro after a navigation path has completed and before the next one starts it works perfect… no issues at all.

This zone file also has lots of navigation “paths” that just have a single point in them. So I’m not sure if that might be part of the issue. Often you will have a long move from point A to B (length of a ramp) with no locs between. If you are stopped due to aggro on your way to B… something might be up with how it picks the loc for resuming navigation. Does it actually resume to the point it was on before aggro or does it attempt to increment to the next one (which doesn’t exist in this example).

This seems to happen less frequently if I make sure to take down all movement buffs and run at 0% speed.

Also available in: Atom PDF