Giving a constructor a build order that the constructor cannot path to (e.g. hover/tank on hilly terrain trying to set up radar/wind, or sea constructors building inland) will result in the constructor getting stuck moving but not making any progress, and not ever showing up as idle. Is there any efficient way to improve this behavior if I'm not the only one experiencing this?
I'm not sure what an ideal fix would be but I'd take any of the following:
- Constructors could clear their queue after not making progress for X seconds, but that behavior will probably look like a bug ("why did my constructor not make this building") and isn't very transparent
- Constructors could show up as idle if they haven't done any activity for X seconds. This is transparent but obviously requires some time to kick in and user attention.
- Have a visible warning when trying to give unpathable orders (maybe that already exists and I missed it!). The UI could be confusing here too, having to distinguish between unbuildable terrain and unreachable terrain.
