Community Garden/Ruleset: Difference between revisions

From Infinite Nomic Wiki
miraheze>Telna
Passed Proposal - Temper - 2021-11-27
Implement Proposal **Sweasons**
 
(32 intermediate revisions by 12 users not shown)
Line 4: Line 4:


=== Players ===
=== Players ===
Any person may become a player by sending a message in any channel in The Community Garden category. A player may stop being a player by announcing their intent in any channel in The Community Garden category or by leaving the Discord server.
Any person may become a player by sending any message in any channel in The Community Garden category. A player may stop being a player by announcing their intent in any channel in The Community Garden category or by leaving the Discord server.


== The Plant ==
=== Measurement ===
At the beginning of the cycle, the plant has 0 leaves and a height of 0 centimeters.
Unless otherwise specified, all measurements of the plant are conducted using centimetres.


== Classes ==
=== Garden Supplies ===
Every person has a Class. The default Class is "Waterer"; any person who has not been assigned another Class is of the default Class.
Bags of Fertilizer are a tracked integer quantity.


Each Class has a number of Class-specific Actions. A person of a Class other than Waterer cannot perform any Actions specific to a Class other than their own. A Waterer who performs an Action specific to a Class other than their own becomes the Class that Action is specific to.
==The Plant==
The plant is a cellular automata.


Any person who does not hold a Role can become a Waterer by posting their intent to do so as a single message in #plant-actions. This action fails if that person has successfully performed any Class-specific Actions within the past 7 days.
===Position===
Each cell has an integer position, which is related to the number of cells it is away from the origin. This position is denoted with a (x,y) notation, where x is the horizontal coordinate relative to the origin with the positive axis pointing right and y is vertical coordinate relative to the origin with the positive axis pointing up. For instance, if one would reference the cell immediately above and to the left of the origin, that would be cell (-1,1).


The following Classes and Class-specific Actions exist:
The origin (0,0) is the bottom-most stem feature that was in place the day the plant became a cellular automata.
* Waterer
** Watering the Plant
* Admirer
** Admiring the Plant
 
== Actions ==
=== Watering ===
Any Waterer may water the plant by posting their intent to do so as a single message in #plant-actions. The first time the plant is watered each day, the plant may attempt to grow. To determine the plant's growth, any person may roll a d10, add any modifiers specified by other rules, and compare the result with the Growth Table.


===Features ===
The plant may have any number of additional features, created via interaction with actions. Each feature has one or more ascii characters that represent that feature in its cell and a rule that describes how that feature may be placed when created. The following type of features exist:
{| class="wikitable"
{| class="wikitable"
|+ Growth Table
|+
! Roll !! Result
!Name
!Ascii
!Rule
|-
|Leaves
|&
|May be placed adjacent to another Branch or Stem
|-
|-
| 1-5 || Nothing Happens.
|Buds
|°
|May be placed adjacent to another Branch or Stem
|-
|-
| || The plant becomes eligible for a development roll today.
|Flowers
|@
|May replace a Bud
|-
|-
| 7-8 || The plant grows 1 centimeter.
|Branches
| -, /, or \
|May be placed adjacent to another Branch or Stem
|-
|-
| 9-10|| The plant sprouts 1 new leaf at its current height.
|Stems
|<nowiki>|</nowiki>
|May be placed in the cell above the existing stem with the greatest y value
|-
|-
| 11+ || If the plant has not grown a bud within 5 centimeters of its current height, the plant grows a new bud at its current height. Otherwise, the plant sprouts 1 new leaf at its current height.
|Bugs
|
|May replace a leaf, flower, or bud. If no leaves, flowers, or buds are on the plant, it can be placed anywhere.
|-
|Fruit
|*
|May replace a flower with at least  one bug adjacent to it.
|}
|}
There are some additional restrictions to this:


=== Admiration ===
* No features may be placed at y-level 0 or below
Any Admirer or Waterer may admire the plant by posting their intent to do so as a single message in #plant-actions. If a Waterer admires the plant, they become an Admirer.
* Only Stems may be placed with an x-coordinate of 0
* Unless a rule states that a feature replaces another, features cannot be placed in a cell that already contains another feature
* Only bugs can be placed while there are bugs in the Feature pile.
* A maximum of 10 bugs can exist in the feature pile. Any additional bugs are not added.
 
