No path found
 

When we receive the message "Waypoint Problem! No path found!" - it's possible to add exactly number of the first waypoint causing this problem?
I know - after "waypoint check" I'll find this after fixing some another problems, but maybe this is not so much difficult to implement in code and for waypointers maybe can little help...

Re: No path found
 

good idea!
it's a rather simple thing so I'll let this for the other coders to implement...

Re: No path found
 

Wow, yes! That's indeed a good one! Not that 1337 waypointers like me had ever had this problem *cough* *cough* Hey, who just said "filthy liar" ? ;) Seriously, this one can help a lot, especially on cs_maps where you sometimes have to be quite restrictive with FL_NOHOSTAGE...

Re: No path found
 

yes......very good catch KWo :)

Re: No path found
 

this is still driving me nuts :(

Re: No path found
 

The current solution for this problem You can read here.

Re: No path found
 

as far as i rememeber when editing waypoints and running check it should report which waypoint is broken (so you can use the command to go there and fix it)

anyway, it would be nice if the
Waypoint Problem! No path found! contained the waypoint number

Re: No path found
 

You don't need that number since when You are trying to save pwf file with broken paths - it teleports You automatically to the first broken connection - to let You fix it.

Re: No path found
 

oh, i was editing waypoints in 2.5 (yea long time ago :D)