I think I might have a little idea for the debuggoal command, when it comes to checking a whole passage (e.g. up a stack of crates, along a ledge and then a jump into a window something the like), with several ways leading to the WP specified in debuggoal - but you want the bot to test this one tricky passage instead of just having him walk up the stairs and go to the window from inside the house.
The problems that can occur when debugging such a passage are the following:
1) As mentioned - bot chooses different passage
2) When doing it step by step, bots can fall down somewhere because they tend to move a bit around the waypoint they have reached
That's why I thought it would be nice to be able to tell the bot via which WPs he is supposed to go to the goal node.
Let's say we have waypoints 210 - 214 that are a complicated jump sequence up a roof. Let's say there's also a ladder some yards away that also leads up the roof. And imagine one WP on top of the roof has the number 367 (it doesn't matter, really). Now if I typed in "debuggoal 367", the bot would be likely to take the ladder, when I want him to try the jumps! And if I want to do it step by step ("debuggoal 210", "debuggoal 212" and so forth), the bot may fall down somewhere while waiting for a new goal.
Now if I could enter something like "debuggoal 210 214 367" to tell the bot to go to 367
via 210 and 214, I could force him to take this one route I want to have tested.
And once we're at it, I just remembered the print function of WinWord. What's that got to do with it? Easy: By entering e.g. "2,4-7,9,23-25" you can tell Word to print p. 2, pp. 4 to 7, p. 9 and pp. 23 to 25... I wonder if a similar scheme could be used for the debuggoal command? Then I could fly around in spectator mode, see the numbers and tell the bot EXACTLY which passage to choose... opinions?