[image]

Kind of hard to answer this all via my cellphone.. But looking at the code:

https://github.com/EQEmu/Server/blob...ne/pathing.cpp

	int MaxNodeID = Head.PathNodeCount - 1;

	bool PathFileValid = true;

	for(uint32 i = 0; i < Head.PathNodeCount; ++i)
	{
		for(uint32 j = 0; j < PATHNODENEIGHBOURS; ++j)
		{
			if(PathNodes[i].Neighbours[j].id > MaxNodeID)
			{
				Log.Out(Logs::General, Logs::Error, "Path Node %i, Neighbour %i (%i) out of range.", i, j, PathNodes[i].Neighbours[j].id);

So if you look at your log errors the number at the end (just before out of range) should be less than the version header count which is 1518 nodes.. I am not fully sure how you pulled this off did you start your own path file or use mine?? Cause I haven't seen these errors before

Pathing files do require lots of planning or at least getting the full set of nodes up you think you need, process however many times to save during that endeavor after you can load the nodes up and if you need to add one here and there manually to make pathing more smooth I add and connect additional nodes manually.


Honestly I never removed nodes so maybe that has a bug..? I always add nodes I plan to keep and disconnect to other nodes I don't like them making

Also yes nodes don't have to be connected to be used individually but it can definitely make them prefer a path by connecting the nodes.