Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If it happens at an earlier stage you might want to consider filing a bug report on the Paradox forum-
What do you mean by "siege progress"? Number of siege phase? It would be the dumbest game mechanic ever and doesn't verify... Siege percentage? the same...
Winning a siege requires you to roll a 20 on a 14 side dice. (which explains the negative chance to win at start).
You have various modifiers that apply to your roll, one of them is called siege status. Food shortages increase siege status by 1 for exemple. But once siege status reaches 12, it won't go any further, meaning food shortages will only kill the garrison, but won't increase your chances to win.
So you have to resiege it? How can I get 70% on a level 8 fort and be stuck at 7 on a level 3? And tested in non iron mode, removing enough troops then putting them back seems to rectify the issue. Looks like bug or really bad design.
Thanks for the reply anyway, I'll watch for those status...
Normally you shouldn't have to resiege when you cap the siege progress.
In your case, if moving troops away and back in solves the issue, it might come from the disease outbreak, which can happen on a bad roll and kills a big part of your army. If you had just enough troops to siege the fort (the exact number or regiments required), this can lead to your army becoming too small for one or two month until reinforcements arrive.
You should check if your problem comes from that (you should see the icon warning you siege cant advance any further and check your army size in that province).
When you first start the siege it become status quo, but usually after 30 days roll of the dice changes to a different result(defenders desert, supplies shortage etc). Even with a large enough army, in one case 10infy/10cannons/siege general/navy blockade i had one of the first forts remain status quo and never change phase. No garrison loss at all.
This lasted until i had every other enemy/province sieged. Only removing the stack and adding it back fixed the issue.
With the amount of sieging done, it is rare, ive seen it maybe 6ish times since common sense came out.
One of the times removing the stack and replacing it just handed over siege control to another attacking country in a seperate war. The AI also suffered status quo and no change in garrison until long after id peaced out, till it got lured off the fort to join a battle and then returned, bug gone.
To make sure you dont end up wasting years sieging for no effect in the rare case this happens, just watch the first phase or 3 kick in after you move troops onto the fort.
If it changes to any other siege effect(supplies/food etc) then you dont need to worry.
If you have enough modifiers(arty, blockade, general with siege bonus etc) and enough total troops that a little attrition isnt lowering your sieging troop count to below minimum and after a few phases you still arent getting anything but status quo, you may need to jump off/on.
Messed around on a non ironman game that i saw it happen on. Reloads sometimes fix it, moving off/on fixed it everytime, adding more/moving all but 1 troop off/on didnt work. moving a leader on didnt change anything. But a few of the times, not all, it seemed to just randomly sort itself out after a prolonged period, it obviously isnt right when a fort has max cannons, 3siege leader, blockade, more then enough troops on a level 1 fort and no change after 4 years.
Just dont think it is always a bug.
If you're sieging a high level fort that might need a minimum of 12 troops and you only leave 12 infantry on it, it could just be due to not enough modifiers(cannons etc) to help your effort and attrition/reinforce rate/manpower making your troops fall below minimum amount and halting any progression.
Make sure you are doing everything right before assuming it is a bug.
As stated in the original post, it's not due to lack of troops : it clearly notify food shortages or whatever siege event. That's why I didn't bother to reply previous answers that were assuming I was new to the game (or the serie, only played hundreds of hours to this one) and was to dumb to read a simple notification like "you don't have enough troops to siege this fort" or the unit screen where the maximun level of siege is mentionned...
It doesn't happen often, yet it's game breaking.
If it's a large coastal fort you will need artillery and preferably a blockade to take the fort without a lucky roll.
On the other hand you could also just wait for their garrison to die off from the siege then storm the ramparts (if the walls are breached)
READ THE POST... food shortage, water shortage? not status quo, yet the siege doesn't advance.
a screenshot will hardly help (a static situation won't show any evolution)... thanks for another insightfull comment...
Instead you seem content to have this bug and argue with anyone that trys to help, so gl with that.