Mischief wrote:
On 3/25/25 9:14 PM, secretsnail9 via agora-business wrote:
Having received 1 support from Mischief and no objections, I do so.
I suggest the following Pre-Proposal ("Agoran Bingo"):
[The person running a bingo game is often called the caller. Agoran
spelling would make that Callor. My eyes want to read that as "caal-
lore" and since it's the same letters, I just changed it to Collar out
of whimsy.]
Given where bingo games often occur, a priest's collar seems apt.
* one or more methods for players to select a bingo board; the Collar
SHOULD define these methods such that:
** there is at least one method that permits a player to keep eir bingo
board secret until e calls bingo
** a player cannot change eir selection once made
** a player cannot choose in advance with certainty the board e will end
up with
Presumably this would be something like:
* player makes a commitment to a document containing some ordered lists
of code values
* Collar makes a commitment to a document mapping those code values to
actual values
* Collar reveals eir commitment before flipping the bingo state to
unpaused for the first time in a bingo round
"Bingo round" suggests a general extension of how Rule 1023 (Agoran
Time) defines pivots/rounds/games:
* for each defined method (hereafter <method>) of winning the game:
** a <method> pivot is either the instant at which <method> was first
defined or an instant at which at least one person won the game via
<method>
** a <method> round (syn. <method> game) is the period of time between a
<method> pivot and the next <method> pivot
When a player successfully calls bingo, e wins the game, the bingo state
is flipped to paused, and all existing bingo board selections are null
and void.
Is it intentional that only one player can win each bingo round, even if
another player could have also called bingo at that time?
--
[ANSC H:GE V:G B:0]
