Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Later on I did manage to collect 4 souls (actually I had 5 at  one point but had to trap myself to get the 5th). Then I got stuck at - couldn't move.

Do you remember how you got to that location?  I'm guessing you didn't make it there from the map to the left, because that would (should) have permanently recorded your spawn position out of bounds.

My recollection is that I did get there from the map to the left. But I'm not 100% certain.

May have been browser cache issue of some sort. I was able to reproduce it, but only once. Then I restarted the browser to take some screenshots. Now the level to the left behaves differently. Sounds like "out of bounds", as you said. I can still sort of move the character to that location - it goes off the screen and I'm stalled until I hit page-reload. But a) it doesn't load the map in the screenshot, and b) page-reload resets the entire map, including character position, to what they were when I first entered it.
Kinda weird that I was able to reproduce it once - PC was off overnight. But I'm clueless re cache behavior. Maybe I refreshed the page whilst taking screenshots - at the time I wasn't suspecting a cache issue and wasn't paying much attention to that.

I see it now - both the buggy level and the level above it (if accessed from the bottom entrance, i.e. from buggy level) have the ability to exit the right side of map into either a non-existent level ("harmless" game freeze) or into another level in a location without any solid ground, which leads to falling out of bounds into non-existent level even after page reload (because player location is saved from previous map change).

I stayed up too late working on that buggy level, obviously.  I fixed up those levels to protect future players.

Well, you did have the "buggy - you've been warned" message. I see it fixed now.

So apparently the time-stamp on the itch.io-reply notification email was correct. When I saw the time I assumed there was yet another glitch either in my email client or somewhere in the server chain.