There is a collection called the Feature Pile, which may contain features waiting to be placed.
 
== Actions ==
Players and non-player persons may perform actions. Any player rolling dice or randomly selecting from weighted pools to resolve the result of a previous action is not, itself, an action.


If the plant has been admired at least once previously during a day it attempts to grow, +1 is added to the roll on the Growth Table.
=== Caring for the Plant ===
Any player may care for the plant once per day by posting their intent to do so in ⁠#plant-actions. This can take any form, such as watering the plant, checking the health of its soil, or even merely admiring it, so long as the intent is clear. That player may then roll Nd(6+X) and add that number of Growth Points to the plant. X represents the number of fruits on the plant, and N represents the Era of the plant.


=== Photosynthesise ===
Players may always choose that N to be 1 and/or X to be 0 instead of their actual value.
=== Growing ===
A player may spend A number of Growth Points to trigger the plant to grow by stating their intent to do so in #plant-actions. The number of Growth Points to trigger this growth is equal to <code>7 * n + 3.5 * (n^2)</code>, rounded down, where n is the current Era. The first time the plant is triggered to grow each day, any player may select a feature to be added to the Feature Pile by performing a weighted roll on the following table. This action fails if there are not enough Growth Points on the plant to spend.
{| class="wikitable"
|+
!Weight
!Feature
|-
|6
|Leaf
|-
|5
|Branch
|-
|4
|Bud
|-
|3
|Flower
|-
|1
|Stem
|-
|1
|Roll 2 more times on this table, and add all features rolled. Repeat as necessary.
|-
|1
|add a Bug to the feature pile. Roll again on this table, and add all features rolled. Repeat as necessary.
|-
|1
|Bug
|-
|2
|Fruit
|}


Any Waterer or Admirer may attempt to prompt the plant to photosynthesise by posting their intent to do so as a single message in #plant-actions. When a successful photosynthesis action is made, the plant grows 1 centimeter, and the plant enters a photosynthesis cycle. The duration of the photosynthesis cycle is measured in days, and can be determined using the following formula and rounding up to the nearest integer:
=== Placing ===
Any player may select a feature in the Feature Pile to place on the plant by specifying what feature they are placing and the coordinates of the cell they are placing the feature in. A feature of the specified type must exist in the Feature Pile in order to be placed. When a player tries to place a feature it is removed from the Feature Pile. If a player tries to place a feature in a cell in a way that would violate that feature's Rule for placement, the feature is not placed there and falls back into the Feature Pile.


Total length of the plant in centimeters/√(Total number of leaves on the plant) = Photosynthesis cycle duration
After placing a feature, the player who placed it should update the record for gamestate accordingly or ask someone else to - so that the plant may flourish and we may all be informed of its current state.


A photosynthesis cycle will count down at the start of each day, regardless of what time it starts. During a photosynthesis cycle, no "Photosynthesise" actions will succeed.
=== Bug Removal ===
Any player can remove one bug from the plant and spend 20 GP to do so, by posting the intent and the location of the bug to #plant-actions. This can take any form as long as the intent is clear. When a bug is removed, a bag of fertilizer is created.


=== Development ===
=== Fertilizing ===
When the plant is eligible for a development roll, any player who has not previously admired or watered the plant that day may choose a bud and make a development roll for that bud by posting their intent to do so as a single message in #plant-actions.
A player may spend x bags of fertilizer to fertilize the plant and trigger a Growth Spurt, where x is 10 + the current Era number. The first time this happens each day, any player may select new features to be added to the Feature Pile by performing 10 weighted rolls on the table in the Growing rule.


