Monday, November 27, 2023

Proposal: Thou Who They Is Maidenless Shalt Not Proceed

Withdrawn. Failed by Kevan.

Adminned at 28 Nov 2023 18:07:44 UTC

Create a new dynastic rule named “Marriage” with the following body:

Each Heir has a Partner, which is a publicly tracked value that defaults to None. If an Heir’s Partner is set to the name of a Bride, they are considered to be Married to that Bride. Each Bride has a name (which is flavor text), a Benefit and Requirements. The list of Brides is as follows:

Marriage is an atomic action with the following steps:
* Set your Partner to the name of a Bride whose Requirements you have met

Divorce is an atomic action with the following steps:
* Set your Partner to None

If a rule named “Claims” exists, add two new claims: one named “Partnership” with a strength of 20 and the requirement “You are Married to a Bride” and one named “Faithful” with a strength of 10 and the requirement of “You have not performed the Divorce action during this dynasty”.

we’re in medieval times, after all
very barebones right now but I’ll try to figure something out with this

Comments

SingularByte: he/him

27-11-2023 19:50:49 UTC

Would claims of negative strength do anything? Currently it’s the highest strength that wins, rather than any kind of sum total.

Bucky:

27-11-2023 20:02:35 UTC

It’d be better to have a positive strength claim for never having divorced.

Bucky:

27-11-2023 20:04:09 UTC

Actually, negative claim strengths aren’t legal at all under the current rules, so Divorced would have the default strength of 1.

SingularByte: he/him

27-11-2023 20:09:22 UTC

They are actually being made legal in this proposal, but I do agree a “never divorced” claim makes more sense. Otherwise, divorcing is weirdly actually better than going totally unmarried, since it’s valid for tie-breaking (though weaker than still being married).

lendunistus: he/him

27-11-2023 20:10:11 UTC

@Bucky fair enough, edited

might be good to have some kind of currency that you get when obtaining claims and that can be spent on stuff

Vovix: he/him

27-11-2023 20:27:47 UTC

Do we want to make it gender-neutral? I deliberately went with Heir over Prince to avoid introducing a default male connotation, because I figured inclusivity > historicity.

Vovix: he/him

27-11-2023 20:47:30 UTC

Oh, also, technically Claims have Conditions rather than Requirements.

SingularByte: he/him

27-11-2023 22:24:26 UTC

Just to confirm, is it intentional that everyone can have the same bride?

Josh: he/they

27-11-2023 22:55:29 UTC

Can it be Spouse instead of Bride? I’m bristling slightly at the default-male assumption here.

Josh: he/they

27-11-2023 22:56:26 UTC

(Implict assumption, I should say)

Vovix: he/him

27-11-2023 23:35:59 UTC

I think Spouse may get confusing with Partner. Maybe “Spouse” for the one you’re married to and something like “Prospect” for the potential partners?

Josh: he/they

27-11-2023 23:41:33 UTC

Out of edit window, anyway; would vote for with fixes against

Kevan: City he/him

27-11-2023 23:44:00 UTC

imperial

4st:

27-11-2023 23:46:08 UTC

for we should def change the the default male-assumption, but otherwise sounds fine to me. Maybe has to happen after the fact :shrug:

JonathanDark: he/him

28-11-2023 00:12:57 UTC

against I think the overall idea is good, but the details need a re-work

Bucky:

28-11-2023 03:02:30 UTC

imperial

lendunistus: he/him

28-11-2023 05:08:33 UTC

@SingularByte thought of that but forgot to write it in, grr

regarding the gender-neutral part, I just couldn’t think of the gender-neutral version of the word “bride” (partners were even named wives when I was writing this)

against thanks for the feedback, will repropose