I’m actually working on a fix for this already. This message log spamming when the game starts is caused by the functions generating the edge arrays trying to access tiles to the north of the norternmost row of tiles and south of the southernmost row. To prevent this I’ll just have to add a branch that checks that we are not accessing tile indexes that are beyond the bounds of the grid. As you say it does not cause any actual issues, but this sort of message spam is of course annoying. My plan is to fix this before sending the new update to Epic.