To make a development roll, roll 1d20 and add 1 to the result for every development roll that has been made for that bud previous to the current one. If the sum is 20 or more, the development roll succeeds. Regardless of the result, the plant stops being eligible for a development roll.
== Eras ==
The Plant starts at Era 1. A player can initiate the advance of the Era of the plant by posting the current Era and the next Era in their intent to do so in ⁠#plant-actions. Once that intent has 6 🪴 reactions, any player can reply to that intent to advance to the next Era, by spending a number of Growth Points equal to <code>100 * n</code>, where n is the current Era. Once the Era has advanced, any player may instantly trigger a Growth Spurt without spending any bags of fertilizer, provided no player has already done so.


When a development roll succeeds, the chosen bud becomes a branch.
== Seasons ==
There are six seasons cycled through according to the calendar date.


== Roles ==
Once during each season, one player may request a seasonal bounty, generating some features that are in season. This bounty is then added to the feature pile.
Roles are positions associated with a specific class that can be held by a limited number of persons at a time. In order to hold a Role, a person must be of the class that Role is associated with. A person holding a Role cannot change Classes or perform actions specific to a Class other than their own under any circumstances.


The following Roles (and their associated Classes) exist:
The table below outlines the seasons:
* Plant Keeper (Waterer)
{| class="wikitable"
!Name
!Time
!Bounty
|-
|Frigid
|January and February in odd years, July and August in even years
|2 stems
|-
|Verdant
|March and April in odd years, September and October in even years
|4 leaves and 2 buds
|-
|Blossom
|May and June in odd years, November and December in even years
|3 flowers
|-
|Arid
|July and August in odd years, January and February in even years
|2 bugs
|-
|Rustic
|September and October in odd years, March and April in even years
|3 fruits
|-
|Misted
|November and December in odd years, May and June in even years
|4 branches and 2 stems
|}


=== The Plant Keeper ===
==The Plant Keeper==
The Plant Keeper is a Role held by at most one person. The Plant Keeper is responsible for resolving rules disputes. The Plant Keeper may cease being such by stating so in #plant-keeper.
The Plant Keeper is a player. There is never more than one Plant Keeper at a time. The Plant Keeper is responsible for resolving rules disputes. The Plant Keeper may cease being such by stating so in #plant-keeper.


A request for clarification is an action that shall take the form of a question or statement. The proper response to a question is an action in the form of an answer to that question, and the proper response to a statement is the truth value of that statement.
A request for clarification is an action that shall take the form of a question or statement. The proper response to a question is an action in the form of an answer to that question, and the proper response to a statement is the truth value of that statement.


Upon formal request by a person other than themself, the Plant Keeper shall, as quickly as possible, issue a response to the request. This response shall be binding only to the extent that it reasonably directly pertains to the request, and only to the extent that it does not blatantly and obviously contradict rules text.
Upon formal request by a player other than themself, the Plant Keeper shall, as quickly as possible, issue a response to the request. This response shall be binding only to the extent that it reasonably directly pertains to the request, and only to the extent that it does not blatantly and obviously contradict rules text.


Any Waterer may attempt to become the Plant Keeper by posting their intent to do so as an action in #plant-keeper. If after 7 days the message sent by the person has at least 3 :+1: reactions, and has more :+1: reactions than :-1: reactions, that person becomes the new Plant Keeper.
In order to be the Plant Keeper, a player must be a Gardener. The Plant Keeper cannot change roles or perform actions specific to a role other than a Gardener under any circumstances.


== Proposals ==
If after 7 days the message sent by the player has at least 3 :+1: reactions, and has more :+1: reactions than :-1: reactions, that player becomes the new Plant Keeper.
 
==Proposals==
Any person may make a proposal by sending a message as an action in #plant-proposals. If that message is deleted or modified during its voting period, the proposal is retracted. If there is an active proposal made by a person in the last 7 days, any new proposal they make is immediately retracted. An "active proposal" refers to any proposal that hasn't been retracted and is still in its 7-day voting period.
Any person may make a proposal by sending a message as an action in #plant-proposals. If that message is deleted or modified during its voting period, the proposal is retracted. If there is an active proposal made by a person in the last 7 days, any new proposal they make is immediately retracted. An "active proposal" refers to any proposal that hasn't been retracted and is still in its 7-day voting period.


