Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crown laws shouldn't be able to be passed on titular KING+ titles. #606

Open
zijistark opened this issue Feb 10, 2019 · 0 comments
Open

Comments

@zijistark
Copy link
Member

Pros:

  • Since only de jure vassals of the title (well, specifically, rulers that are subject to it as their crownlaw_title, which does require de jure pretension over them) incur the temporary (but significant) opinion maluses for raising authority in any way, players/rulers with titular crown-tier titles can raise authority willy nilly while they wait for de jure duchies (for a kingdom) or de jure kingdoms (for an empire) to drift into their title.
  • Since almost all of the crown laws don't even have an effect upon vassals that aren't subject to it de jure, it's highly misleading / even bugged to allow the laws to be enacted when they cannot do anything.
  • It doesn't actually take that long to de jure drift a title into being non-titular, especially if it's an empire title (50 years by default in that case). Further, there are game rules that can shorten the drift timers quite significantly if a player prefers.
  • AIs with weird titles (looking at you, k_teutonic_state) are simply out of luck. However, they were already out of luck since they had no de jure vassals and the laws would've done nothing. Note, however, that this is a bit of a separate issue (i.e., some laws that are typically crown laws might be more appropriate as demesne laws for these cases — think: Protected Inheritance & Free Infidel Revocation).
  • It's easy to get your hands upon a de jure crown law title (e.g., create/usurp/revoke the kingdoms under your titular empire). If people don't like the extra patience required, they can just take that into account when creating their next titular crown-tier title.

Cons:

  • Titular KING+ rulers cannot achieve the fastest route to popular succession laws that are unlocked by High CA (and Medium CA if you're a weirdo that wants Seniority): they have to wait to be able to pass Late Feudal Administration (a demesne law) to unlock all of that. This seems totally acceptable to me.
  • Titular KING+ rulers will not enjoy things like access to the De Jure Duchy Claim CB, De Jure Kingdom Claim CB, or the Subjugation CB (not to be confused with Pagan/Nomad/Indian Subjugation) against DUKE- or KING-tier targets. They also won't be able to stop internal vassal military plotting/infighting (High CA), and they won't be able to enjoy Protected Inheritance or King's Peace. They will still be able to enjoy Title Revocation (if they have Conclave).

Pros OR Cons, depending upon your perspective:

  • Generally speaking, players are the only ones that end up with these types of titles for long (from Custom Title Formation). That means they need to actually work hard to de jure drift as fast as they can so they can start asserting de jure legal authority on their vassals. Players are very well-equipped to do so if they understand how de jure drift works. [IMHO, this is a Pro no matter which POV.]
  • For players/rulers that are under any liege with only a titular crown-tier title, they have time to create kingdoms and do their own thing before the de jure shoe drops.
@zijistark zijistark self-assigned this Feb 10, 2019
@zijistark zijistark added this to Ideas in EMF v9.01 / Furry2 Feb 16, 2019
@zijistark zijistark added this to Low Priority in EMF v9.02 / Furry3 via automation Mar 5, 2019
@zijistark zijistark removed this from Ideas in EMF v9.01 / Furry2 Mar 5, 2019
@zijistark zijistark moved this from Low Priority to Ideas / Long-Term in EMF v9.02 / Furry3 Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
EMF v9.02 / Furry3
  
Ideas / Long-Term
Development

No branches or pull requests

1 participant