Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Dungeon: Keep Her

Create and defend your dungeon from pesky invaders in this 3D strategy adult game · By keepherdev

Bug report

A topic by voidtninja created Oct 10, 2024 Views: 242 Replies: 2
Viewing posts 1 to 3

I have two issues, one with many interconnecting symptoms.

the first issue is that sometimes, and i do not know what is the trigger, i'll lose the ability to target in combat.  there seems to be some relation to room type:  i'll not be able to target anything at all in a binding room or a gold mine, but in a research lab the targeting cursor works for some small portion of the legs.  it's almost as if the cursor is being blocked by something, but i've not found an angle around the "phantom obstruction."


the second bug has many symptoms.  One is it seems like the "upkeep loop" breaks, and all variable stats become as if frozen.  they stop both decaying and regenerating, though external sources like items or a wandering character with the "sexy" trait will still affect the relevant stats.  the effect is that no one needs to eat, bath, or socially interact any more.  characters with low mind will be stuck in the "crying" state.  characters with no energy will not regenerate it, and thus remain "tired" unless they enter combat or are given an energy restoration item.   affection is also "frozen," and neither servants or prisoners passively gain it anymore.  my keeper has a pregnancy that is stuck.

these two bugs are my run-enders.  if they crop up, there is no further point in continuing that save.  they seem to hit me most frequently in the range of day 150-200.


there's also a number of smaller bugs, that while annoying, are bearable:

crafting hangs the program.  for several seconds, sometimes.  something is seriously wrong for such a simple object manipulation to be doing this.

the program stresses my rig and cannot maintain a constant 60 fps.  with this engine, with this level of graphic fidelity, and the scale of data being used and manipulated, this should not even be possible.

children are sometimes randomly born as zombies.  when neither parent is a zombie, to be clear.

"crying" is a negative trait you can chose to remove on level up.

an update to the "normal" version of the stuck pregnancy bug:

i managed to catch a pregnancy the day it got stuck.  i reloaded the game, and as the day played out, the birth happened as it was supposed to.  one major thing was different between the stuck day and the day that didnt stick:  an invasion.

there's a slight chance that it was interacting with a servant at exactly the wrong frame did it, but i think the problem is that an invasion prevented the birth dialog box from being created, which caused the birth to never process.


suggested hotfix: in the "upkeep loop" or whatever you've named it that increments the pregnancy timer, implement a check to se if days till birth is less than
zero, and force the dialog if so.

(1 edit)

looking into the log file, the nearest i can trace down the "upkeep loop" breaking down is this:

NullReferenceException: Object reference not set to an instance of an object

  at DungeonWorldEventManager.TriggerEvent_OnPregnancyEnd () [0x000f8] in <f2417dd6da484ffa8597b424d99bbdbc>:0
  at DungeonWorldEventManager.TriggerEventSet_OnNewTurn () [0x00000] in <f2417dd6da484ffa8597b424d99bbdbc>:0
  at DungeonManager.NextTurn () [0x001e1] in <f2417dd6da484ffa8597b424d99bbdbc>:0
  at DungeonManager.Update () [0x00046] in <f2417dd6da484ffa8597b424d99bbdbc>:0

in this particular instance, the upkeep loop breaks during a birth.  the birth may or may not be blocking the return message of servants i have sent out of the dungeon.  of note, as i've been reloading a save constantly to narrow down the event breaking the loop, an invasion once blocked the problematic birth, but upkeep was broken all the same.  this is why i suspect there is a competing "return from outside mission" event being blocked by the birth event.  and to be specific, the servant returning is not the same servant who is giving birth.


the log is also full of an "amical behavior" fail, which may be related to the servant being born and stuck at zero mind because upkeep breaks before the child is fully generated and placed in the game world. 

there's a lot of "failed to play audio source" errors, which i suspect might be the zero-mind newborn's sobs.

there's a lot of geometry errors, particle effect errors, and navmesh errors seemingly tied to weapons.

finally, in the end-of-file memory scan, there's a remarkable number of logged errors in what i assume to be multithreading reports.