Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(3 edits)

Hi orange,


Congrats on the release of Fear and Hunger. Wanted to give a quick bug report forr V1.0.3. After beating a particular enemy in the room (image) shown below, then attempting to enter the escape menu, the following "Failed to load: img/pictures/_1.png" error appears. Clicking retry will show a loading bar, which promptly returns you to this screen, making this a soft-lock. I've been able to replicate it a few times, so am confident in saying it is consistent between play-throughs. EDIT: on further investigation, it only occurs when the blood golem was summoned mid-fight; is it not being removed from the party at the end of the fight?

On a side-note, am loving the game, but found it very frustrating to complete the task needed to fight the particular enemy that appears in this room (being coy to avoid spoilers). As it is based on having certain party members with you, and I had a party of four prior to entering the area, I found myself having to clear out a party member to make room. This took over three hours purely because I had killed all but two very weak enemies (including the hydra), and had no circles for sacrificing another party member at that point. If possible could I suggest adding another way to remove a character from the party for cases where there's literally nothing left to cull them off with? Perhaps an item like a sacrificial knife, or even just something added to the above area/s, maybe pushing them into the center of this room? It would certainly fit with the area's theme after all!

Hoping to see the updates continue to roll out - really enjoying the narratives so far!

Hey yeah, I saw this on the RiskRim's channel. Really big thanks for finding the source of the bug. This crash has been popping up since the game testing, but I could never pinpoint the cause, because I couldn't replicate the bug myself. Also blood golem probably doesn't sound like the logical cause for this, so I understand that the testers didn't realize this connection. But it's painfully obvious now that you mentioned it. It indeed is the cause.