Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

The Aching

Horror adventure game in an unsettling other world. · By Hadrosaurus Software

Disappearing text prompt and score (in most recent version)

A topic by Athanasius created Jul 16, 2023 Views: 194 Replies: 2
Viewing posts 1 to 2

Hi.

I'm fascinated by this game, great atmosphere. I really craved for such a weird, bizarre experience and find it absolutely intriguing. However I seem to have run into a bug: This bug seems already have been mentioned here but it's happening to me in the most recent version too. I play the DOS-version of the game under DOSBox. The problem is as follows:

The text prompt and the score on the screen doesn't appear if I load one specific savegame. There is no difference if I skip the intro first or load the game while the intro is playing. In this savegame I'm standing at the graveyard. If I walk back beyond the Strangle Wood section or jump down the waterfall, both the score and the text prompt reappear again. I don't know if this specific savegame is corrupted. This situation happened several times to me. I noticed that the disappearing score/text prompt issue happens mostly in the area to the left of the strangle woods.

Thanks for your help.

Hi, sorry for the delayed response! Yes this is that very issue you thought it was. The current build in dev has the fix but owing to how much we're still fixing and adding, it's taking us a bit longer than we'd like.

In response to your curiosity, it is technically a save game glitch. The engine uses a sort of VM and the save files are more or less save stating the VM. There was a bug in the current release that corrupted a few of the core state flags. Sorry for the inconvenience, but as you seem to have found out hitting certain rooms will force a state correction.

We're glad you've been enjoying the experience in spite of the bugs and hope to have the patch out very soon!

(1 edit)

Hey, no need to apologize! 

Ah now I understand. I thought the fix was already in the current official version. Thank you, I look forward to the release of the update. :)