The voting period for proposals is 7 days. Once a proposal's voting period ends, if there are more votes in favor than against, the proposal takes effect.
The voting period for proposals is 7 days. Once a proposal's voting period ends, if there are more votes in favor than against, the proposal takes effect.


A :+1: or :-1: reaction on a Proposal message at the time when the voting period ends constitutes a vote in favor or against, respectively.
A 👍 or 👎 reaction on a Proposal message at the time when the voting period ends constitutes a vote in favor or against, respectively.
 
== 4sts's Agreement ==
Players may choose to be critics, who are trolls instead of humans by announcing such in the Plant-Chatter channel of the discord, this however has no gameplay effect

Latest revision as of 21:56, 30 November 2024

Info[edit | edit source]

Time[edit | edit source]

All times mentioned in this ruleset are in UTC. Days start at 00:00 UTC.

Players[edit | edit source]

Any person may become a player by sending any message in any channel in The Community Garden category. A player may stop being a player by announcing their intent in any channel in The Community Garden category or by leaving the Discord server.

Measurement[edit | edit source]

Unless otherwise specified, all measurements of the plant are conducted using centimetres.

Garden Supplies[edit | edit source]

Bags of Fertilizer are a tracked integer quantity.

The Plant[edit | edit source]

The plant is a cellular automata.

Position[edit | edit source]

Each cell has an integer position, which is related to the number of cells it is away from the origin. This position is denoted with a (x,y) notation, where x is the horizontal coordinate relative to the origin with the positive axis pointing right and y is vertical coordinate relative to the origin with the positive axis pointing up. For instance, if one would reference the cell immediately above and to the left of the origin, that would be cell (-1,1).

The origin (0,0) is the bottom-most stem feature that was in place the day the plant became a cellular automata.

Features[edit | edit source]

The plant may have any number of additional features, created via interaction with actions. Each feature has one or more ascii characters that represent that feature in its cell and a rule that describes how that feature may be placed when created. The following type of features exist:

Name Ascii Rule
Leaves & May be placed adjacent to another Branch or Stem
Buds ° May be placed adjacent to another Branch or Stem
Flowers @ May replace a Bud
Branches -, /, or \ May be placed adjacent to another Branch or Stem
Stems | May be placed in the cell above the existing stem with the greatest y value
Bugs May replace a leaf, flower, or bud. If no leaves, flowers, or buds are on the plant, it can be placed anywhere.
Fruit * May replace a flower with at least one bug adjacent to it.

There are some additional restrictions to this:

  • No features may be placed at y-level 0 or below
  • Only Stems may be placed with an x-coordinate of 0
  • Unless a rule states that a feature replaces another, features cannot be placed in a cell that already contains another feature
  • Only bugs can be placed while there are bugs in the Feature pile.
  • A maximum of 10 bugs can exist in the feature pile. Any additional bugs are not added.

There is a collection called the Feature Pile, which may contain features waiting to be placed.

Actions[edit | edit source]

Players and non-player persons may perform actions. Any player rolling dice or randomly selecting from weighted pools to resolve the result of a previous action is not, itself, an action.

Caring for the Plant[edit | edit source]

Any player may care for the plant once per day by posting their intent to do so in ⁠#plant-actions. This can take any form, such as watering the plant, checking the health of its soil, or even merely admiring it, so long as the intent is clear. That player may then roll Nd(6+X) and add that number of Growth Points to the plant. X represents the number of fruits on the plant, and N represents the Era of the plant.

Players may always choose that N to be 1 and/or X to be 0 instead of their actual value.

Growing[edit | edit source]

A player may spend A number of Growth Points to trigger the plant to grow by stating their intent to do so in #plant-actions. The number of Growth Points to trigger this growth is equal to 7 * n + 3.5 * (n^2), rounded down, where n is the current Era. The first time the plant is triggered to grow each day, any player may select a feature to be added to the Feature Pile by performing a weighted roll on the following table. This action fails if there are not enough Growth Points on the plant to spend.

