Saturday, March 29, 2025

Proposal: Divide and Conquer

Withdrawn and therefore failed -SingularByte

Adminned at 30 Mar 2025 08:19:40 UTC

Add a new rule named “Challenges” with the following text:

A Challenge is a Story Post with a title that begins with the text “Challenge” in the title. A Challenge may be Open or Closed and is Open by default. While a Challenge is Open, no other Challenges may be submitted.

As a Weekly Communal Action, any Nomicer or the Imperator may submit a Challenge by performing the following steps as an atomic action:
* Roll 2DICEN, where N is the current Float. The result is the Reward for that Challenge.
* Create a Story Post with a title that begins with the text “Challenge” and a body indicating the amount of the Reward from the preceding step.

Each Nomicer has an Attack Commit and a Defense Commit, which are both numbers privately tracked by the Imperator that default to 0. While a Challenge is Open, any Nomicer may Attack any number of times by privately informing the Imperator of their Attack Commit, which is a number between 1 and their Equity, and then posting a comment on that Challenge that contains only a single instance of the text “I Commit my Attack”. Similarly, any Nomicer may Defend any number of times by privately informing the Imperator of their Defense Commit, which is a number between 1 and their Equity, and posting a comment on that Challenge that contains only a single instance of the text “I Commit my Defense”.

If there have been no Nomicers who Attacked or Defended an Open Challenge for the past 48 hours, the Imperator may perform a Tally on that Challenge. A Tally is an atomic action with the following steps:
* Post a comment to that Challenge with the text “This Challenge is Closed”.
* For each Nomicer that Attacked or Defended that Challenge, if their Equity is less than their Attack Commit plus their Defense Commit, set both their Attack Commit and Defense Commit to 0, and consider them as not having Attacked or Defended that Challenge.
* For each Nomicer that Attacked that Challenge, subtract their Attack Commit from their Equity.
* For each Nomicer that Defended that Challenge, subtract their Defense Commit from their Equity.
* Calculate the Offense, which is the sum of all Attack Commits of all Nomicers who Attacked that Challenge.
* Calculate the Defense, which is the sum of all Defense Commits of all Nomicers who Defended that Challenge.
* If the Offense is greater than the Defense of that Challenge, add the Reward to the Offense, then divide the result by the number of Nomicers who Attacked in that Challenge, rounding down to the nearest integer, then add this result to the Equity of each of the Nomicers who Attacked in that Challenge.
* If the Defense is greater than the Offense of that Challenge, add the Reward to the Defense, then divide the result by the number of Nomicers who Defended in that Challenge, rounding down to the nearest integer, then add this result to the Equity of each of the Nomicers who Defended in that Challenge.
* Post a comment to that Challenge detailing the Attack and Defense Commits of all Nomicers who Attacked and Defended that Challenge, respectively, as well as the Equity increases for each Nomicer from the previous steps.

A Challenge is Closed once a Tally has been performed on it.

You can either join Nomicers on one side of the Attack or Defend and split the Reward, or you can attempt to compete with Nomicers for the Reward by joining the other side, but you may also find that the refund of your Attack or Defense Commits gets diminished by a Nomicer on your side who committed less to Attack or Defense than you did.

Comments

JonathanDark: he/him

29-03-2025 05:39:50 UTC

I realized that I didn’t specify that Attack Commit and Defense Commit were reset to their default values when a Challenge first becomes Open. If that’s the only objection people have to this Proposal, I’m happy to “arrow” it and re-propose, or we can just pass-and-patch, since there would be time to patch it before there was a second Challenge, even if someone started the first one right away.

SingularByte: he/him

29-03-2025 07:03:11 UTC

So, there’s an obvious exploit here: if you hedge your bets by spending at least 1 equity on each side, you share in the profits of whichever side wins.
arrow

With regard to resetting the attack and defence commits, I’d probably say they should be set with respect to a given challenge, rather than just being global.

JonathanDark: he/him

29-03-2025 14:28:35 UTC

Ok, got it:

* Don’t allow both Attacks and Defends from the same Nomicer. Or, allow a Nomicer to “switch sides” by resetting their Attack Commit if they Defend and vice-versa, so that they can’t have both. In the latter case, only count an Attack or Defend if the respective Commit is non-zero

* Explicitly track the Commits per Challenge

Anything else? I’ll “arrow” this if it’s clear that there aren’t any objections to the overall idea. I don’t want to waste time making adjustments if this winds up being crossed-out against by a lot of people.

Kevan: he/him

29-03-2025 15:27:29 UTC

The “privately informing the Imperator” stuff should be a Virtual Action, if that Building Block is considered fit for purpose, to save us from the usual rigmarole of whether requests like “one higher than the current highest submission”, “|4x^2-τ| mod 13” and “no wait ignore that I changed my mind” do anything.

JonathanDark: he/him

29-03-2025 15:42:59 UTC

Also, I was considering an “anti-grief” clause so that a Nomicer who feels like they might be on the losing end doesn’t keep advancing the timeout just to prevent the ending of a Challenge.

Something reasonable like 3 or 5 total Attacks and Defends per Nomicer per Challenge.

DoomedIdeas: he/him

29-03-2025 16:06:26 UTC

arrow I agree that a clause preventing an indefinite extension of the timeout should be added. I have no objections to the overall idea of this proposal.

ais523:

29-03-2025 18:44:43 UTC

imperial I’m not sure how I feel about the proposal on the merits, being torn between an arrow and a cross. I doubt the Emperor is going to vote unconditionally FOR this version, so this is intended as an arrow-DEF.

JonathanDark: he/him

29-03-2025 19:16:05 UTC

Any particular concerns, or you don’t like the idea of secret bids to battle for extra Equity?

Kevan: he/him

29-03-2025 19:22:29 UTC

against Lukewarm on whether a bidding and bluffing “attack” subgame really fits with the Equity concept of the dynasty.

Kevan: he/him

29-03-2025 20:04:10 UTC

imperial CoV to DEF; Emperor’s call on how well this fits the dynastic theme.

ais523:

29-03-2025 22:59:31 UTC

@JonathanDark:

I misinterpreted the proposal. I thought at the time of my previous comment that whether a player is attacking or defending is entirely private, which would lead to a symmetrical and mostly luck-based situation.

With the actual version, you have to announce whether you’re attacking or defending (although not to what extent) – that significantly changes things and gives a substantial last-mover advantage (because whoever goes last has the most information). I feel like that is probably a fundamentally unfixable problem (given that the version with private attacking vs. defending is also not really desirable gameplay).

CoV against as I no longer think that a good way to do this exists.

If this does end up getting arrow-withdrawn or reproposed, one other required fix: as written you can attack or defend multiple times, but there’s only one Commit variable for each, which doesn’t seem to take the multiple attacks/defences into account.

Josh: Imperator he/they

29-03-2025 23:39:09 UTC

against I tend to be strongly of the view that the Emperor sets the theme but the players define it collectively. Thematically this doesn’t work for me personally - I think this is a jockeying-for-position, sudden-powergrab dynasty than a head to head conflict dynasty - but my vote is more motivated by a sense that this is a bit mechanically messy in a way that doesn’t quite pay for itself, and worry that it will devolve into a screw-the-leader endgame that becomes more trudge than fun.

JonathanDark: he/him

30-03-2025 03:57:44 UTC

Based on several people stating that this doesn’t fit thematically, I’m going to fully against withdraw this. I appreciate the discussion.