Wednesday, January 15, 2025

Proposal: Bounty Hunters

Reaches quorum 5-0 with one emperor not counting towards quorum -SingularByte

Adminned at 17 Jan 2025 07:29:33 UTC

If the Proposal “Security” was not enacted, the rest of this Proposal has no effect.

Add a new rule named “Bounties (Heists) {M}” with the following text:

Each Participant has a publicly tracked number named Claims that defaults to 0.

A Bounty Notice is a post in the Story Posts - Votable Matter category which broadly requests a single mechanical or ruleset change and contains the text “Bounty Notice:” at the start of the post title. Unlike other Votable Matters, only valid Votes from a Mastermind are counted in a Bounty Notice as described in this rule, and Votes from non-Mastermind Participants are ignored. A Bounty Notice may be Open or Closed, being Open by default and being Closed when set to the ‘Enacted’ or ‘Failed’ status in the post backend. As a Heist Action, a Mastermind may post a Bounty Notice.

If a Mastermind believes that one or more enacted Votable Matters satisfy the demand of an Open Bounty Notice, they may post a comment to that Bounty Notice with a FOR icon and the names of each Participant (other than themselves) who authored at least one of those Votable Matters.

Bounty Payout is an action where a Participant’s Claims is increased by 1.

A Bounty Notice may be set to Enacted by a Mastermind if all of the following are true:
* It has been Open for at least 12 hours
* All Masterminds have posted at least one EVC in that Bounty Notice while it was Open.
* Each Mastermind’s most recent EVC in that Bounty Notice contains a FOR icon and the name of at least one Participant other than themselves.

A Bounty Notice may be set to Failed by a Mastermind if any of the following are true:
* Any Mastermind’s most recent EVC in that Bounty Notice contains an AGAINST icon.

When a Bounty Notice is Enacted, the Mastermind who Enacted it should apply the Bounty Payout action to each Participant named in each Mastermind’s EVC containing the FOR icon.

In the rule “Teams and Targets”, add the following bullet to the end of the bullet points in that rule:

* For each Participant, add their Claims to their Triumphs, then set their Claims to 0.

It feels like Bounties might be a good fit for this dynasty.

Rewritten per ais’ suggestion, plus making the rule name unique to distinguish it from the Bounties rule on the Building Blocks wiki page.

Comments

ais523: Mastermind

15-01-2025 19:19:36 UTC

I was considering the building block myself, but there are a couple of potential issues that would need solving. One is that the Masterminds could post numerous spam bounties that reward things that their team has already done, or is about to do, in order to get lots of payouts. The other is that we don’t yet have a resource to pay people with (but maybe we should create one!).

I think at the minimum there should be some limit on creating the bounties (Heist Action?) and that both Masterminds should need to agree in order to pay out the reward, rather than just one. That’s different enough from the existing rule that maybe this should be a new dynastic rule, rather than a building block.

JonathanDark: he/him

15-01-2025 19:21:49 UTC

Good points. Let me think on this and re-write.

JonathanDark: he/him

15-01-2025 22:30:28 UTC

I’ve re-written this Proposal to incorporate text similar to the “Bounties” in the Building Blocks, but with specific rules to fit this dynasty.

ais523: Mastermind

15-01-2025 22:39:02 UTC

You have an “If the Mastermind” in the last paragraph, which needs to allow for the multiple Masterminds.

Also, you have “that defaults 0” at the start, which is probably a typo.

JonathanDark: he/him

15-01-2025 23:07:05 UTC

Thanks, fixed.

I also rewrote (again) some parts because I forgot to include your request that both Masterminds should agree before the bounty is paid out. I had to spell out the voting process.

Interestingly, this allows each Mastermind to submit their list of Participants who they believe met the conditions of the Bounty. This could have some timing issue, if the last Mastermind to submit a list wants to submit a bogus list and then Enact the Bounty. I ran out of time trying to figure out how to address that, so I’ll leave it up to a later Proposal, if folks are ok with going what I have as a start.

Brendan: he/him

16-01-2025 02:54:19 UTC

for

Habanero:

16-01-2025 03:00:00 UTC

for Interestingly, I think I was there for the last time Bounties were tried in SingularByte I.

Habanero:

16-01-2025 03:00:15 UTC

Unless, of course, I missed something in between

SingularByte: he/him

16-01-2025 06:47:04 UTC

imperial Making each claim equivalent to a successful triumph might be a little powerful, but I suppose it does depend on how widespread the bounties end up being.

JonathanDark: he/him

16-01-2025 17:00:15 UTC

I’m up for rebalancing at some point. Let’s see how it plays out.

Josh: Mastermind he/they

16-01-2025 17:03:43 UTC

imperial

ais523: Mastermind

16-01-2025 17:14:04 UTC

imperial

SingularByte: he/him

17-01-2025 05:50:08 UTC

CoV for  Just so this ideally doesn’t clog the queue.

ais523: Mastermind

17-01-2025 06:24:16 UTC

for to keep the queue moving