Softlocked after delivering final blow to final boss

[spice hinge]

Unable to move or do anything, obviously
Music is still playing

Yippee

Just noticed I got the achievement for killing it, but after going back to menu and back in game, everything was as if I didn't beat it

[drifting ledge]

Hey, can you provide the player.log files?

[spice hinge]

Sure, where can I find them?

[drifting ledge]

If you also want to send me the player file, I can fix the game to make it as you’ve beaten it

But this is optional, I’m sure that it’s frustrating and just wan to give you the option

[drifting ledge]

Did you reset the game more than two times after the crash?

[spice hinge]

Nope. Went back to main menu and back in the game to check its state, then closed the game.

[drifting ledge]

oh ok

Hey, quick question, were you using any visual filters from the painter?

[spice hinge]

No

[spice hinge]

also, thanks for the offer but nah its ok, I'll do it again. I want to see what happens when I actually beat it. Just hoping it wont happen twice in a row

[spice hinge]

I HAVE BAD NEWS

here's the log... I think I'm gonna stop playing for a while

[drifting ledge]

Weird, I was testing the boss earlier and could not reproduce it

I will try to understand what might be happening more accurately tomorrow

[spice hinge]

Thank you. Tell me if you need more data/info.

In the last log I sent, the error happens at line 66878 :

  at SequenceSystem.SequenceExecutor..ctor (SequenceSystem.Sequence sequence, UnityEngine.MonoBehaviour host, System.Action onFinishCallback) [0x00000] in <00000000000000000000000000000000>:0 
  at DungeonDrafters.Scripts.Progress.TowerProgress+<MonsterGodDied_Rountine>d__33.MoveNext () [0x00000] in <00000000000000000000000000000000>:0 
  at DungeonDrafters.Variables.CoroutineStorer+<Run_WithExceptions>d__17.MoveNext () [0x00000] in <00000000000000000000000000000000>:0 
  at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00000] in <00000000000000000000000000000000>:0 
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:LogException(Exception, Object)
DungeonDrafters.Variables.<Run_WithExceptions>d__17:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)```
and it seems it's the exact same error in the previous log, line 69130

[spice hinge]

any news? i'd like to know what I can do to avoid the issue at least :c

[drifting ledge]

Hey! Would you mind sending you save file? I’ve tried to replicate the issue without any success

[spice hinge]

here

[drifting ledge]

Hey, just want to update you that we are investigating this and we may have found out what happened. If I have more news about this I will promptly come here to tell you.

[spice hinge]

yay! thanks

[still fable]

I have reproduced the issue by defeating the hidden boss. And I did it with a melee attack so it didn't soft lock. The bad news is that after this bug happens the player can't take damage.

At all.

I had makhor's sigil equipped and just took 0 damage.

Anyways this is interesting because when I defeated the Demon Lord on a new save file it worked out just fine, but on this save file I've had since before the update it didn't. Could that possibly be related?

[spice hinge]

could be; I started playing ~1 month after release

[still fable]

just did basically the same thing on a newer save and it worked without issue

just now. the credits appear and everything.

It might be related to some progression flag, maybe an id was changed or something. or the save struct.

[still fable]

wait my game clear type is 7???

that shouldn't even be a value

It's similar with Chepaki's save, its 3

oh wait

wait ofc they're bit flags

[still fable]

huh. the same savefile didn't crash on my steam deck that's using the linux version. let me try use proton.

[drifting ledge]

oh no, we probably know the issue

we know where the issue is located and the probable cause of it

our current suspicion is that the windows build broke during the unity building process

and the object that handles the games endings lost reference of that specific ending

[still fable]

yup it just happened to the proton run windows build

[drifting ledge]

if somehow you are able to play on linux, you will see that the game is working fine

[drifting ledge]

yup, I did this check yesterday

[midnight tiger]

Ah, I have the same bug, rip

[drifting ledge]

yup, it’s almost certain a windows bug

[spice hinge]

https://www.reddit.com/r/DungeonDrafters/s/yHAobWqVTd
someone else on reddit encounterred the issue

sooo, no way to avoid it until it's patched I'm guessing?

[still fable]

Yeah...

[spice hinge]

[drifting ledge]

I'm working on it!

Just finishing configuring the build

I was fixing a Illusionist softlock

and I'm sorry @still fable but the effigy bug from the speedrun will be fixed

[still fable]

understandable, but that means I have to do a new run for the newer version

[drifting ledge]

AS FUNNY AS IT WAS

yeah, that's the main reason I warned you

[still fable]

first time he did that, that happened

I went to boss rush and just stood behind him xd

[midnight tiger]

You should leave it and say he's working as intended XD

[drifting ledge]

Hey! @spice hinge @still fable @midnight tiger @patent citrus

We've released a 1.1.1.3 fixing the Demiurge issue

[midnight tiger]

Heeeeell yeah! I'm gonna 100% the game today then! :)

[spice hinge]

YAY! Thank u! I'll try to beat it again later today!

[patent citrus]

i've tested on my end. its been fixed. thanks

[patent citrus]

https://youtu.be/sMu5EOo3hgQ

i noticed the behaviour is kinda defferent after the update,

before: the window just overlap but nothing happened.
after: i get softlocked now

[still fable]

Nope, that's the same

If you open the deck and close it and maybe open and close the pause menu again it will unsoftlock itself