Community Garden/Ruleset: Difference between revisions

From Infinite Nomic Wiki
← Older edit
VisualWikitext
miraheze>Nyhilo
Implement Proposal: **Rules Cleanup🧹**
Implement Proposal **Sweasons**
Β 
(18 intermediate revisions by 8 users not shown)
Line 9: Line 9:
Unless otherwise specified, all measurements of the plant are conducted using centimetres.
Unless otherwise specified, all measurements of the plant are conducted using centimetres.


=== Seasons ===
=== Garden Supplies ===
At every point in time, it is one of three seasons, ordered as follows: Growth, Harvest, or Frost. On the first and fifteenth day of each month, the season changes to the next in the list.
Bags of Fertilizer are a tracked integer quantity.


== The Plant ==
==The Plant==
At the beginning of the cycle, the plant has a trunk with 0 features and a height of 0 centimetres.
The plant is a cellular automata.


=== Branches ===
===Position===
The plant consists of a number of branches. Every branch has a parent branch, except for the trunk. When a branch comes into existence, it does so with 0 leaves and a length of 1 centimeter. The trunk is considered to be a branch for the purposes of this Ruleset.
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).


=== Nesting Level ===
The origin (0,0) is the bottom-most stem feature that was in place the day the plant became a cellular automata.
Every branch has a Nesting Level, defined in the following way: The trunk has a Nesting Level of 0, and every other branch has a Nesting Level equal to one more than the Nesting Level of its parent branch.


=== Position ===
===Features ===
All features on the plant have a position, which is equal to the length of their parent branch upon the feature coming into existence. This position does not change if the length of the parent branch does.
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:
Β 
=== Identifiers (ID) ===
Every unique feature with a Nesting Level of 1 or more will additionally have a unique identifier or "ID", defined in the following way: Each unique feature identifier will begin with its position in centimetres (eg. 7 for 7cm) on its parent feature. Additionally, any feature on a shared position will incrementally be further identified with a lowercase English character in the sequence of the English alphabet, beginning with a and progressing to z. If additional features require identifiers beyond z, continue incrementing by doubling, then tripling the character identifier. (Ex. aa => zz, then aaa => zzz). Subsequent features will continue to be identified with this pattern as necessary.
Β 
Additionally, each unique feature identifier will contain positional information, starting with the unique identifier of each of its parent features beginning with Nesting Level 1 and proceeding to the feature's Nesting Level.
Β 
As a result, any unique feature can be referred to using the following format:
Β 
{Feature Type}@{Parent Identifiers}-{Unique Identifier}
Β 
Example references to features may look like:
Β 
* leaf@7c: A leaf with Nesting Level 1, which is the 3rd feature at position 7cm.
* branch@13c-4d: A branch with Nesting Level 2, which is the 4th feature at position 4cm growing from parent feature branch@13c.
* flower@17e-3b-6: A flower with Nesting Level 3, which is the only feature at position 6cm growing from parent feature branch@3b, which in turn is growing from parent feature branch@17e.
Β 
=== Features ===
The plant may have any number of additional features, created via interaction with role-specific and plant-specific actions. The following type of features exist:
Β 
* Leaves
* Buds
* Branches
* Flowers
* Fruits
Β 
=== Parents & Children ===
When a feature comes into existence, the feature it grows upon is referred to as its parent. Additionally, any features that are grown from a feature are referred to as its children. The Trunk has no parent.
Β 
== Plant Growth ==
=== General Growth ===
When the plant attempts to grow, any player may randomly select a weighted result from the General Growth Pool according to the current season.
{| class="wikitable"
{| class="wikitable"
|+ General Growth Pool
|+
! rowspan="2" | Result !! colspan="3" | Entries
!Name
!Ascii
!Rule
|-
|-
!Growth
|Leaves
!Harvest
|&
!Frost
|May be placed adjacent to another Branch or Stem
|-
|-
| Nothing Happens. || 5
|Buds
|5
|Β°
|5
|May be placed adjacent to another Branch or Stem
|-
|-
| The trunk grows 1 centimeter. || 3
|Flowers
|2
|@
|2
|May replace a Bud
|-
|-
|The trunk sprouts 1 new leaf at its current height.
|Branches
|0
| -, /, or \
|1
|May be placed adjacent to another Branch or Stem
|0
|-
|-
|The plant becomes eligible for a coronation roll today
|Stems
|4
|<nowiki>|</nowiki>
|2
|May be placed in the cell above the existing stem with the greatest y value
|2
|-
|-
|The plant becomes eligible for a development roll today.
|Bugs
|1
|࢞
|3
|May replace a leaf, flower, or bud. If no leaves, flowers, or buds are on the plant, it can be placed anywhere.
|1
|-
|-
|If the trunk has not grown a bud within 5 centimeters of its current height, the trunk grows a new bud at its current height. Otherwise, the trunk sprouts 1 new leaf at its current height.
|Fruit
|2
|*
|2
|May replace a flower with at leastΒ  one bug adjacent to it.
|0
|}
|}
There are some additional restrictions to this:


=== Photosynthesis ===
* No features may be placed at y-level 0 or below
Β 
* Only Stems may be placed with an x-coordinate of 0
When the plant is eligible for photosynthesis, any player 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 enters a photosynthesis cycle, then may immediately attempt to grow 1d6 times. 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:
* Unless a rule states that a feature replaces another, features cannot be placed in a cell that already contains another feature
(Total length of the plant in centimeters)/√(Total number of leaves on the plant) = Photosynthesis cycle duration
* Only bugs can be placed while there are bugs in the Feature pile.
A photosynthesis cycle will count down at the start of each day, regardless of what time it starts. When the photosynthesis cycle ends, the plant becomes eligible for photosynthesis again.
* A maximum of 10 bugs can exist in the feature pile. Any additional bugs are not added.
Β 
=== Development ===
When the plant is eligible for a development roll, any player 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.


To make a development roll, roll 1d10 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 10 or more, the development roll succeeds. Regardless of the result, the plant stops being eligible for a development roll.
There is a collection called the Feature Pile, which may contain features waiting to be placed.


When a development roll succeeds, any person can roll 1dN, where N is one plus the Nesting Level of the branch the chosen bud grew from. If the result of this roll is 1, the chosen bud becomes a branch, and its parent branch is the branch the chosen bud grew from. Otherwise, the chosen bud becomes a flower.
== 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.


=== Coronation ===
=== Caring for the Plant ===
If no branch is specified when performing this action, the specified branch is the 0th level branch of the plant (the trunk).
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.


When the plant becomes eligible for a coronation roll, any player may make a coronation roll on the specified branch. To make a coronation roll, randomly select a child branch among the direct children of the selected branch, then roll on the Coronation Pool for the selected child branch according to the current season. Regardless of the result, the plant stops being eligible for a coronation roll.
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"
{| class="wikitable"
|+Coronation Pool
|+
! rowspan="2" |Result
!Weight
! colspan="3" |Entries
!Feature
|-
|6
|Leaf
|-
|5
|Branch
|-
|4
|Bud
|-
|-
!Growth
|3
!Harvest
|Flower
!Frost
|-
|-
|The branch becomes eligible for a development roll today.
|2
|1
|1
|1
|Stem
|-
|-
|The branch grows by 1 centimeter.
|2
|1
|1
|1
|Roll 2 more times on this table, and add all features rolled. Repeat as necessary.
|-
|-
|The branch sprouts 1 new leaf at its current length.
| 1
|2
|1
|1
|add a Bug to the feature pile. Roll again on this table, and add all features rolled. Repeat as necessary.
|-
|-
|If the branch has any sub branches, perform the Coronation action specifying this branch. Otherwise, the branch sprouts 1 new leaf at its current length
|1
|1
|1
|1
|Bug
|-
|-
|If the branch has not grown a bud within 5 centimeters of its current height, the branch grows a new bud at its current height. Otherwise, the branch sprouts 1 new leaf at its current height.
| 1
|2
|2
|1
|Fruit
|}
|}


== Roles ==
=== Placing ===
Players may have a role. The roles a player may have are defined by the rules with 'Role:' in their title, and actions defined with that rule are actions specific to that role. Players may perform actions specific to their role by posting their intent to do so as a single message in #plant-actions.
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.


If a player does not have a role or has not changed roles within the past 7 days, the player may change roles by posting their intent to perform any action specific to that role as a single message in #plant-actions. The players role is changed, and then the action is performed.
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.


==Role: Admirer ==
=== Bug Removal ===
===Admiration ===
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.
Any Admirer may admire the plant. When they do so, they may optionally specify a valid result that could exist in the current Trunk Growth Pool.


If the plant has been admired at least once previously during a day it attempts to grow, add 1 entry of the specified result for that roll attempt. If no result is specified, add 1 entry of the following result for that roll attempt:
=== Fertilizing ===
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.


"If the trunk has not grown a bud within 5 centimeters of its current height, the trunk grows a new bud at its current height. Otherwise, the trunk sprouts 1 new leaf at its current height."
== 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.


==Role: Critic==
== Seasons ==
===Criticism===
There are six seasons cycled through according to the calendar date.
Any Critic may critique the plant or a player's action that was done that day.


If the plant has been critiqued at least once previously during a day it attempts to grow, then for that roll attempt:
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.


*Add 2 entries of "The plant becomes eligible for a development roll today."
The table below outlines the seasons:
*If the plant had not been also admired at least once previously during that day, instead add 1 entry of "Nothing Happens."
{| class="wikitable"
If a watering action is critiqued, the plant that was watered can attempt to grow again on the second time the plant is watered that day, but only if the second watering comes after the critique, and from the player who did the critiqued action.
!Name
Β 
!Time
If an admire action is critiqued, the second time the plant is admired, double the number of entries added via the admiration for that plant, but only if the second admiration happens after the critique and from the player who did the critiqued action.
!Bounty
Β 
|-
If a caretaker action is critiqued, the player of that action will learn from the inefficiency, and will not become fatigued on their first action the next day, unless they fall off the plant.
|Frigid
Β 
|January and February in odd years, July and August in even years
After a Critic has performed their third critique in a day, additional critiques from that player on that day have no effect. These additional critiques can not be taken seriously.
|2 stems
Β 
|-
==Role: Gardener ==
|Verdant
Β 
|March and April in odd years, September and October in even years
===Watering===
|4 leaves and 2 buds
Any Gardener may water the plant. The first time the plant is watered each day, the plant may attempt to grow.
|-
Β 
|Blossom
===Composting===
|May and June in odd years, November and December in even years
Any Gardener may create a bag of fertilizer for the plant. The bag of fertilizer is made from features in the composting pile. If a feature was in the composting pile at the beginning of a day, it has decomposed some and can be used to make one bag of fertilizer that day. When a bag of fertilizer is made from a feature, that feature is destroyed.
|3 flowers
Β 
|-
===Fertilizing ===
|Arid
Any Gardener may apply bags of fertilizer to the plant, as long as fertilizer is available. Bags of fertilizer are kinda tiny, so they can only be applied in integer quantities. Once a bag is applied, it is consumed whether or not the fertilizer has an effect.
|July and August in odd years, January and February in even years
Β 
|2 bugs
If the plant is not in a photosynthesis cycle, then when the total bags of applied fertilizer is at least (sum of length of all branches combined)/10 bags, 1 d6 is added to the number of growth rolls the next time a photosynthesis cycle is triggered on the plant. Fertilizer can only do so much, so this effect can only apply once to a photosynthesis cycle. The amount of applied fertilizer is reset to zero whenever the plant's cycle changes.
|-
Β 
|Rustic
The first time per day a bag of fertilizer is applied to the plant while it is in a photosynthesis cycle, then the cycle time is reduced by one day.
|September and October in odd years, March and April in even years
Β 
|3 fruits
==Role: Caretaker==
|-
Β 
|Misted
Caretakers are very small. When a player becomes a Caretaker, they shrink down to a hundredth their size (generally somewhere around 1.75cm tall) before they do anything else.
|November and December in odd years, May and June in even years
Β 
|4 branches and 2 stems
Because of their small size, Caretakers become fatigued very easily for even simple actions. If they are fatigued, a Caretaker is unable to do any action and must rest. Should they cease to be Caretakers, players return to the size they were before they became Caretakers.
|}
Β 
===Climbing===
Caretakers may climb to a specific location on the plant. If no location is specified, the player will climb to the lowest feature that is the tip of a branch. In the event of a tie, this feature is chosen randomly among the tied features. After climbing, a Caretaker will be fatigued for the rest of the day.
Β 
===Pruning ===
Any Caretaker may prune a feature at their current location on the plant. By pruning the plant, the plant will lose the feature at that location. If a Caretaker attempts to prune a branch, the thickness and hardness of the plant will cause them to become fatigued for the rest of the day, and their attempt to prune will fail.
Β 
If a feature is successfully pruned:
*It falls below into the composting pile, stored as the kind of feature it was on the plant.
*The plant will become eligible for a coronation roll at the beginning of the next day.
*The Caretaker who pruned the plant rolls 1d3. If they roll a 1, they fall off the plant. Though unharmed, this takes a lot out of a little Caretaker! If they fall of the plant, they become fatigued for the rest of the day, and for the entirety of the next day. If they do not fall of the plant, they still become fatigued for the rest of the day due to the hard work involved.
Β 
If the plant has been pruned at least once on the day previous to a day it attempts to grow, remove 1 entry of 'Nothing Happens.' for that roll attempt.
Β 
===Pollinating===
Any Caretaker may pollinate a flower at their current location. In doing so, they get fluffy pollen from that flower all over them. If they had pollen on them from a different flower than the one they are pollinating, that pollen is removed from them, and the flower becomes pollinated. After pollinating, a Caretaker will be fatigued for the rest of the day.


==The Plant Keeper==
==The Plant Keeper==
Line 218: Line 167:
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.
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.


Any Gardener 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 player has at least 3 :+1: reactions, and has more :+1: reactions than :-1: reactions, that player becomes the new Plant Keeper.
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==
==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.


Line 226: Line 175:


A πŸ‘ or πŸ‘Ž 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

Retrieved from "https://infinite.nomic.space/wiki/index.php?title=Community_Garden/Ruleset&oldid=7456"