Saturday, August 26, 2023

Proposal: The Subsequence Dilemma

Timed out 3 votes to 1. Enacted by Kevan.

Adminned at 28 Aug 2023 10:16:02 UTC

In the rule The Conclave, change “while it is not required that a District immediately update gamestate tracking to reflect that expenditure, it must be accounted for before any subsequence response to a Plenary Session is made.” to:

while it is not required that a District immediately update gamestate tracking to reflect that expenditure, they must do so before they make any subsequent response to a Plenary Session.

In the rule The Conclave, change “2 Score per Connection” to “1.5^x Score per Connection (where x is the amount of Connections that District is allocating to this Plenary Session)”, change “1 Score per Connection” to “1.2^x Score per Connection (where x is the amount of Connections that District is allocating to this Plenary Session)” and change “1 Score per Order” to “1.5 Score per Order” wherever they appear.

bugfix + some miscellaneous buffs

Comments

Josh: he/they

26-08-2023 09:31:41 UTC

Good catch.

Rafter:

26-08-2023 10:15:51 UTC

First change is solely to put burden of updating on the District that made the expenditure?

Josh: he/they

26-08-2023 10:54:25 UTC

No, it’s because the way it’s currently worded (“before any subsequent response… is made”) arguably prevents any other District from making a response if one District refuses to carry out their gamestate update.

Josh: he/they

26-08-2023 16:22:04 UTC

for

JonathanDark: he/him

26-08-2023 18:35:58 UTC

against

I don’t like that you coupled a fix that makes sense with “miscellaneous ” buffs that help yourself the most. I have no problem with the “subsequence” fix and will greentick it if it’s included on its own.

JonathanDark: he/him

26-08-2023 18:49:53 UTC

@lendunistus: Just a note that once Josh spends his sizeable energy on another Connection, he’ll be in a better position than you thanks to this proposed change.

Rafter:

27-08-2023 23:01:00 UTC

for