(Jip) Willem Wijnia

 Made a debugging tool for `CanPathTo` to make testing easier. There is both a visual representation of the status quo, and the answer (you'd get in code) is visible...

 Example of an air grid, along with a path 😄

      A few more examples of the output of the current status quo

What operation system are you running?

Ah, yes. I can hear it too. Not sure what the solution is yet.

We can not change that from within the game, the solution you provide is likely the best one we have. Thank you for coming forth with it

This has been extensively discussed on the forums, see also: - https://forum.faforever.com/topic/845/battleships-shouldn-t-be-able-to-damage-submarines-with-artillery-fire - https://forum.faforever.com/topic/3041/countering-seraphim-t3-submarine-hunters And there is one large other topic that I can't find. There is a solution available,...

We can add data to the replay by doing a `SimCallback`. Where are the images, I think we should use those

Batching them into a zip would be preferred, I can't properly navigate that link

This is already implemented with #4270 , each unconnected area has a label assigned to it. It is the foundation of the function `CanPathTo`, see also: - https://github.com/FAForever/fa/pull/4270/files#diff-54afb8d1e2391054af22d032f5ee6fad652b7a99d5ec28ff484a907efbd0f74eR34 - https://github.com/FAForever/fa/pull/4270/files#diff-27f81f4cd655fe55438dd405e819b00d616deec749f850daeee0ad0f836e975dR189...