Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

Okay, so I had this happen a couple times where I set Kerfur-Omega to patrol inside the base (locked doors leading outside) while I slept and when I woke up he was missing but his camera showed he was inside some kind of meat hell. The first time he showed back up outside and deactivated when some other event caused the power to fluctuate (I think this event wanted to deactivate him so it got him out of wherever he was). The second time he just stayed there while the meta-paranoia sound continued and I couldn't save or sleep. I decided to take care of a couple tasks out in the field (just repairing the transformers since they were a little low) figuring there was a chance I would move far enough away from whatever was keeping me from saving or sleeping but the meta-paranoia persisted the whole time. After fixing all three transformers I went to Romeo and tried debug events and saw the skerfuo_Walk_red_C event was active with the object skerfuro_Walk_red_C_2147133520

I looked up the event to see if I was missing something but couldn't find a way to proceed to I used debug scrape. That got rid of the paranoia. Went back to base, found kerfur, and continued about my business until I got a message saying skerfuro_Walk_red_C_2147133520 had encountered some kind of issue and to report it on the bug forum. I don't remember the exact wording of the alert and unfortunately, despite my efforts, didn't manage to catch any screenshots.

I believe the issue is related to the meat hell Kerfur was stuck in. Both times this happened because I told him to patrol the base while I slept and I kept the base doors locked because I don't actually want him to wander far, just try to stop aliens from killing me in my sleep. The in-game day was 41 & 42, I believe or around there. Definitely higher than 38. Hope this is at all helpful.

(+2)

When Kerfur-O is trapped in the meat hell you need to check all the windows in the base. It's not very well telegraphed, if at all, but when you look through the correct one you might catch an entity walking away from it and Kerfur-O will be returned to you. It's possible that the error is caused from scraping the event without completing it as intended.