Crusade Quest Bug

[Pep]

In my last game, I received the 'Crusade Quest', conquered the holy city and, the Quest failed at the next turn!

I'm playing with Solver's unofficial patch. I receive the quest when I was already at war with the owner, and then razed one if their cities.

Edit: removed old attachments because my quota is near the limit...

 

[jkp1187]

Noticed the exact same problem in my game. I, too, am playing with Solver's patch, and was tasked with capturing Seoul. The turn after I captured Seoul, I got the message that the quest had failed.

One thing of note: immediately after I captured Seoul, Wang Kong became a vassal of Frederick. I reloaded, took Seoul again, then turned Wang into my own vassal. The next turn, I still "failed" the quest. I was wondering if, perhaps, the fact that WAng became a vassal (and, thus, the foreign relations status changed before I got the "quest succeeded" message,) was causing the quest to fail for me?


EXPECTED BEHAVIOR: I take Seoul then succeed at quest.

ACTUAL RESULTS: I take Seoul then fail at quest.

TO RECREATE: Use military force to take Seoul (order does not matter--I recreated it using different attack order,) then cycle to next turn. Even though you take Seoul, the quest is failed.

 

[jkp1187]

This crusade quest bug tasks me in another game. This one is a bit easier to replicate than the other save file. Constantinople (the goal city of the quest) has been taken -- all you need to do is cycle to the next turn, and the quest fails. My earlier hypothesis about the victim turning vassal was incorrect. The quest just won't succeed once I've taken the target city like I was supposed to. (The other quest, "Greed", however, succeeds....)

 

[mnf]

I've just had the crusade quest, and it just happens that the Holy City I was told to take was the last of the civilization's city. This is now with the latest Solver patch.

-QUEST LOG-
You have failed the crusade quest!
The Japanese civilization was destroyed!

....

 

[Solver]

Yep, it's a known bug at this point, apparently the quest is broken. With luck, I'll include a fix in my events mod.