Has anyone developed a reliable way to detect the edge of the map with the automapper? There may be no way to do this, though I’ve attempted with various combinations of StrictEmpty being set.
Basically my problem is that when I use StrictEmpty the outside of the map (the void) seems to be detected as an infinite set of empty tiles. This means if I want to ‘edge’ the map, some sides get flipped the opposite direction. The desired behavior is that the ‘void’ outside the map is ignored.
I’ll show you what I mean
Region + Input (StrictEmpty: true)
Region + Output
Perimeter input on Top of Map
Perimeter input bottom of map:
I can see the bottom is perfectly fine (because that rule ran last)
The top is facing the wrong direction:
The outside of the map seems to be counting as a ‘blank’ tile, and I am not sure how to make it not count as anything. I also noticed it counts a really any number of tiles. if I try to make a rule that maybe checks for many blank tiles preceding, or following the target tile, the perimeter still is detected as any number of those blank tiles. I mean a rule like this:
Does not seem to matter. The ‘outside’ doesn’t count as ‘one’ blank tile, it seems to behave the same way each time, as an infinite number of blank tiles.
Is there a way to avoid this behavior, and either explicitly target the perimeter with its own rule, or explicitly ignore the void beyond the perimeter so that it doesn’t affect the pattern matching.
Here’s a larger image to further describe the issue
based on my rules i would expect the leftmost circle to be black (not perceive the outside as ‘blank’), as well as the top-left. the third circle closer to the center is just the image above, where the tiles are flipped backwards. These are all related to the root cause of the outside of the map being detected as n-number of blank tiles.