Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

I have a weird crash where occasionally when the timer runs out and I'm in the middle of a jump, my mouse disappears and I'm unable to press continue so I have to force stop the program. It also really sucks that there isn't a save function.

Saving system is on my long to do list.

Sorry to hear about the crash/bug. I never experienced it while testing. Did it happen more than once? Were you playing in full screen, or windowed? What jump were you using at the time? Were you alt-tabbing to a different window?

Yes it happened more than once. Full screen. The default jump because I didn't realize there were multiple. And probably alt tabbing because I was also watching Twitch on a second monitor and would move my mouse over to chat. Although nothing really seemed to effect it during gameplay. The camera would work fine, but I think what might have happened is the camera would freeze when the timer stopped, but didn't disengage the mouse so it was essentially stuck to the center. A quick fix would be to make the continue button also be pressed by enter or esc.

Thank you for your reply. Getting feedback and hearing about bugs is very important to me. Yes, I can make the continue button to also work on a keyboard key press of some kind for the next version as a quick fix, or have it continue after e.g. 5 seconds on its own. I was unfortunately not able to reproduce the bug myself.

Side note, I was going to work on more things before dropping the next version, but looking at my changelog notes, it's probably enough of fixes and new things to release it. I'm gonna add a fix to the problem you experienced, and do some testing, and probably release new version tomorrow.

Thank you for playing my game.

(1 edit)

Thankfully, after a few hours of playing the new build, that bug isn't popping up. Not saying it can't, but I had nothing happen this time. Although, I did find it odd that on a few occasions, when loading a random seed, a button popped up asking to try a different seed.

That's good to hear. I tried to fix the bug you reported earlier, even though I was not able to reproduce it, and I was wondering if you would experience it again even after my fixes. As for the loading, I mentioned that in my devlog, instead of trying to make every generation work, and allocating more memory, now when the given "problem seed" would take too long, you can just try a different seed instead of increasing the generation time. In theory it should decrease dungeon generation time for "good seeds", and make sure the game doesn't break for lower spec machines.

I expect dungeon generation to get better with more rooms I add in future.