Crusader Kings III

Crusader Kings III

Love Marriage Family
Showing 11-20 of 136 entries
< 1  2  3  4 ... 14 >
Update: 12 Jun @ 5:58am

  • Did some streamlining of the code for courtier courting & seduction schemes as well as courtier marriage proposals, to make the overall processing overhead less - which will be particularly noticeable in very large player realms (like the Iron Throne in AGOT). Big thanks to the AGOT coders for help on that one.

  • Fixed a bad trigger reference which was using the trigger for courtiers who'd be willing to do courting schemes when it should have been looking for courtiers willing to do seduction schemes.

  • Fixed a few bad scopes referenced in the army events.

  • Added a check to make sure at least one of the two lovers referenced in a "can they elope?" check is a courtier. Also fixed the option to promise an elopement when the player is the target of an elopement scheme, so it's now possible to do (assuming an elopement is indeed possible).

Update: 11 Jun @ 7:54am

  • Added a couple of new army events which revolve specifically around encountering peasant men/women who a knight or commander might have sex with while out in the field, thus increasing the chance of encountering such an event.

  • Changed a number of the events so they use nighttime camp backgrounds.

  • Changed the "Night of Merriment" event so you can't walk away if you're at the second stress level threshold.

  • Fixed the "Lost and Found" event so the beautiful stranger is of local culture/faith rather than your own.

  • Tweaked some of the chances of encountering certain army events, mostly based on current stress level.

Update: 10 Jun @ 5:54am

Just a fix to the event where a peasant mother of a bastard child comes to court - needed some changes to have it localize properly (and changed the event order so you learn the secret during the event and not right before). Other than that, just a few other minor loc tweaks to the new army events.

Update: 9 Jun @ 10:52pm

No other changes than updating the AGOT compatibility a bit - namely, updating the references to the Old God religion and the Faith of the Seven to use the new versions, as well as moving compatibility localization into the new sub-folder structure that AGOT has so you won't see improper loc any longer for the First Men heritage or the birth/pregnancy events that involve a paramour.

Update: 9 Jun @ 12:00am

  • Added new army events, which can affect every knight and commander currently in an army much like travel events (including the player, if they're commanding an army). How does this apply to LMF's theme? Well, soldiers sleeping with camp followers and locals to relieve stress was one of the main ways that bastards appeared historically, and a good chunk of these events revolve around that.

  • Added game rules for the new army events, allowing you to restrict them to player only, player realm only, or all independent rulers of duke+ tier... or to shut them off altogether. Note that, unless the events are shut off, there's a back-up mechanism which will still sometimes create bastards that is used by AI realms even when you have the game rule set to player-only or player-realm only (it's just much less frequent for AI rulers, then).

  • Added a new form of story similar to the "peasant affair" from vanilla, where a lowborn peasant woman in the pool that you slept with could return later with your bastard child. This one allows the story to result in the mother (or the bastard, when they're an adult) to seek out the father, and works whether the father is themselves a ruler or has close/extended family that's a ruler. The event where the heir visits another ruler for training and can party it up and sleep with a commoner now uses this story (as do a number of the new army events).

  • Fixed LMF marriage-related events causing errors in the error log because they didn't account for the new "send herd" marriage proposal option.

  • Fixed a dynasty_prestige_level check in the courtier and guest management file to properly scope to the dynasty, so it no longer causes a bunch of regular errors in the error log.

Update: 5 Jun @ 2:05am

  • Updated for the 1.16.2.3 patch.
  • Borte's event-driven pregnancy (in the vanilla Genghis Khan events) will now work properly if you have the Realistic Pregnancies rule applying.
  • Replaced most courtier seduction code that used "num_of_relation_lover < 1" to use "is_below_ai_lover_soft_cap_trigger" instead, so that courtiers with the Lustful trait, Seducer trait, or the Temptation intrigue focus to have up to 3 lovers instead of being limited to 1.

Update: 27 May @ 1:39am

  • Updated for the 1.16.2.2 patch.
  • Updated a few issues with Court and Seduce schemes, the main noticeable thing is that you shouldn't get the "will not cheat on spouse" penalty when you are the scheme target's spouse.

Update: 22 May @ 6:55am

  • Updated for the 1.16.2.1 patch.

Updates for ANSF3:
  • The error log will no longer spam with error entries every time you go to the main family screen.

  • Fixed creating player children with a concubine.

  • Fixed creating half-siblings with a previously existing character.

  • If you create player children or half-siblings with a previously existing secret lover, the lover secret will be exposed upon the child's creation. The mod does not create secret children (yet).

  • Backing out of a player child's or half-sibling's creation will no longer kill off the "other parent" if that character was previously existing.

  • Former spouses, consorts, and lovers are now also added to the additional characters row in the main family screen.

  • The event option to select a previously existing character is now different, depending on whether you already have children with them or not.

Update: 20 May @ 9:56pm

Updates for ANSF3:

  • Fixed the issue when trying to create a child with the player and a former spouse, lover, or concubine.

  • If you create a lover to be the parent of either the player's child or a half-sibling, they can no longer be a current lover if the player or half-sibling's parent already has one.

  • Age ranges for created relatives will always be integers - no more decimals for situations where dead characters need to be factored into the age range calculation.

Update: 19 May @ 10:53pm

Fixes the ANSF3 issue when trying to create legitimate children (with your current spouse, as opposed to with a different parent like a former spouse or lover) leading to the wrong event.