Comments

Log in with itch.io to leave a comment.

In the Sol boss fight, I summoned a second guardian with a second summoner, and the game became unresponsive.  When I reloaded, summoning even a single guardian softlocked the game.  I have some buffs that are automatically applied to my summons, and I have the 'pay health instead of energy' daemon.  The 'a unit died' sound plays when the guardian is summoned, and the game continues its passive animations and a weird one where a circle of particles radiate out of the guardian a short distance, and the settings menu and esc menu are still responsive, but the turn cannot be ended and no moves can be used.

(1 edit)

Weird. I tried to launch this thing with no crashes, but there are too many weird interactions to grab them all. I'll take a look at it

(1 edit)

I've tried a bunch of different combinations trying to replicate this thing, but I can't seem to find it. It must be a very specific interaction you've found. 

  1. Would you mind sending me a screenshot of the crash if you have one? 
  2. If not, don't worry, but do you remember the buffs you had that you automatically give the summon? 
  3. Were the damage particles the same generic damage particles that play when something gets hit/takes damage?
  4. Did the game crash when either unit tried to summon a guardian with no buffs?
    1. If not, it was probably a weird interaction with another daemon. Can you think of anything that has to do with healing/summoning/killing/auras on another unit?

Since I can reload into the fight at-will it's easy to reproduce on my end.  Here's a video: https://www.loom.com/share/65af8847ed9049c690f48ef593a37292?sid=291fc7bc-9be8-4b... Summon is @ ~1:50, it starts from loading the save file.

(1 edit) (+1)

Interesting. It looks like you had a very specific interaction where summoning a unit on a tile with two overlapping necrotizing spores auras causes a crash. It should've been fairly rare, and you just happened to get unlucky with the rng. Thanks for pointing it out though, and it should be fixed now (along with several other random improvements)!

(+1)

Very cool