Friday, May 31, 2024

Proposal: Making It Count

Popular, 4-0. Enacted by JonathanDark.

Adminned at 01 Jun 2024 14:50:30 UTC

In the rule “Fragments”, replace “The Publisher is encouraged to publicly track the number of Fragments that they have received” with “The Publisher is encouraged to publicly track the number of Storytellers who have sent valid Fragments to them”.

In the rule “Scoring”, replace “The Publisher should publicly track the number of Scoring Responses received for an Open Judging, and may re-use the same tracking gamestate for subsequent Open Judgings as long as the count of Scoring Responses received is reset each time a new Judging is Open.” with “The Publisher should publicly track the number of Storytellers who have sent valid Scoring Responses for an Open Judging, and may re-use the same tracking gamestate for subsequent Open Judgings as long as the count of Storytellers who sent valid Scoring Responses is reset each time a new Judging is Open.”

Somebody abused the system by sending multiple Scoring Responses. Since it’s a Virtual Action with no other limitations, I had to count the actual number of Scoring Responses received, when we actually want to track the number of Storytellers who sent them.

Comments

Clucky: he/him

31-05-2024 16:01:42 UTC

Do we also need to make sure those counts reset each round?

JonathanDark: he/him

31-05-2024 17:26:11 UTC

The Scoring Response count already has such language to reset it, and the Fragments count says “The Publisher is encouraged to publicly track the number of Fragments that they have received since the most recent Drawing”, so every time there is a new Drawing, the count of “since the most recent Drawing” only counts the Fragments since that Drawing.

JonathanDark: he/him

31-05-2024 17:28:52 UTC

And with this Proposal’s replacement text, the Fragment rule would read as follows:

“The Publisher is encouraged to publicly track the number of Storytellers who have sent valid Fragments to them since the most recent Drawing”

Clucky: he/him

31-05-2024 17:31:32 UTC

got it makes sense

GloopyGhost:

31-05-2024 21:44:33 UTC

for

Darknight: he/him

31-05-2024 23:11:51 UTC

for

Kevan: he/him

01-06-2024 10:48:27 UTC

for