An idea for an alternate approach could be to insert the logic in ShipController instead. If after ChooseShipTrack the VF_PATHFINDER_LOST flag is set, and the current order is go to depot (and it's not a scheduled order) then select a different depot and try again. It's probably necessary to keep a list of depots already tried (and failed), but it can just be local to the ship controller function.

Of course that won't handle the case of OPF, since that never signals no path found. I would suggest not doing anything about that for now, but maybe make a separate change that keeps track of how far a ship has sailed since it last completed an order, and compare that to the expected distance, and send a warning to the player if the ship appears to be taking too long.

I tried implementing the approach I outlined above, it's probably not complete like this, but it's significantly shorter and touches much less code: nielsmh@fd90477

We recently switched from Jenkins as CI to Azure Pipelines as CI. This means you need to rebase before this Pull Request will pass its checks. Sorry for the troubles!

@nielsmh
I just experimented your approach and it causes stalls during gameplay when there's too many unreachable depots nearby. It calls the pathfinder for everyone of them.

@J0anJosep has already implemented part of what I had in mind for npf, which got into master, and some of the complexity that was on npf.cpp is gone. Unless you mean the other changes...

NoNoCAB v5 (O) 1.7.2.zip
Savegame with 5000 ships for testing

NoCAB v499 (Y), 1.6.1-RC1.sav.zip

Just resolved conflicts

This one appears to be stuck, and reviewers are finding it difficult to providing constructive reviews. Also it appears difficult to be confident that the solutions proposed are correct. On this basis I am closing this one. Thanks for contributing!