Web build doesn't load due to Builds.loader.js 403-ing.
PC build has no safeguards against going out of bounds. (and no means for going back in bounds)
fails to load:
Unable to parse Build/WebGL.framework.js.br! This can happen if build compression was enabled but web server hosting the content was misconfigured to not serve the file with HTTP Response Header "Content-Encoding: br" present. Check browser Console and Devtools Network tab to debug.
top right flower-bridge can't be fixed (attempting to get in range of to the north-side flower causes the camera to focus on the south-side flower and leave the north-side flower outside the view)
Camera should center on player with some deviation to wards the direction of travel. (currently impossible to see enemies coming from the left, and this blindness is even worse while moving left)
True, but an all-conditions check would allow you to store the puzzles as just the conditions, which should
A. increase the amount of puzzles that can be stored.
and B. make it harder to cheat as peeking in the puzzle storage would only reveal what is already visible.
The current version doesn't check if the image produced by the player satisfies all the conditions, instead only checking if said image matches what its RNG produced, causing it to reject completely valid solutions.
It gave that impression though, but that could simply due to how it handles words it doesn't understand. (for example, any sentence that contains the word left is treated as a command to walk left)
There is no safeguard against going out of bounds with the knight. (simplest solution would be to make all-walls the layout the game falls back to when the map's layout isn't defined, that way the knight will never see jumping into an OOB area as valid)