Store Page

Crusader Kings III

All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Crusader Kings III > Workshop > Stik' | Mostly Mechanical Mods's Workshop

1,187 ratings

Prisoners of War

Description Discussions8 Comments438 Change Notes

Award

Balance, Gameplay, Warfare

File Size

Posted

Updated

2.190 MB

Jun 8, 2021 @ 8:38am

Mar 18 @ 4:11pm

23 Change Notes ( view )

Required items

This item requires all of the following other items

Foundational Framework

Created by

Stik' | Mostly Mechanical Mods
Offline

See all 14495 collections created by Stik' | Mostly Mechanical Mods and other people (some may be hidden)

158,501	Unique Visitors
60,574	Current Subscribers
4,011	Current Favorites

Subscribe to download
Prisoners of War

Subscribed

Unsubscribe

In 2 collections by Stik' | Mostly Mechanical Mods

Mostly Mechanical Mods

13 items

Foundational Framework

8 items

Description

Updated for v1.15.*
Long gone are the days when prisoners teleported from a siege location deep in enemy territory to your own dungeons !

Prisoners of War is a Mostly Mechanical Mod

Prisoners of War adds a new layer of tactical choices : should you siege back your holding to negate the warscore from its occupation, or should your chase down the army that's taking away your heir, in the hope of liberating it before his capture can be leveraged in a call for peace ?

Commanders Assemble! - New Feature

Commanders must be physically present at the location of the army - and will no longer teleport there.

When you appoint a Commander to lead your army, the Commander will have to actually travel there, making full use of the new travel system. The UI will display the estimated travel time to better inform your choice.

If the Commander is removed from their post (because the army is disbanded, merged, or stackwiped), they will head back home - with their Prisoners in tow.

By default, all travel events are disabled for traveling commanders, with a setting to turn them back on.

Prisoner Transfer

Characters imprisoned in battle, raids and sieges will be tied to the Commander that captured them, until the Commander reaches friendly territory (either by leading the army there, or by leaving the army to head home), and prisoners are transferred to the dungeon.

Should the army be defeated in battle before that happens, prisoners will be either liberated, or transferred to the army of their new jailor.

Changes:
Because the Prisoners are now tied to the Commander, and not the Army itself, to make use of the travel system, armies without Commanders can no longer make prisoners. This is a tradeoff for a much more robust system, with fewer bugs and weird situations.

Prisoner Released Travel - New Feature

All prisoners travel home upon release or escape.
By default, all travel events are disabled for returning prisoners, with a setting to turn them back on.

Compatibility

Prisoners of War requires Foundational Framework to work, and will be compatible with all supported mods.

If your mod has compatibility issues with Prisoners of War, please get in touch on our discord ![discord.gg].

Credits

This mod benefitted from the invaluable help of the CK3 Mod Co-op.
All remaining bugs are my own.
Russian translation by Vadim Kodeks

Popular Discussions View All (8)

Apr 12 @ 1:44pm

PINNED: Bug Reports

Stik' | Mostly Mechanical Mods

Oct 5, 2024 @ 8:53am

German Localization

Tannenzäpfle

Jan 4 @ 3:58pm

Советы в развитии мода.

Shrek

438 Comments

< >

AuraOuroboros Jul 22 @ 5:46am

@akagi can confirm you file change suggestion fixes the UI issues, however it seems to remove the ability to change a raiding army's stance so raiding acts like it did before Kahns was released. Personally, I don't mind, but I figured it was worth mentioning so others know.

akagi Jul 10 @ 3:38pm

I figured out how to fix it — just remove the UI changes related to prisoners of war. However, I’m not sure if this will cause any strange side effects.

Find the file named PoW_types.gui in the prisoners of war mod folder.
Clear all the code inside the types PoWReplace brackets, leaving it empty like this:

types PoWReplace {

}

Doing this should restore the UI part to the original vanilla state and, in theory, shouldn’t affect gameplay.
But I don’t understand code myself, so although it works fine for me now, I hope someone who knows code can check if this approach causes any issues.

Also, please use the patch linked here to fix the Foundational Framework bug:
https://steamcommunity.com/sharedfiles/filedetails/?id=3480802836