I’m trying to block certain seekers from taking particular routes by using a GUO to set a non-traversable tag across corridors. This is proving problematic when using erosion.
In the beta version (4.3.60) the the erosion tags are replacing the GUO tags, making it passable for the seekers close to the edges e.g.
This seems to behave differently to the non-beta version (4.2.17), where the GUO tags are retained e.g.
Is this an intended change in behaviour?