CK III - stupid crusade

[mastermind666]

Short summary of your issue stupid crusade

Game Version Chevron (1.1.3)

What OS are you playing on?
Windows

What platform are you using?
Steam

Do you have mods enabled? Yes

Have you tried verifying your game files (Steam only)?
Yes

How much "pain" is this causing you?
10

Please explain the issue you experienced in the most condensed way possible
pope declared crusade with 3000 vs 190000 troops even when cathlics don't own a single county? can't get warscoe -> 10 year war incoming

Please explain how to reproduce the issue


Is there anything else you think could help us identify/replicate the issue?


I have attached a save game
No

 

[Thorvarg]

Or see this crusade. 8.500 attacker vs 780.000 defender.

 

[mastermind666]

Also pretty bad but at least you could fight them to speed it up (i asume) but for me they didn't have any province where they could have spawned their troops so i could do exactly NOTHING.

 

[Thorvarg]

Now I have the same situation. I rule almost the whole world, but I cannot continue with my conquest, because the crusade prevents me from doing so. The pope has no more land and there is nothing else to conquer. In order to destroy the papacy, I have to dominate all of Italy. However, I am missing a single county on Sardinia, a county that belongs to another MUSLIMIC ruler. Quintessence, I cannot end the crusade and therefore I cannot achieve my goal of conquering the world. Sorry, but I am totally pissed off.

Check my Ironman save game and the screenshots.

 

[zack137]

This really does suck, I'm currently waiting for the warscore to tick up in my crusade. Capturing enemy capitals doesn't affect warscore in GHW either. They gotta fix this. Mine isn't quite as bad as this, I can destroy one of their armies occasionally when they pop up for an extra 1%. I will say, it didn't prevent me from starting and finishing an invade kingdom war while the GHW warscore slowly ticked up 10%.

 

[Tiny_Atrocities]

Hello!

Thank you for the report! We are aware of the issue, it has already been added to our bug database.