Weight Feature
6 Leaf
5 Branch
4 Bud
3 Flower
1 Stem
1 Roll 2 more times on this table, and add all features rolled. Repeat as necessary.
1 add a Bug to the feature pile. Roll again on this table, and add all features rolled. Repeat as necessary.
1 Bug
2 Fruit

Placing[edit | edit source]

Any player may select a feature in the Feature Pile to place on the plant by specifying what feature they are placing and the coordinates of the cell they are placing the feature in. A feature of the specified type must exist in the Feature Pile in order to be placed. When a player tries to place a feature it is removed from the Feature Pile. If a player tries to place a feature in a cell in a way that would violate that feature's Rule for placement, the feature is not placed there and falls back into the Feature Pile.

After placing a feature, the player who placed it should update the record for gamestate accordingly or ask someone else to - so that the plant may flourish and we may all be informed of its current state.

Bug Removal[edit | edit source]

Any player can remove one bug from the plant and spend 20 GP to do so, by posting the intent and the location of the bug to #plant-actions. This can take any form as long as the intent is clear. When a bug is removed, a bag of fertilizer is created.

Fertilizing[edit | edit source]

A player may spend x bags of fertilizer to fertilize the plant and trigger a Growth Spurt, where x is 10 + the current Era number. The first time this happens each day, any player may select new features to be added to the Feature Pile by performing 10 weighted rolls on the table in the Growing rule.

Eras[edit | edit source]

The Plant starts at Era 1. A player can initiate the advance of the Era of the plant by posting the current Era and the next Era in their intent to do so in ⁠#plant-actions. Once that intent has 6 🪴 reactions, any player can reply to that intent to advance to the next Era, by spending a number of Growth Points equal to 100 * n, where n is the current Era. Once the Era has advanced, any player may instantly trigger a Growth Spurt without spending any bags of fertilizer, provided no player has already done so.

Seasons[edit | edit source]

There are six seasons cycled through according to the calendar date.

Once during each season, one player may request a seasonal bounty, generating some features that are in season. This bounty is then added to the feature pile.

The table below outlines the seasons:

Name Time Bounty
Frigid January and February in odd years, July and August in even years 2 stems
Verdant March and April in odd years, September and October in even years 4 leaves and 2 buds
Blossom May and June in odd years, November and December in even years 3 flowers
Arid July and August in odd years, January and February in even years 2 bugs
Rustic September and October in odd years, March and April in even years 3 fruits
Misted November and December in odd years, May and June in even years 4 branches and 2 stems

The Plant Keeper[edit | edit source]

The Plant Keeper is a player. There is never more than one Plant Keeper at a time. The Plant Keeper is responsible for resolving rules disputes. The Plant Keeper may cease being such by stating so in #plant-keeper.

A request for clarification is an action that shall take the form of a question or statement. The proper response to a question is an action in the form of an answer to that question, and the proper response to a statement is the truth value of that statement.

Upon formal request by a player other than themself, the Plant Keeper shall, as quickly as possible, issue a response to the request. This response shall be binding only to the extent that it reasonably directly pertains to the request, and only to the extent that it does not blatantly and obviously contradict rules text.

In order to be the Plant Keeper, a player must be a Gardener. The Plant Keeper cannot change roles or perform actions specific to a role other than a Gardener under any circumstances.

If after 7 days the message sent by the player has at least 3 :+1: reactions, and has more :+1: reactions than :-1: reactions, that player becomes the new Plant Keeper.

Proposals[edit | edit source]

Any person may make a proposal by sending a message as an action in #plant-proposals. If that message is deleted or modified during its voting period, the proposal is retracted. If there is an active proposal made by a person in the last 7 days, any new proposal they make is immediately retracted. An "active proposal" refers to any proposal that hasn't been retracted and is still in its 7-day voting period.

The voting period for proposals is 7 days. Once a proposal's voting period ends, if there are more votes in favor than against, the proposal takes effect.

A 👍 or 👎 reaction on a Proposal message at the time when the voting period ends constitutes a vote in favor or against, respectively.

4sts's Agreement[edit | edit source]

Players may choose to be critics, who are trolls instead of humans by announcing such in the Plant-Chatter channel of the discord, this however has no gameplay effect