Bot not following path

[somedaysomeday15-byte]

Description

Hello! For some reason my bot has decided to stop following its designated path.

I believe I am using the latest addon version, have used this class profile and path frequently previously without issue. So am a little puzzled why all of a sudden it has stopped working.

The bot cannot seem to move at all, other than when it cycles through the unstuck routine and strafes, moves slightly in a direction. Other than that it does not follow the path, nor does it approach when Approach is triggered in the log.

I saw another thread on this topic where movement keys were the issue. As far as I can tell they are all bound correctly.

Any insight would be much appreciated :)

Addon Version

1.12.1

World of Warcraft Client

World of Warcraft Classic

Reproduction Steps

Load bot normally (initialize, load class and path)
Start bot normally
Bot does not follow the path, even when positioned very near to the path

Last Good Version

1.11.0 However I did not have this issue earlier on 1.12.1

Screenshots

pathingerror.txt

Logs

No response

[somedaysomeday15-byte]

A few more comments on this topic:

• For some reason the pathing issues only seem to occur in Elwyn Forest
• As a test, I tried the bot in Teldrassil on both hunter and warrior, and it had no issues
• All of the above is after redownloading navmesh files (gemini told me this was the cmd to run: powershell -ExecutionPolicy Bypass -File ".\scripts\download-navmesh.ps1" -Era precata)

[Xian55]

Thanks for the log — it has everything needed. Your baked navmesh tiles for Azeroth are missing. Kalimdor's are present, which is exactly why Teldrassil works and Elwynn does not.

What the log shows

The bot itself is healthy: it targets, casts Fireball and loots all the way through. Only route-walking is dead. Across the 16 minutes there are 2292 pathfinder calls and zero successes, each failing in 0.2–0.8 ms — far too fast for a search to have run, so it is failing at endpoint resolution, before pathfinding even starts.

You have no game archives installed, so pathing is disk-only over baked tiles:

[PPatherService] No usable geometry for Azeroth ... Pathing disk-only over baked navmesh tiles
[PPatherService] Navmesh engine ready for Azeroth (disk-only, no game files) - tile cache: ..\json\PathInfo\navmesh\precata\Azeroth\b1473dae

That hash is correct — it matches the CDN bundle. So the directory is the right one; it just has no tiles in it.

I reproduced it with the exact coordinates from your log (<-8766.622, -148.387> → <-8748.561, -169.620>, both inside tile_126_62.dnm) against a disk-only cache:

tile cache	result
tiles present (10590)	13-point route
directory empty	0 points, and not one line of log output

The empty case is identical to your log, line for line.

Fix

Check what you actually have:

(Get-ChildItem "C:\WowClassicGrindBot\Json\PathInfo\navmesh\precata\Azeroth\b1473dae" -Filter *.dnm).Count

It should be 10590. Anything less — especially 0 — is the problem.

Then, from C:\WowClassicGrindBot, note the -Force:

powershell -ExecutionPolicy Bypass -File ".\scripts\download-navmesh.ps1" -Era precata -Force

Without -Force the script skips any continent whose directory already looks populated, which is almost certainly why your earlier re-download changed nothing. Check the navmesh destination: line it prints resolves to C:\WowClassicGrindBot\Json\PathInfo\navmesh.

On our side

This should never have been silent, and that is the real bug here. A disk-only cache returned "no tile" without logging anything, and the engine reported itself ready for a directory holding zero tiles — so the only thing you ever saw was Character may stuck!, which blames the character for a missing file.

Fixed on dev (fab9f92). You will now get, on startup:

[INF] Navmesh engine ready for Azeroth (disk-only, no game files) - 0 baked tiles in ...\precata\Azeroth\b1473dae
[ERR] No baked navmesh tiles for Azeroth in ...\precata\Azeroth\b1473dae - pathing on this continent will fail every request. Download them (scripts/download-navmesh.ps1 -Era precata) or install the client archives so tiles can be baked on demand.
[WRN] Navmesh tile ...\tile_126_62.dnm is not on disk, and there are no game files to bake it from.

It also names tiles found under a different settings hash, since those are invisible rather than wrong and look identical to having downloaded nothing.

Could you post the tile count from the command above? That will confirm it before I close this.

One separate note: [ApproachTargetGoal] Seems stuck! Clear Target. fires when the addon reports the player is not moving after the interact press. Since mobs die and loot fine throughout your log, that is most likely the target already being adjacent rather than a second fault — but worth keeping an eye on once pathing is back.

[somedaysomeday15-byte]

Hey @Xian55 thanks again for all the responses to my questions!

Yes confirming prior to trying the fix the tile count was 10590

After running the second command to redownload the tiles it appears everything is mostly running smoothly again

Not sure if it matters at this point but after my last comment I did notice the bot having pathing issues in Teldrassil too

Unfortunately I am still getting similar pathing errors at times, although much less frequently now. Most of the time a bot restart and /reload seems to fix it though. I will upload another log the next time it happens..

Big thanks for your help

[Xian55]

Gooday, provide logs over these cases so i can get a better understanding what's going on!