Closed mikxingu closed 4 years ago
I'm Closing this issue because the same error occurs on the original source code. As my first goal was to reproduce the project, this is "correct". After the release of the stable build, this could be worked as an improvement. I even have the idea of locking movement before the current movement has been finished.
When moving from one cell to another too quickly, some cells lose their explored properties, and they no longer get explored. This does not happen when I wait for a movement to finish before I start a new one.