Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I apparently encountered the same bugs described and shown by vitsum. I made a video of the whole game in which these bugs occurred, in case that may help track down the errors.


My main goal in the game after the graphical bug occurred was to move onto or attack the square with the scrambled visual, so I didn't worry so much about playing optimally, and I made some careless mistakes. The video is sped up to mitigate my somewhat slow decision-making for my moves (2x speed before and 4x speed after the graphical bug occurs). I figure that 1 min. 53 sec. is enough time to demonstrate the bugs, rather than sharing the full 6 min. 17 sec. length of the game at 1x speed.

I used the Mesen emulator. Details about how I created the video are in the video description.

(+1)

Fixed 😄

Thanks for the video, it really helped me track down the problem.

I'm glad that the video helped. Thanks for fixing the problem.

Did it have anything to do with leftover castling code from the prior edition of the game, Chessnovice? That is what the scrambled rook icon makes me think of, especially since the king moved towards the rook with no pieces between them.

nope, this app is completely rewritten. It was an issue with the castling logic.