Confirmed The Eternal Court - Quest Bug

[Eomolch]

Hi Banterbot! Thank you for the bug report and sorry for the inconvenience this caused.

I have "fixed" your save game so you can still complete the story path, though you unfortunately do miss the bit of the story happening on that tomb wonder. If the save complains about a different game version when loading that should be fine, just hit yes to load it anyway

Also, do you still have a save from earlier in that session? Ideally even from the game start?
I could not yet find out how the Tomb ended up explored (but it was not an AI player) and taking a look at the game start would be of great help here.

Thank you!
~Eomolch

 

[Eomolch]

Hi Guillaume, thanks a lot for sharing those save games
I now found the problem and fixed it in our dev build (the Tomb failed to create its defenders when playing the mission on Hard difficulty). Unfortunately the fix is too late for our next upcoming patch, but it will then be added to the patch thereafter.

Below I fixed your final save the same way I did for the other player. So unfortunately you still miss part of the story that plays out in the tomb itself, but at least you can continue and still complete the story path this way.

Best regards,
Eomolch

 

[Eomolch]

Hi RunningTwo! Sorry to hear this has affected you too. Unfortunately the bug materializes at the mission start, since this is when the Ancient Wonder tries to spawn its defenders, but fails. So the upcoming patch will only fix this for new sessions, not for ones already affected by it.

However if you share your save game I could fix it the same way I did for the others before. With the caveat of missing the story of the tomb.
Else I'm afraid you would have to restart the mission after the next patched dropped (which will be after easter afaik).

Best regards,
Eomolch

 

[Eomolch]

Here you go, RunningTwo!
Also, since multiple people got this, I'm leaving screenshots of the tomb events here in a spoiler, so you can read up on what you missed.

Spoiler: Tom of the Lost Mother

 

[Eomolch]

Happy to help, always pains me to see someone stuck with a story bug.

Thanks, you too have a great weekend!

 

[Eomolch]

Hi Wiggie12, sorry about the late reply, I was away on Easter vacation.

But here is your fixed save game now, hope it still helps!

 

[Eomolch]

Yes, I can

 

[Eomolch]

You should have gotten a story event featuring Meandor when loading the save?
I unfortunately cannot fully fix the bug in live games; I could just complete that part of the quest for you. I included spoilers in one of my above posts where you can read the part of the story you miss that way.

 

[Eomolch]

Hi Patriarche, thanks for reaching out
Here is your fixed save game!

 

[Eomolch]

Good morning, Patriache!
Sorry for the late reply, but I had to check with a few people about this.

As it turns out, unfortunately, what I did was not very well informed and save game fixing like this will only work for GoG players. For other platform users the save games are cloud based and as you observed this means the system will ignore files you put in the same folder manually.

My apologies for this mixup and giving you unfounded hope of fixing the session, which sadly is not possible.

However, at the very least, yesterday's 1.2.1 Giant Kings patch did bring our general fix of the issue for players on new playthroughs. This does unfortunately not help you, but should mean no more people will get stuck on this moving forward.

Best regards,
Eomolch

 

[Eomolch]

Hi Velodir, thank you for reporting this and very sorry about this bug somehow still messing with your game. I have looked into it and it seems that there is another bug in addition to the one previously fixed that still makes it that _sometimes_ the wonder is cleared on game start. A coder is looking into the exact cause of this now!

Unfortunately as established before I cannot fix your save, so you will have to complete your session the non-story route

 

[Eomolch]

HI Vidyaraja, I am very sorry about the late reply. I did look into the problem again when you reported it, but it then had to go to a (very busy) coder for debugging and I forgot to reply.

I found exactly the same thing as you, that it was sometimes working fine and sometimes cleared on hard.
There is no need to start another bug thread, it is in our system and QA is pushing for a fix for our AP release.