Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

OK, I got the game to bug out hard. SO I went back to exactly 0, 0 and stood there for a while. Then I turned a bit and jumped. I forgot to stop turning to jump so I had to counter my rotational velocity, then the sounds from the atmosphere got really loud, and it kept saying I was collecting things. At first, the game would respond to certain things, then it stopped responding altogether.

OK, this isn't just a bug that resolves itself the next time you enter the game. It corrupted my save apparently.

Oh no! I will attempt to reproduce and investigate. I wonder if the lack of speed limits with RCS Thrusters was a mistake. Depending on the fix it might be possible to recover your save if you haven’t cleared it yet. Beware that my time is limited for the next few days.

I haven't. I am not sure where it's located, apart from possibly being in %appdata%\itch\apps\exo.

If you want to try editing the save data directly, you’d be searching for a localStorage file in there. If you search for the string “exo_game” you’ll find some JSON with a “position” key. I suspect it has an infinite number in it. The programmatic fix I’d add in a hotfix would set them to sane default values like (0, 0, 0) for your coordinates and (1, 0, 0, 0) for your quaternion. You can try that manually if that makes any sense, but do make a backup first.

Other solutions would include building from source and running Electron with developer tools enabled so you can access localStorage through Web Inspector. Or simply choosing New Game from the menu, which will clear your progress but allow you to keep enjoying the game.

(1 edit)

I wasn’t able to reproduce this by moving around but, with the right console commands, I was able to get the game into a similar state which corrupted my position and made it impossible to load my save. So I can issue a hotfix later tonight that will correct this and allow you to safely load into your save without data loss.

I’ve also identified a few items related to rotation that might be the root issue, but I need more time to understand the math and fix. That will be part of the v1.1.0 post-jam update within the next few weeks.

Thanks for identifying this bug, as well as your patience and understanding.

No problem. Speaking of math though, you really never turn to 360 degrees in real life, but you can in game. 360 is like a parallel to 0, kind of like how you never have a time of 23:60 , it just rolls around to 0:00.


I'll pass on building it from source, I hate web development.

Haha! I never thought about that edge case. When you’re facing 359.5 degrees the formatter rounds it up to 360. I’ll throw in a tiny fix for that too. 😂 Watch out for a small patch in a bit.