I have a few proposals centered around a semi-solo game of collecting a set
of items. As you gather more items, there are more blocking plays
available, but not so much that you absolutely can't get a win, it just
gets more unlikely. The only reason to team up is to prevent others from
winning, and to make sure no one is preventing you from winning, so it's
not 100% a pooling strategy.
At least, that's the intention.
Mostly just want to confirm there's no hidden scams among these first three
that detail the primary gameplay that I may have missed. Then there's two
more that lean more towards the win conditions.
{
Title: Let them have cake
Adoption Index: 1.0
Author: 4st
Co-author(s): secretsnail9, Jason, Murphy
Enact a new rule with Power=1.0 titled 'Desserts', with the text:
{
The Cookor is an office, and the recordkeepor of desserts.
For each dessert, <type> Dessert Ownership is a secured
negative boolean player switch.
The number of Desserts a player owns is the number of eir
Dessert Ownership switches that are set to True.
The desserts are as follows:
1. Rosemary Citrus Sorbet
2. Banana split
3. Baklava
4. Pistachio Cannoli
5. Apple Fritter
6. Creme brulee
7. Chocolate souffle
8. Blood Orange Galette
9. Tres Leches Cake
10. Grape Popsicle
11. Pavolova
12. Cherry Cobbler
13. Lemon meltaways
14. Banana Pudding
15. Baked Alaska
16. Pecan Pie
17. Blondies
18. Lobster Ice Cream
19. Apple Brie Tart
20. Poffergies
21. Churros
22. Ghost Pepper Toffee
23. Chocolate Covered Ants
24. Tiramisu
25. Grilled Pears with Raspberry
}
}
{
Title: Getting Just Desserts
Adoption Index: 1.0
Author: 4st
Co-author(s): secretsnail, Jason, Murphy
Enact the following rule with power=1.0 titled
"Potluck Parties" with the following text:
{
Each player CAN intend to grab a dessert ONCE each week,
by announcement, with the specific dessert being a public secret.
(See the ACORN on Secret Auctions)
A player that intends to grab more than one dessert in a week
fails to intend to grab any dessert.
Colliqually, this is known as the Dessert Signup Period.
At the beginning of each week, each player who intended to grab
a dessert, announces what dessert they intended to grab.
A player that fails to do so by the end of the week fails to
intend to grab any dessert.
Colliqually, this is the Dessert Chaos Period.
At the beginning of next week, for each dessert,
if only one player has a revealed intention to grab that dessert,
that player has eir Dessert Ownership Flag for
that Dessert type flipped to True.
Colliqually, this is the Dessert Resolution Period.
}
}
{
Title: Desserts Are Too Easy
Adoption Index: 1.0
Author: 4st
Co-author(s): secretsnail, Murphy, Jason
Enact the following rule with power=1.0 titled
"Food-Borne Illness" with the text:
{
At the beginning of each week, the Cookor
will publicly roll a 1d10, then add 5.
Let the resulting number be called N
for the context of this rule.
All players who have N Dessert Ownership Switches
flipped to True will have all eir Dessert
Ownership Switches flipped to False.
}
}
And these are the reasons to play I have, but of course, maybe those ones
don't pass.
{
Title: Livin' the pie life
Adoption Index: 1.0
Author: 4st
Co-author(s): secretsnail
Enact the following rule with power=1.0 titled "Eating"
with the following text:
{
A player CAN Flip eir own <type> Dessert Ownership switch
from True to False. A player that does so gains 1 point.
Colliqually, this is "eating" a dessert.
}
}
{
Title: Dessert Win Condition When
Adoption Index: 1.0
Author: 4st
Co-author(s): secretsnail, Murphy, Jason
Enact the following rule with power=1.0 titled
"Potluck Master" with the text:
{
If a player has 15 or more Dessert Ownership Switches
flipped to True, that player MAY announce that
e is the Potluck Master. That player wins,
and all eir Dessert Ownership Switches are set to False.
}
}
