@Ais: I see it now, thank you very much.
And some tardy replies:
@Kerim: Thanks! I've implemented those ideas. Yes, it has got archives for
past rolls.
@Juan: Your site is definitely more rigourous than mine but it look me a
bit to learn to navigate it. For playability purposes I'd rather go with
the easier site, in my (amateur) attempt to get the most people involved,
but I'm grateful for your suggestion.
I submit the following Proposal:
Title: Chicken Dinner
Adoption index: 1.0
Author: Yachay
Coauthors:
Body:
{
Create a new Power 1.0 rule titled "Chicken Dinner" that says:
"If this rule has existed in the Ruleset for 7 days or more, then any
Player may perform a Chicken Dinner by announcement, if it has never been
performed previously. When a Chicken Dinner is performed, then the nth
oldest active player by registration date becomes the Winnor Winnor, being
n the first number in the "3 NUMBERS
FROM 1 TO 50" section of https://avkg.com/en/daily-random/. If there would
be no active player in that n-th place, then the Chicken Dinner action
CANNOT be performed. Perfoming a Chicken Dinner is INEFFECTIVE unless it
also unambiguously has a list of all active players ordered by oldest
registration date, and the number mentioned for n corresponding to that
Agoran day.
Upon becoming the Winnor Winnor, that player gains 3 stamps of their own
type, and then this rule repeals itself.
}
On Sunday, March 19, 2023, ais523 via agora-discussion <
agora-discussion@agoranomic.org> wrote:
> On Sun, 2023-03-19 at 11:40 -0700, Yachay Wayllukuq via agora-
> discussion wrote:
> > On Thursday, March 16, 2023, Janet Cobb wrote:
> > > Don't use a "MUST" to impose effectiveness requirements upon an
> > > action.
> > - Unfortunately this isn't evident to me either. Why?
>
> If the requirements aren't met, the message has broken the rules (as
> opposed to the person who sent the message). It's hard to prosecute a
> message for rule-breaking and it probably wouldn't do anything useful.
>
> You want phrasing along the lines of "is INEFFECTIVE unless it" in
> order to cause the message to do nothing, as opposed to causing the
> message to break the rules.
>
> See rule 2152 for definitions of the various capitalised terminology we
> use in our rules.
>
> --
> ais523
>
