What does this mod do?
- When a human-controlled character dies and his heir is of a different dynasty, the heir is instantaneously switched to the human-controlled character's dynasty, and then is switched back to his original dynasty one day later. This prevents a game over.
- Some localization is changed to reflect the fact that "no heir of your dynasty" does not necessarily lead to "game over".
Why is this mod cool?
- You can continue your campaign even if your heir is of a different dynasty when you die. (This makes the "No Matrilineal Marriage" game rule more playable.)
Why is this mod NOT cool?
- This mod does not affect abdication. If a faction overthrows you in favor of your wrong-dynasty heir, it's still game over. (Fixing this would involve breaking the wide compatibility with other mods that this mod presumably enjoys--but see also the next point.)
- For the single day of inheritance, your new character belongs to your previous character's dynasty rather than to the dynasty to which he should belong. This may cause problems with decisions, events, and CBs on that single day. (For example, EMF's "invite people to your coronation" decision targets characters of your dynasty regardless of how far away they are but is less free with targeting characters who aren't members of your dynasty.) To avoid such problems, don't take any decisions or declare any wars on the day of your inheritance--just skip forward one day before doing anything.
- If your heir was the only member of his dynasty (including dead characters), he will not revert to his original dynasty.
-
- Any kind of elective succession (Feudal Elective, Patrician Elective, Nomad, etc.) may result in bugs. You may want to temporarily disable the mod if your current ruler is under such a succession law. (This won't break your savegame.)
With which version of vanilla is this mod compatible?
It should be compatible with any version back to 2.5.2, in which the random_dynasty_member_even_if_dead scope was implemented.
Is this mod compatible with other mods?
- It should be. I've used it extensively with HIP. (As noted above, however, I don't rule out the possibility of problems with decisions, events, and CBs on the single day of inheritance.)
- CK2Plus's "Non-Dynastic Heirs" game rule (through events Plus.1761 and .1762 in CK2Plus_misc_events.txt) already produces the same effect as this mod, though it uses a slightly-different mechanism (and has some extra trappings so that you don't switch between dynasties in an elective monarchy or a merchant republic). Using this mod with CK2Plus would be redundant. (The original version of this mod was first uploaded two months before the CK2Plus mechanic was introduced in the fifth beta of version 4.06. Don't accuse me of plagiarism.)
Do I have permission to use parts of, or the entirety of, this mod in my own mod?
Of course! Who would be mean enough to prevent others from using his work? Just don't forget to include me in the credits.
2018-01-16, later: Simplified code after learning the difference between event_target and global_event_target
2018-01-16: Initial upload of Game Over Prevention 2 (uses event targets; works if multiple human-controlled characters die on the same day; works if the heir's dynasty contains dead members but no living members other than the heir) in its own thread
2017-__-__: One or two very minor updates(?) uploaded as part of misc. tweaks for HIP
2017-01-08: Initial(?) upload of Game Over Prevention 1 (uses character flags; possibly has better backward-compatibility with vanilla than version 2) buried in a random thread
2018-01-16: Initial upload of Game Over Prevention 2 (uses event targets; works if multiple human-controlled characters die on the same day; works if the heir's dynasty contains dead members but no living members other than the heir) in its own thread
2017-__-__: One or two very minor updates(?) uploaded as part of misc. tweaks for HIP
2017-01-08: Initial(?) upload of Game Over Prevention 1 (uses character flags; possibly has better backward-compatibility with vanilla than version 2) buried in a random thread
Last edited:
