Proposal Archive:
Proposal (Thomas)
proposed prior to 5 June 2000
adopted on 7 June 2000
I propose to add the following (rule) to the ruleset:
"The Ruleset is divided in rules, identified by an identification string. This
string has to be composed of words (a-z,A-Z,0-9) separated by dots.
Every proposal must define an identification string in order to create a new
rule."
to give this rule the string "rules.numbers"
and to move the existing rules in the following categories:
"rules.amending"
> The ruleset may be changed only if all players agree
on that same
> proposed change, unless the ruleset is changed by
application of one
> or more parts (rules) of the ruleset itself.
"players.list"
> Players List
> the players of the game are:
>
> Mike (chaseangel@hotmail.com)
> Thomas (thomas@hirsch.org)
> Zagarna II (zagarna@yahoo.com)
"players.quitting"
> Players are removed from the players list, when they
did not
> make any
> game-relevant action during 30 consecutive days.
> A player may be removed from the list, if e
communicates this
> intent to all players on the list.
"players.joining"
> Anyone is added to the players list, if e communicates
this
> intent to all
> players on the list.
Proposal (Thomas)
proposed prior to 5 June 2000
Adopted on 8 June 2000
I propose the following new rules:
(ignore the categories, if my last proposal did not
succeed)
_winning.list____________________________________________________
The winning list is a list of players or people having played GNomic. It is
initially empty. Once a player wins the game, his name is added to the
winning list, together with the time and reason of his win. The game does
not end, when a player is a winner. A player may win GNomic multiple
times.
Proposal (Thomas)
proposed prior to 5 June 2000
Adopted on 8 June 2000
_winning.score_________________________________________________
The official currency of GNomic are Gnomes. They live in the earth in burrow-like homes. They may be owned by players. Initially, there are no Gnomes in GNomic.
Proposal (Thomas)
proposed prior to 5 June 2000
Defeated; proposal retired by rule proposals.removal
on 8 June 2000
_winning.winner________________________________________________
The goal of GNomic is to have a Gnome Clan (1000 Gnomes). A player having a Gnome Clan has won GNomic. However, Gnome Clans tend to have a short life span, as Gnomes do not like company. Thus, a Gnome Clan disappears after having celebrated the winner with a large ceremony and large quantities of alcoholica.
Proposal (Zagarna II)
proposed prior to 5 June 2000
Adopted 20 June 2000
i propose the following new rules:
_GNomic.name_______________________________________________________________________
The name of this game is GNomic_Gnomes.mantainance.Mines___________________________________________________________
Gnomes live in Mines under the earth. Mines may be owned by players.
Mines may not be traded by players. Every specific Mine has a name, chosen when that Mine is originally created.
In order to possess Gnomes a player must own a Mine for the Gnomes to live in. Every Mine may hold 400 Gnomes.
Initially, there are no Mines in GNomic.
Proposal marsh.1 (The Governor)
proposed on 6 June 2000
Defeated; proposal retired by rule proposals.removal
on 8 June 2000
(1) Repeal the rule "rules.amending".
(2) Add the following rule:
rules___________
These rules shall govern the game of Gnomic. These rules may not be changed except as specified therein.
(3) Add the following rule:
rules.limitations_____
The rules shall not prohibit a player from leaving the game. A player shall always have the option of leaving the game, instead of
suffering any penalty assessed by the rules.
(4) Add the following rule:
proposals_______
A proposal to change the rules may be made by publishing such proposal to all players.
(5) Add the following rule:
proposals.numbers____
Each proposal shall have a unique identifier. This identifier shall consist of two words separated by a dot (period). The first word shall be unique to each player, and shall be the same on all proposals made by any one player. Both words shall consist only of lower- and upper-case roman letters and arabic digits.
(6) Add the following rule:
proposals.voting____
Upon receipt of a proposal, a player may vote on its passage by publishing such vote to all players.
(7) Add the following rule:
proposals.voting.options_____
A vote shall be one of the following: SUPPORT, OPPOSE, or ABSTAIN.
(8) Add the following rule:
proposals.passage________
A proposal shall be adopted if all players have voted SUPPORT. The rule change proposed shall then be made, unless such change is forbidden by the rules.
Proposal marsh.2 (The Governor)
Proposed on 6 June 2000
Adopted on 7 June 2000
Add the following rule:
tabulator________
The Tabulator shall count all votes cast on each proposal. When the outcome is assured, or when any prescribed voting period has ended, the Tabulator shall publish the results of the vote to all players. Should a proposal be reported by the Tabulator as being adopted, it shall have effect immediately after such publication.
Proposal marsh.3 (The Governor)
Proposed on 6 June 2000
Defeated; proposal retired by rule proposals.removal
on 8 June 2000
Add the following rule:
proposals.withdrawing______
After making a proposal, a player may withdraw it by publishing his intent to do so, to all players. In any official archive, the proposal shall be marked as "withdrawn," and shall not affect gameplay. A proposal may not be withdrawn after it has been adopted.
Proposal marsh.4 (The Governor)
Proposed on 6 June 2000
Defeated; proposal retired by rule proposals.removal
on 8 June 2000
Add the following rule:
players.list.changing______
(1) Each time a player joins Gnomic, his name and Email address shall be added to rule "players.list".
(2) Each time a player leaves Gnomic, his name and Email address shall be removed from rule "players.list".
(3) This rule shall have priority over rule "players.list".
Proposal marsh.5 (The Governor)
Proposed on 7 June 2000
Adopted on 8 June 2000
(1) Repeal the rule "rules.amending".
(2) Add the following rule:
rules___________
This ruleset shall govern the game of Gnomic. The rules may not be changed except as specified therein.
(3) Add the following rule:
proposals_______
A proposal to change the rules may be made by publishing such proposal to all players.
(4) Add the following rule:
proposals.voting____
Upon receipt of a proposal, a player may vote on its passage by communicating such vote to the Tabulator, or, if there is no Tabulator, to all players.
(5) Add the following rule:
proposals.voting.options_____
A vote shall be one of the following: SUPPORT, OPPOSE, or ABSTAIN.
(6) Add the following rule:
proposals.voting.abstention.passive______
If an official voting period is specified, any player casting no vote on a proposal within such period shall be considered to have cast a vote of ABSTAIN. This may be referred to as passively abstaining, or passive abstention.
(7) Add the following rule:
proposals.passage________
A proposal shall be adopted if all players have voted SUPPORT. The rule change proposed shall then be made, unless such change is forbidden by the rules.
Proposal marsh.6 (The Governor)
Proposed on 7 June 2000
Adopted on 8 June 2000
Add the following rule:
proposals.numbers____
Each proposal shall have a unique identifier. This identifier shall consist of two words separated by a dot (period). The first word shall be unique to each player, and shall be the same on all proposals made by any one player. Both words shall consist only of lower- and upper-case roman letters and arabic digits.
Proposal marsh.7 (The Governor)
Proposed on 7 June 2000
Adopted on 8 June 2000
Amend the rule "players.quitting", to read in its entirety:
A player's name and Email address shall be removed from rule "players.list" if he does not make any game-relevant action during 30 consecutive days. A player's name and Email address shall be added to rule "players.list" if he communicates his intent to join the game to all players listed in the rule. A player's name and Email address shall be removed from rule "players.list" if he communicates his intent to leave the game to all players listed in the rule.
proposal
zagarna.nofailedproposals (Zagarna II)
Proposed on 8 June 2000
Defeated on 8 June 2000
create a new rule named
proposals.removal
Whenever a proposal is voted AGAINST it is considered a failed proposal and no longer a pending proposal. Players do not need to vote on failed proposals.
Failed proposals should be removed from the "current proposals" (or equivalent) page on the gnomic website (provided the site mantainer has the time and will to do so).
proposal zagarna.2 (Zagarna II)
Proposed on 8 June 2000
Adopted on 8 June 2000
create following rule named
proposals.removal
Whenever a proposal is voted AGAINST or ABSTAIN it is considered a failed proposal and no longer a pending proposal. Players do not need to vote on failed proposals.
Failed proposals should be removed from the "current proposals" (or equivalent) page on the gnomic website (provided the site mantainer has the time and will to do so).
Proposal rg.1 (RG)
proposed 9 June 2000
adopted 10 June 2000
Amend the rule "players.quitting", to read in its entirety:
players.listmaintenence
A player's name and Email address shall be removed from rule "players.list" if he does not make any game-relevant action during 30 consecutive days. A player's name and Email address shall be added to rule "players.list" if he communicates his intent to join the game to all players listed in the rule. A player's name and Email address shall be removed from rule "players.list" if he communicates his intent to leave the game to all players listed in the rule.
Proposal hirsch.2 (Thomas)
Proposed 9 June 2000
Adopted on 10 June 2000
I propose to create the following rule:
_rules.spelling__________________________
If a spelling error is discovered in the current ruleset, it may be corrected if the correction does not change the proposals meaning and targets. The amendment shall be reported to all players.
Proposal hirsch.3 (Thomas)
Proposed 9 June 2000
Adopted on 10 June 2000
I propose to change the title of rule "proposals.voting.abstention.passive" into "proposals.voting.passive.abstention".
I propose to create the following rule:
_proposals.voting.passive.support________
The creator of a proposal automagically votes SUPPORT for his own proposals, unless he specifies another vote.
Proposal rg.2 (RG)
Proposed 9 June 2000
Defeated on 10 June 2000
proposals.debate
Pending proposals may be subject to debate amongst the players of the game and could result in alternate versions of the original proposal being voted upon.
Proposal rg.3 (RG)
Proposed 9 June 2000
Defeated on 10 June 2000
proposals.withdrawal
Pending proposals may be withdrawn by the proposer and such withdrawal shall be communicated to all the players.
Proposal rg.4 (RG)
Proposed 9 June 2000
Defeated on 10 June 2000
An Alternate version of Hirsch.4 (sic)
proposals.voting.passive.support
The creator of a proposal automagically votes SUPPORT for his own
proposals, unless the player explicitly chooses to ABSTAIN.
**I would like to prevent a proposer from voting AGAINST**
Proposal marsh.8 (The Governor)
Proposed 14 June 2000
Adopted 20 June 2000
Amend rule "rules.numbers" to read, in full:
rules.numbers_________
(a) Each rule shall have a unique identifier, which may be referred to as the rule number or rule title. The identifier may consist of one or more words separated by dots (periods). A word may consist of one or more upper- or lower-case roman letters or arabic digits.
(b) Rule numbers shall have a hierarchy. The word appearing before the first dot shall describe the rule number's first level. The word appearing before the second dot shall describe the rule number's second level, and so on. For purposes of this subsection the final word in the rule number shall be considered to be followed by a dot.
(c) In any official rule set, all rules whose rule number has the same word in its first level shall be grouped together. In any such grouping, all rules whose rule number has the same word in its second level shall be grouped together, and so on.
Proposal marsh.9 (The Governor)
Proposed 15 June 2000
Defeated 20 June 2000
Create a new rule, entitled
justice.chief.selection________
Each instance of noon on Sunday, Greenwich Mean Time, a new player shall become Chief Justice. The Chief Justice shall have been a player for a minimum of two weeks. Within this restriction, the player chosen shall be the player for whom the longest time has elapsed since he hbas been Chief Justice. A player who has never been Chief Justice shall always be chosen if he is not otherwise restricted. If, through action of this rule, two players appear equally qualified to be chosen Chief Justice, the qualified player whose Email domain is first alphabetically shall be Chief Justice.
Proposal marsh.10 (The Governor)
Proposed 15 June 2000
Adopted 20 June 2000
(1) Create a new rule, entitled
justice.callfor_________
When a dispute arises as to the interpretation of the rules, or the correctness or legality of any action, finding, or determination within the context of this game is in question, a player may submit a Call For Justice to the Chief Justice. Such a problem shall, as nearly as possible, describe the question to be decided by the Chief Justice.
(2) Create a new rule, entitled
justice.callfor.limitations_________
The Chief Justice may not submit a Call For Justice.
(3) Create a new rule, entitled
justice.callfor.numbers_________
Immediately upon receipt of a Call For Justice, the Chief Justice shall assign it a unique identifier. This identifier shall consist of two words separated by a dot (period). The first word shall be unique to any particular Chief Justice, and shall be the same on all Calls For Justice made to that Justice. Both words shall consist only of one or more lower- or upper-case roman letters, or arabic digits. The identifier so assigned may be referred to as a "Call For Justice Number", a "CFJ Number", or a "CFJ#".
(4) Create a new rule, entitled
justice.callfor.procedure________
Immediately upon receipt of a Call For Justice, the Chief Justice shall publish it to all players together with the identifier assigned by rule "justice.callfor.numbers". Nothing in this rule shall prevent the Chief Justice from including his ruling in the same publication.
Proposal marsh.11 (The Governor)
Proposed 15 June 2000
Adopted 20 June 2000
Create a new rule, entitled
justice.rulings____________
Upon receipt of a Call For Justice, the Chief Justice shall issue a ruling by publishing it to all players. Such publication shall refer to the identifier assigned to the Call For Justice by rule "justice.callfor.numbers", and may, at the Chief Justice's option, include the Call For Justice itself.
Proposal marsh.12 (The Governor)
Proposed 15 June 2000
Adopted 20 June 2000
Create a new rule, entitled
justice.rulings.standards
All rulings shall be made in accordance to the rules. If the rules are silent, inconsistent, or unclear, the Chief Justice shall consider game custom and the spirit of the game before applying other standards.
Proposal marsh.13 (The Governor)
Proposed 15 June 2000
Adopted 20 June 2000
Create a new rule, entitled
justice.rulings.limitations_________
A ruling issued by a Chief Justice shall be limited in scope to answering the question posed by the Call For Justice. However, nothing in this rule shall prevent the Chief Justice from including with his ruling any comments or arguments supporting his ruling.
Proposal marsh.14 (The Governor)
Proposed 15 June 2000
Defeated 20 June 2000
Create a new rule, entitled
justice.rulings.recusal__________
The Chief Justice may issue a ruling of NO DECISION to any Call For Justice submitted to him. Such a ruling shall not prohibit any player from resubmitting a Call For Justice to the same or any other Chief Justice.
Proposal marsh.15 (The Governor)
Proposed 15 June 2000
Defeated 20 June 2000
Create a new rule, entitled
justice.rulings.passive.recusal_________
If no ruling has been issued by a Chief Justice before the second Chief Justice following him has been selected, he shall be considered to have issued a ruling of NO DECISION.
Proposal hirsch.4 (Thomas)
Proposed 16 June 2000
Adopted 20 June 2000
create:
_players.missing___________
Players may be declared as 'missing'. Missing players are marked in the players List as such and do not have to participate in the regular gameplay. For the purpose of rules which require an action of players, missing players are considered as non-players. A player may declare himself as no longer missing at any time.
amend the first sentence of players.listmaintenance to
"A player is declared 'missing' if he does not make any game-relevant action during 7 consecutive days."
Proposal hirsch.5 (Thomas)
Proposed on 18 June 2000
Adopted on 20 June 2000
Create the following rule:
_rules.steadiness_____________________________________________
Every rule is associated with a value named its steadiness, which must be a rational number between 0 and 1 included. Unless another value is specified, a rules steadiness shall be equal to 1.
Create the following rule:
_proposals.steadiness__________________________________________
Every proposal is associated with a value named its steadiness, which must be a rational number between 0 and 1 included. This value is the maximum of the following:
- the steadiness of all rules amended by the proposal.
- the steadiness of all rules repealed by the proposal.
- the future steadiness of all rules created by the proposal.
- other steadiness values defined by any element changed by the proposal.
- 0.5
Amend proposals.passage to read:
_proposals.passage____________________________________________
A proposal is adopted, if at least two players voted SUPPORT and the number of players voting SUPPORT divided by the number of players not voting ABSTAIN is greater than or equal to the proposal's steadiness.
The change proposed shall then be made, unless such change is forbidden by the rules.
proposal zagarna.3 (Zagarna II)
Proposed 20 June 2000
Defeated 23 June 2000
Steadiness: 1
Throughout the ruleset replace all instances of the words: "SUPPORT", "OPPOSE" and "ABSTAIN", with: "Support", "Oppose" and "Abstain" respectivley.
Proposal marsh.16 (The Governor)
Proposed 20 June 2000
Adopted 27 June 2000
Steadiness: 0.5
Create a new rule, entitled
justice.chief.selection________
Each instance of noon on Sunday, Greenwich Mean Time, a new player shall become Chief Justice. The Chief Justice shall have been a player for a minimum of two weeks. Within this restriction, the player chosen shall be the player for whom the longest time has elapsed since he has been Chief Justice. A player who has never been Chief Justice shall always be chosen if he is not otherwise restricted. If, through action of this rule, two players appear equally qualified to be chosen Chief Justice, the Chief Justice shall be the qualified player whose Email address is first alphabetically, sorting first upon Email domain, and second on Email name.
proposal marsh.17 (The Governor)
Proposed 20 June 2000
Defeated 27 June 2000
Steadiness: 1
Amend "proposals.passage" to read, in full,
A proposal is adopted, if at least two players voted SUPPORT and the number of players voting SUPPORT divided by the number of players not voting ABSTAIN is greater than or equal to the proposal's steadiness. The change proposed shall then be made, unless such change is forbidden by the rules. Any rules created or amended by the proposal shall have the steadiness value which was associated with the proposal.
Proposal marsh.19 (The Governor)
Proposed 21 June 2000
Adopted 27 June 2000
Steadiness: 0.75
(1) create a rule with steadiness 0.75:
rules.priority.first
If two or more rules conflict, the rule(s) with larger steadiness values shall have priority over the rule(s) with smaller steadiness values.
(2) create a rule with steadiness 0.5:
rules.priority.second
If two rules of equal steadiness conflict, or if a rule should conflict with itself, a player may Call For Justice on the question of which rule or part of a rule shall have priority. A legally made ruling of the Chief Justice under this rule, shall be binding upon the ruleset, and any official ruleset shall be annotated with the priority findings of the Chief Justice.
Proposal marsh.20 (The Governor)
Proposed 21 June 2000
Adopted 27 June 2000
Steadiness: 1
(1) Amend rule "proposals" to read in full:
A player may make a proposal under this rule by publishing it to all players. Such proposal shall include any combination of one or more of the following:
- A proposal to create one or more rules
- A proposal to amend one or more rules
- A proposal to repeal one or more rules
- A proposal to overturn one or more rulings of the Chief Justice
- A proposal to elect one or more players to one or more elected positions created by the rules
- A proposal to award one or more artefacts of the game to one or more players
- A proposal to create or destroy one or more artefacts of the game
(2) Grand rule "proposals" a steadiness of 0.75.
Proposal marsh.21 (The Governor)
Proposed 21 June 2000
Defeated 27 June 2000
Steadiness: 1
create a rule with steadiness 1:
proposals.legality
If a proposal contains elements which, if the proposal were adopted, would be contrary to the rules, the entire proposal shall be without force even if adopted.
Proposal marsh.22 (The Governor)
Proposed 21 June 2000
Adopted 27 June 2000
Steadiness: 1
(1) Retitle rule "winning.score"
as "Gnomes".
(2) Grant rule "Gnomes"
a steadiness of 0.5.
Proposal marsh.23 (The Governor)
Proposed 22 June 2000
Defeated 27 June 2000
Steadiness: 1
For all of the following rules which exist at the time of adoption of this proposal, set the steadiness of the rule to 0.51:
Proposal marsh.24 (The Governor)
Proposed 22 June 2000
Defeated 27 June 2000
Steadiness: 1
Append the following to rule "players.list":
The steadiness of this rule shall be 0 for purposes of priority. The steadiness of this rule shall be 1 for purposes of determining the steadiness of a proposal to amend or repeal it.
Proposal zagarna.4 (Zagarna II)
Proposed 22 June 2000
Withdrawn by author
Steadiness: 1
change the title of rule 'winning.score' to: 'GNomes'
Proposal zagarna.5 (Zagarna II)
Proposed 22 June 2000
Adopted 27 June 2000
Steadiness: 1
repeal rule 'proposals.removal'
(we could actually keep it as AGAINST is not defined in the
rules, but ABSTAIN unfortunatley is)
Proposal zagarna.6 (Zagarna II)
Proposed 22 June 2000
Defeated 27 June 2000
Steadiness: 1
append to rule 'proposals.voting.options':
Capitalization is ininfluent for the purposes of this rule.
Proposal marsh.25 (The Governor)
Proposed 22 June 2000
Defeated 27 June 2000
Steadiness: 0.751
(1) Create a rule with Steadiness 0.751:
rules.numbers.predecessor__________
If a rule is amended to have a new rule number, the rule before amendment shall be known as a predecessor rule to the rule after amendment. This definition shall have recursive application.
(2) Create a rule with Steadiness 0.751:
rules.numbers.successor__________
If a rule is amended to have a new rule number, the rule after amendment shall be known as a successor rule to the rule before amendment. This definition shall have recursive application.
(3) Create a rule with Steadiness 0.751:
rules.numbers.reference_______
If a rule or proposal refers to a rule not in the ruleset, the reference shall be to its successor rule, if any. This rule shall have recursive application.
Proposal hirsch.7 (Thomas)
Proposed 23 June 2000
Adopted 27 June 2000
Steadiness: 1
Amend proposals.passage to read in full:
A proposal is adopted, if enough players voted for the proposal, at least two players voted SUPPORT and the number of players voting SUPPORT divided by the number of players not voting ABSTAIN is greater than or equal to the proposal's steadiness. The change proposed shall then be made, unless such change is forbidden by the rules.
In the context of this rule, enough players have voted either if all players cast one vote or if the proposal may not be defeated even if all remaining players cast OPPOSE.
Proposal hirsch.9 (Thomas)
Proposed 23 June 2000
Adopted 27 June 2000
Steadiness: 1
Create
_proposals.failing___________________________________________
A proposal fails, if all players casted a vote on this proposal and it did not pass. A proposal also fails if even when all remaining votes to cast would be SUPPORT it will not pass.
Proposal jeff.1 (Jeff Weston)
Proposed 25 June 2000
Defeated 27 June 2000
Steadiness: 1
Ammend players.list to read in full:
Players List
the players of the game are:Thomas (thomas@hirsch.org)
Zagarna II (zagarna@yahoo.com)
The Governor (dmarsh@voyager.net)
RG (rgpal@tibcofinance.com)
Jeff Weston (jjweston@pop.net)
Proposal jeff.2 (Jeff Weston)
Proposed 25 June 2000
Adopted 27 June 2000
Steadiness: 0.50
Create a new rule proposals.conflicts with steadiness = 0.50 that reads:
No more than one active proposal is allowed to modify a particular rule. If a rule is proposed to be modified by any active proposal, no proposals may be made that modify that same rule until the first proposal either succeeds or fails.
This rule has no effect on any proposals that are already active when it is enacted.
Proposal jeff.3 (Jeff Weston)
Proposed 25 June 2000
Adopted 27 June 2000
Steadiness = 0.50
Create a new rule proposals.withdrawing with steadiness = 0.50 that reads:
Anytime before a proposal has succeeded or failed, the proposal author may elect to withdraw their proposal. This has the effect of causing the proposal to immediately fail, regardless of whatever votes it had already received.
Proposal marsh.26 (The Governor)
Proposed 26 June 2000
Defeated 27 June 2000
Steadiness: 1
If no rule numbered "proposals.legality" exists,
create it with the text below. If such a rule exists, amend
it to read, in full,
proposals.legality
If a proposal contains elements which are contrary to the rules, or would be contrary to the rules if the proposal were adopted, the entire proposal shall be without force even if adopted. If the player making such proposal owns any Gnomes, one of them dies of shame, and is destroyed.
Proposal marsh.27 (The Governor)
Proposed 26 June 2000
Adopted 27 June 2000
Steadiness = 1
(1) Create rule entitled "time.week" with Steadiness = 0.751:
A calendar week shall end at noon on Sunday, Greenwich Mean Time, and a new calendar week shall then begin.
(2) If a rule entitled "justice.chief.selection" exists, amend it to read, in full,
At the beginning of each calendar week, a new player shall become Chief Justice. The Chief Justice shall have been a player for a minimum of two weeks. Within this restriction, the player chosen shall be the player for whom the longest time has elapsed since he has been Chief Justice. A player who has never been Chief Justice shall always be chosen if he is not otherwise restricted. If, through action of this rule, two players appear equally qualified to be chosen Chief Justice, the Chief Justice shall be the qualified player whose Email address is first alphabetically, sorting first upon Email domain, and second on Email name.
Proposal marsh.28 (The Governor)
Proposed 26 June 2000
Adopted 27 June 2000
Steadiness = 0.51
(1) Create a rule entitled "Gnomes.Mines.depth" with Steadiness 0.51:
A Mine's depth may be measured in rope lengths. Upon creation, a Mine's depth is 0.
(2) Create a rule entitled "Gnomes.Mines.depth.extension" with Steadiness 0.51:
During one calendar week, five Gnomes may increase the depth of one Mine by one rope length if the Gnomes are not otherwise employed.
Proposal marsh.29 (The Governor)
Proposed 26 June 2000
Adopted 27 June 2000
Steadiness = 0.51
(1) Create a rule entitled "Gnomes.Mines.production" with Steadiness 0.51:
A Mine's production value is a number from the following set: { . . . 1/4, 1/3, 1/2, 1, 2, 3, 4 . . . }. Upon creation, a Mine's production value is 1.
(2) Create a rule entitled "Gnomes.Mines.production.increase" with Steadiness 0.51:
During one calendar week, one hundred Gnomes expending one hundred Ingots may increase the production value of a mine to the next higher value, if the Gnomes are not otherwise employed. Any Ingots so expended, are destroyed.
Proposal marsh.30 (The Governor)
Proposed 26 June 2000
Adopted 27 June 2000
Steadiness = 0.51
(1) Create a rule entitled "Gnomes.Ingots" with Steadiness 0.51:
An Ingot is a unit of a metal which is found only in Mines. At the time this rule is adopted, no Ingots shall exist.
(2) Create a rule entitled "Gnomes.Ingots.production" with Steadiness 0.51:
During one calendar week, ten Gnomes may produce a number of Ingots equivalent to the Mine's production value for each two rope lengths of depth of that Mine, if the Gnomes are not otherwise employed. Any fractional Ingots left after application of this rule are destroyed; the ore processing machines are remarkably inefficient. [Gnomes/10 * depth/2 * PValue = Ingots.]
proposal marsh.31 (The Governor)
Proposed 26 June 2000
Adopted 27 June 2000
Steadiness = 0.51
Create a rule entitled "Gnomes.accountinggnome" with Steadiness 0.51:
The Accounting Gnome shall maintain an accurate record of all Gnomes, Mines, and Ingots, their owners, how all Gnomes are currently being employed, and the production values and depths of all Mines. He shall make such record available to any player upon request.
Proposal marsh.32 (The Governor)
Proposed 26 June 2000
Adopted 27 June 2000
Steadiness = 0.51
Create a rule entitled "Gnomes.employment" with Steadiness 0.51:
A player may choose how to employ any or all of his Gnomes by notifying the Accounting Gnome of any change. The change shall occur at the beginning of the next calendar week.
Proposal
hirsch.10 (Thomas)
Proposed 26 June 2000
Adopted 28 June 2000
Steadiness: currently indeterminate
Amend Gnomes.mines (if existing) to read in full: [Archivist's note: Rule Gnomes.mines did not exist at this time.]
_ Gnomes.Mines _(0.6)_______________________________________________
Mines may be owned by players. Mines may not be traded by players. Every specific Mine has a name, chosen when that Mine is originally created.
Create:
_ Gnomes.Mines.creation _(0.5)______________________________________
If a player does not own a Mine, he may create one Mine in his possesion by specifying its name, as well as 10 GnHomes in its proximity, populated by 10 Gnomes.
Remove all Mines, Gnomes and GnHomes in GNomic.
Proposal
hirsch.11 (Thomas)
Proposed 26 June 2000
Defeated 28 June 2000
Steadiness: 0.65
Create:
_ Gnomes.Tasks _(0.65)______________________________________________
During each week, a player may order their Gnomes to perform Tasks by announcing this to the Accounting Gnome. One Gnome may only perform one Task at a time.
The duration D of a Task is measured in Gnomeweeks - one Gnome will be able to perform that Task in D weeks. N Gnomes may share one Task in order to decrease the effective duration: A Task will require D/N weeks to be accomplished.
Proposal
hirsch.12 (Thomas)
Proposed 26 June 2000
Adopted 28 June 2000
Steadiness: 0.6
Create:
_ Gnomes.GnHomes _(0.6)_____________________________________________
A GnHome is a place where a Gnome lives. GnHomes are situated in direct proximity to Mines and considered to belong to their Mines. Every Gnome in a mine will occupy a GnHome in the same mine. Only one Gnome may live in one GnHome.
Amend:
_ Gnomes (0.6) _____________________________________________________
Gnomes are beings. They live in GnHomes. A Gnome who has got no GnHome is going to Migrate.
Create:
_ Gnomes.GnHomes.creation _(0.5)____________________________________
Making a GnHome is a Task that requires two Gnomeweeks. This GnHome will belong to the Mine where the Gnomes belong to.
Proposal
hirsch.13 (Thomas)
Proposed 26 June 2000
Adopted 28 June 2000
Steadiness: 0.5
Create:
_ Gnomes.creation _(0.5)____________________________________________
Making a Gnome is a Task that requires four Gnomeweeks.
Proposal
hirsch.14 (Thomas)
Proposed 26 June 2000
Adopted 28 June 2000
Steadiness: 0.5
Create:
_ Gnomes.migration.immigration _(0.5)_______________________________
Every week, one Gnome is coming from the legendary World Beyond GNomic and Migrates._ Gnomes.migration.intragnomical _(0.5)______________________________
Every four weeks, one Gnome from each Mine having more than five Gnomes is going to Migrate.
Proposal
hirsch.15 (Thomas)
Proposed 26 June 2000
Defeated 28 June 2000
Steadiness: 0.6
Create:
_ Gnomes.migration _(0.6)_________________________________________
Migrating Gnomes move from their current Mine into the Mine with the best Living Condition where a GnHome is available. In case of equal Living Conditions, they will move to the mine where the most time has elapsed since the last immigration. If there are no free GnHomes, the Migrating Gnome will emigrate to the World Beyond and leave GNomic.
Proposal
hirsch.16 (Thomas)
Proposed 26 June 2000
Adopted 28 June 2000
Steadiness: 0.5
Create:
_ Gnomes.Mines.livingcondition _(0.5)_______________________________
Every Mine is associated with a value L called its Living Condition. L is calculated as follows: Take the number of free GnHomes in a mine.. Subtract the depth of the mine in rope lengths.
Proposal jeff.4
(Jeff Weston)
Proposed 26 June 2000
Adopted 28 June 2000
Steadiness: 1
Create a new rule rules.comments with steadiness = 1 that reads:
Rules can contain comments. A comment starts with the character '[' and ends with the character ']'. A comment in a rule is non-binding for gameplay purposes. Comments may be used by a Chief Justice when issuing rulings to settle rule disputes.
Proposal jeff.5 (Jeff Weston)
Proposed 27 June 2000
Adopted 28 June 2000
Steadiness: 0.50
Ammend rule proposals.withdrawing to read in full:
Anytime before a proposal has succeeded or failed, the proposal author may elect to withdraw their proposal. Such a withdrawal is made by communicating it to all the players. This has the effect of causing the proposal to immediately fail, regardless of whatever votes it had already received.
Proposal jeff.6 (Jeff Weston)
Proposed 27 June 2000
Adopted 28 June 2000
Steadiness: 1
Ammend rule proposals.voting.options to read in full:
A proposal vote shall be one of the following: SUPPORT, OPPOSE, or ABSTAIN. Capitilization of the vote choice does not matter for purposes of this rule.
Proposal marsh.33 (The
Governor)
Proposed 27 June 2000
Defeated 28 June 2000
Steadiness: 1
(1) Amend rule "proposals.steadiness" to read, in full,
Every proposal is associated with a value named its steadiness, which must be a rational number between 0 and 1 inclusive. This value is the maximum, of the minimum steadiness values of each action included in the proposal.
(2) Create (S=0.751):
proposals.steadiness.rules_________
A proposal to create, amend, or repeal a rule shall have as its minimum steadiness value, the steadiness value associated with the rule or proposed rule. If a proposal to create a rule does not specify a steadiness value for that rule, its steadiness shall be the default value for rules.
(3) Create (S=0.751):
proposals.steadiness.justice.overturning_____________
A proposal to overturn the ruling of a Chief Justice shall have a minimum steadiness value of 0.750.
(4) Create (S=0.751):
proposals.steadiness.elections______________
A proposal to elect a player to an office created by the rules shall have a minimum steadiness value of 0.50.
(5) Create (S=0.751):
proposals.steadiness.artefacts______________
A proposal to create, destroy, or award to a player any artefact of the game shall have a minimum steadiness value of 0.50.
(6) Create (S=0.751):
proposals.steadiness.other______________
A legal proposal which does not have a minimum steadiness value shall have a minimum steadiness value of 0.50.
Proposal jeff.8
(Jeff Weston)
Proposed 28 June 2000
Withdrawn 28 June 2000
Steadiness: 1
Ammend rules.spelling to read in full:
If a spelling or grammatical error is discovered in a rule in the current ruleset, the rule may be corrected if the correction does not change the rule's meaning and targets. The amendment shall be communicated to all players.
A player may object to a correction made in this fashion by communicating his or her objection to all players. If two or more players object to a correction, it is removed. That same correction cannot be made again via this process. [However, a proposal containing the correction can still be made.]
Proposal
jeff.12 (Jeff Weston)
Proposed 28 June 2000
Withdrawn 28 June 2000
Steadiness: 1
Ammend proposals.passage to keep its current steadiness and read in full:
If the steadiness of a proposal is 1 it is adopted if enough players have voted, no players voted OPPOSE, and at least two players voted SUPPORT. If the steadiness of a proposal is less than 1, it is adopted if enough players have voted, the proportion of SUPPORT votes to non-OBSTAIN votes is greater than its steadiness, and at least two players voted SUPPORT. The change proposed shall then be made, unless such a change is forbidden by the rules.
In the context of this rule, enough players have voted either if all players cast one vote or if the proposal may not be defeated even if all remaining players cast OPPOSE.
[Example: Enough players have voted on proposal foo.1, with steadiness equal to 0.50. Three players have voted SUPPORT. Two players have voted OPPOSE. Two players have voted ABSTAIN. The number of non-ABSTAIN votes is 5. The proportion of SUPPORT votes to non-ABSTAIN votes is 3 / 5, or 0.60. Since this number is greater than the proposal's steadiness, the proposal is adopted. Instead, if there were three OPPOSE votes, the proportion of SUPPORT votes to non-ABSTAIN votes would be 3 / 6, or 0.50. Since this number is not greater than the proposal's steadiness, the proposal would fail.]