|
Round
9
(ended)
Turn
9 - 16
2007-12-31
16:19 CST
Not logged in
Home
About
Calendar
Players
Public Forum
¤
Report Bug
¤
Rules
Game Activity
RFC
Proposals
GnP ¤
Judgments
Noncepts ¤
Random Number
Rune Spells
Virus ¤
Wiki ¤
History
Round 1
¤
Round 2
¤
Round 3
¤
Round 4
¤
Round 5
¤
Round 6
¤
Round 7
¤
Round 8
¤
Current
|
|
|
Show summary
Mutable
-
201.1
Turns and Times
|
Rule
|
|
Keywords
|
Rounds and Turns
|
|
Text
|
All times referenced in the ruleset shall be considered North American Central Time (GMT -6:00), observing U.S. daylight savings time.
Turns begin every week at 22:00 on Monday; this moment may be called a turn's beginning. Turns continue until 22:00 on Saturday. This moment is the turn's end. The moment at 10:00 on Thursday is the turn's middle.
Turns are designated as: [round]-[ordinal] The ordinal of the first turn of a round is 1. Each other turn has an ordinal which is 1 greater than that of the previous turn.
The period between the beginning and middle of a turn is the turn's first half. The period between the middle and the end is its latter half. The period between the end of one turn and the beginning of the next is called an interim. The period comprising a turn and the following interim is one game week.
|
( 9 - 0: Initial [201.1])
-
202.1
Rule-Change Proposals
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
Each active player may submit one rule-change proposal at the beginning of each turn unless a rule specifically allows more then one rule-change proposal for purposes of game play.
|
( 9 - 0: Initial [202.1])
-
203.1
Rule-Change Adoption
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
A proposal to enact, amend, or repeal a mutable rule is adopted if and only if it receives more votes in favor of it than against it.
|
( 9 - 0: Initial [203.1])
-
204.1
Quorum Required
|
Rule
|
|
Keywords
|
Noncept
Proposals
Referenda
|
|
Text
|
If any proposal or referendum is voted on by fewer than half of the active players, that proposal or referendum neither passes nor fails, but is placed up for vote the next turn. Proposals and referenda rolled forward in this manner do not count as new submissions.
This rule takes precedence over any rule that explicitly governs rule-change adoption or the passage of referenda.
|
( 9 - 0: Initial [204.1])
-
205.1
Passage Happens
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
An adopted rule-change takes full effect at the moment of the completion of the vote that adopted it; that is, at the end of the turn in which it is submitted for vote.
If more than one adopted rule-change affects the same existing rule, the one that received the most favorable votes takes precedence and the others are ignored. In the case of a tie on favorable votes, the proposal submitted first takes precedence.
|
( 9 - 0: Initial [205.1])
-
206.1
Explicit Precedence
|
Rule
|
|
Keywords
|
Precedence
|
|
Text
|
If two or more mutable rules conflict with one another, or if two or more immutable rules conflict with one another, then the rule with the lowest ordinal number takes precedence.
If at least one of the rules in conflict explicitly says of itself that it defers to another rule (or type of rule) or takes precedence over another rule (or type of rule), then such provisions shall supersede the numerical method for determining precedence.
If two or more rules claim to take precedence over one another or to defer to one another, then claims that name specific rules by number shall supercede those that name general types of rules. In case of conflicting precedence claims that operate by the same method, the default numerical method of determining precedence shall apply.
|
( 9 - 0: Initial [206.1])
-
207.1
Requests for Judgment
|
Rule
|
|
Keywords
|
Judgements
|
|
Text
|
The Judicial Review Period shall consist of the present game week and the previous game week.
If there is disagreement among the players about the legality of a move made within the Judicial Review Period or the interpretation or application of a rule within the Judicial Review Period, then an active player may seek a Ruling by submitting a Request for Judgment (RFJ) to the administrator, who shall assign it a case number. The submitting player shall be considered the Petitioner for the RFJ. The RFJ shall take the form of a statement to be judged TRUE or FALSE. The Petitioner should also assign a title to the case, and may optionally include arguments regarding the RFJ statement. Disagreement, for the purposes of this rule, may be created by the insistence of any player.
When an RFJ is invoked, it is a duty of the administrator to, as soon as possible, select a Judge as described in the rules and publish the RFJ, along with the identity of the Judge. The Ruling on the RFJ, including comments by the Judge, shall guide game play in regard to the issue addressed by the RFJ. If two or more rulings conflict on an issue, the latest Ruling shall take precedence. The Ruling shall only guide game play during or after the Judicial Review Period that was in effect when the RFJ was first submitted; the game state in turns prior to that Judicial Review Period shall stand as originally reported (after taking into account the effects of any prior RFJs).
|
( 9 - 0: Initial [207.1])
-
208.1
The Judicial Pool
|
Rule
|
|
Keywords
|
Judgements
|
|
Text
|
Any active player may or may not be in the Judicial Pool. An active player may enter or leave the Judicial Pool at any time by contacting the Administrator or their designee. A player who is in the Judicial Pool is removed from it if they cease to be an active player, fail to vote on at least one Proposal during any turn in which Proposals were up for vote, or are selected as a Judge. When a Judge returns a Judgment, they are returned to the Judicial pool if not already there. When a player first becomes active, they are not in the Judicial Pool.
When a Judge is required, the administrator shall randomly select a Judge from those players in the Judicial Pool, except the Petitioner and any player mentioned in the RFJ. If the Judicial Pool is empty (or contains only players disallowed by the preceding sentence), the administrator shall serve as Judge.
Judges appointed to cases in which they have a greater vested interest than other players should recuse themselves, but it is left to each player to determine their own conflicts of interest.
|
( 9 - 0: Initial [208.1])
-
209.2
Rendering Judgment
|
Rule
|
|
Keywords
|
Judgements
|
|
Text
|
When a player has been chosen as a Judge, they may recuse themselves by notifying the Administrator within 48 hours of notification of the Judge appointment. Upon receiving such notification, the Administrator shall select a new Judge, and the previous Judge shall be returned to the Judicial Pool.
If a Judge fails to deliver a Ruling within 7 days of his appointment, he shall be penalized 15 points, and a new Judge shall be selected. In this situation, the previous Judge shall not be returned to the Judicial Pool.
A legal Ruling is either TRUE or FALSE and may be accompanied by reasons and arguments. When determining a Ruling, the Judge should consider the rules in effect at the time of the disputed game action.
|
( 9 - 0: Initial [209.1]) ( 9 - 10: Amend [209.2] by Looney)
-
210.1
Appeals
|
Rule
|
|
Keywords
|
Judgements
Noncept
Referenda
|
|
Text
|
If a player is not satisfied with the result of an RFJ, he may submit an appeal as a referendum. The appeal shall consist of a new ruling of TRUE or FALSE, along with new reasonings and arguments. An appeal submitted on a particular RFJ shall be voted upon during the turn immediately following its submission (if more than one appeal is submitted on the same case in one turn, only the first submitted shall be voted upon.) If two-thirds of the players voting on the appeal support it, the appeal and its reasonings and arguments shall replace the original ruling in its entirety.
During the period from the submission of an appeal to the end of the turn in which players vote on that appeal, no other appeals may be submitted on the same RFJ. After this, and regardless of the result of any previous appeal, new appeals may be submitted as per the preceding paragraph.
|
( 9 - 0: Initial [210.1])
-
211.2
Credit to the Devious Ones
|
Rule
|
|
Keywords
|
Judgements
Victory
|
|
Text
|
If a player believes that the rules are such that further play is impossible, or that the legality of a move cannot be determined with finality, or that a move appears equally legal and illegal, then that player may submit an RFJ such that the statement to be judged explicitly specifies that there is a paradox. If such an RFJ is ruled true, the following shall occur:
If the ruling was submitted during a turn, the round will end at the end of the following turn unless the ruling is changed by appeal during that turn.
If the ruling was submitted during interim, the round will end at the end of the turn after that which immediately follows the interim unless the ruling is changed by appeal before that time.
If the round ends in the manner described, the following players are all winners: the player(s) who created the paradoxical situation by actions other than voting and the player who submitted the RFJ describing that situation.
|
( 9 - 0: Initial [211.1]) ( 9 - 2: Amend [211.2] by Looney)
-
212.1
Time Drops
|
Rule
|
|
Keywords
|
|
|
Text
|
A Time Drop is a means for automatically collecting and revealing information that is to remain secret for a time, after which it is to be made public. All the information collected in one Time Drop must become public at the same time.
A Time Drop should be able to:
1. Accept "deposits" of secret information from any player or a subset of the players. 2. Store that information reliably. 3. Automatically reveal all the deposits made to it to the public forum once its contents are no longer secret.
The Administrator is not necessarily expected to provide a Time Drop implementation, but if he does so, he is expected to inform the players that he has done so. If a rule depends on a Time Drop implementation, but none is available, then that rule is not in effect.
|
( 9 - 0: Initial [212.1])
-
213.1
Smith//Minmax
|
Rule
|
|
Keywords
|
|
|
Text
|
There exists a voting system called Smith//Minmax. In Smith//Minmax, each player ranks all of the alternatives in a nonstrict ordering. That is, multiple alternatives may be given the same ranking. If the implementation provides for leaving alternatives unranked, unranked alternatives are considered to be ranked equal to each other and lower than all explicitly ranked candidates. Whether one candidate beats another is determined by comparing the rankings of those candidates in each ballot submitted; if A is ranked higher than B, then this counts as a vote for A beating B and against B beating A.
Define the Smith set to be the smallest non-empty set of candidates in a particular election who, when paired off in pairwise elections, can beat all other candidates outside the set. Eliminate all candidates not in the Smith set.
Define the loss-measure of a candidate to be the greatest margin by which that candidate is beaten by another candidate (in the Smith set). If the candidate is not beaten by any other candidate, its score is 0. The candidate with the lowest loss-measure wins. If more than one candidate is tied for lowest loss-measure, a random one of those candidates wins.
|
( 9 - 0: Initial [213.1])
-
215.1
Player Status Changes
|
Rule
|
|
Keywords
|
Players
Referenda
|
|
Text
|
A player is an individual who is an active participant in Nomicron. An individual retains status as a player except under the following conditions:
1. If that player requests a change to observer status, that request shall be granted at the end of the game week in which the request is submitted.
2. If that player fails to vote for three consecutive turns in which proposals were up for vote, they shall become an observer.
Observers are not players, but are comprised of former players and anyone who wants to officially register as an observer of Nomicron.
Anyone may request to become a player by sending the request to the public forum. They shall become a player at the beginning of the turn following the request. If a player objects to such a request, a referendum will be held on the following turn to determine if the player request will be granted. If more players vote in favor of the referendum than against it, player status is granted. Otherwise, the individual is denied player status.
|
( 9 - 0: Initial [215.1])
-
216.1
Straw Poll
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
The author of a draft proposal posted on the RFC may invoke a straw poll to determine what level of support the proposal has. The straw poll is announced to the public forum and remains active so long as the draft is on the RFC.
Each active player may indicate their vote in the straw poll by choosing an option: Yea, Nay, or Undecided. A player may change their vote in the poll at any time. The vote summary results of the straw poll are available to all players on the draft's RFC page, though not how individual players voted.
|
( 9 - 0: Initial [216.1])
-
217.1
Sponsorship
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
A player may designate one of their drafts as "available for sponsorship". This player shall be referred to as the Author of the proposal. The text of the draft becomes public (if not already) and no changes to it may be made until the start of the next turn.
Any other player may choose to submit a draft from the "available for sponsorship" pool as their rule-change proposal for the next turn. This player shall be referred to as the Sponsor of the proposal. A draft may only be sponsored by one player. Once sponsorship is given, the Sponsor is committed to submitting the draft. Those drafts made available for sponsorship lose that status at the beginning of the turn.
Any rewards received upon passage of a sponsored proposal shall be divided evenly between the Author and Sponsor of that proposal, with any remainder going to the Sponsor. Any penalties received upon failure of a sponsored proposal shall go entirely to the Author. This rule takes precedence over mutable rules that designate effects to occur upon passage or failure of a proposal.
|
( 9 - 0: Initial [217.1])
-
218.2
Game Maintenance
|
Rule
|
|
Keywords
|
|
|
Text
|
The administrator is responsible for publishing the rules, tallying votes on proposals, and maintaining a list of players and their scores. Other rules may specify administrator duties and the administrator may voluntarily take on other duties. If a rule has maintenance requirements that do not fall under administrator duties, the player who submitted the proposal is responsible for the maintenance. They may perform the maintenance themselves, develop an automated mechanism, or find another player to do so. If at any point a rule has nobody to maintain it, that rule is considered a "blue law", rendering its provisions invalid. Any player may volunteer to maintain a blue law, making the rule valid again.
A player who maintains one or more rules is known as an officer, including the administrator. An officer may choose a title for their role. Each officer earns a salary of 2 points per turn, no matter how many rules they maintain. If an officer fails to perform any of their duties for a turn before the end of the game week, they forfeit their salary for the turn. Enforcement of this penalty shall not be restricted by the Judicial Review Period. This rule takes precedence over Rule 207.
|
( 9 - 0: Initial [218.1]) ( 9 - 9: Amend [218.2] by Looney)
-
219.1
Keyword Maintenance
|
Rule
|
|
Keywords
|
|
|
Text
|
The rules may have keywords attached to them. Active players may create new keywords and edit any rule's keywords at any time.
|
( 9 - 0: Initial [219.1])
-
220.1
Referenda
|
Rule
|
|
Keywords
|
Noncept
Referenda
|
|
Text
|
Votes conducted for purposes other than rule-changes may be collectively referred to as referenda. Any active player may submit up to n referenda at the beginning of each turn, where n is the number of rules that authorize particular types of referendum. Referenda are voted on in the same manner as rule change proposals.
Referenda shall be assigned numbers in order of submission, beginning with 7001. Any entity created by a referendum shall be identified by that referendum's number.
|
( 9 - 0: Initial [220.1])
-
301.1
Unleashed Index
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
When a player votes on a rule change proposal, they may specify an integer between 0 and 10 that indicates the degree to which the rule change is unique and different than rules in past rounds of Nomicron. The proposal's "Unleashed Index" is an average of all submitted values, rounded to the nearest integer. The author earns points equivalent to the proposal's unleashed index if the proposal passes, or half that amount (rounded up) if the proposal fails.
|
( 9 - 1: Enact [301.1] by Jef)
-
302.1
Votes unleashed
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
If a player votes on all proposals in a turn that player shall receive 3 points. Explicitly abstaining counts as voting for the purpose of this rule.
|
( 9 - 1: Enact [302.1] by Silverius)
-
304.1
Abstinence Only Legislation
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
In any turn in which a player casts at least three explicit votes of "Abstain" on proposals, and in which the player explicitly abstains on all referenda or proposals except for one, the player shall have two votes on the referendum or proposal they did not abstain on. In no circumstance shall this rule allow any player to get more than one extra vote on any referendum or proposal in a single turn.
|
( 9 - 2: Enact [304.1] by demn_percy)
-
305.1
Point King and Whale Scum
|
Rule
|
|
Keywords
|
Noncept
Proposals
|
|
Text
|
The Point King is the player with the most points in the game. The Point King is entitled to one extra rule-change proposal per turn.
Likewise, the Whale Scum is the player with the fewest point total in the game. The Whale Scum is also entitled to one extra rule-change proposal.
Only one player may be Point King at any given time; if two or more players are tied for most points, nobody is Point King. However, if two or more players are tied for fewest points, then all of them are Whale Scum.
This rule takes precedence over mutable rules that govern the submission of rule-change proposals.
|
( 9 - 2: Enact [305.1] by Silverius)
-
306.4
Referendum-Based Hotness and Frostbite, because anything is better than nothing
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
There is an index number called Temperature.
At the Beginning of each Turn, the following changes are applied to the value of Temperature:
- Decrease Temperature by the number of open RFJs or Appeal Referenda.
- If the number of Proposals and Referenda for Vote this Turn is less than half the number of Active Players (rounded up), decrease Temperature by the number of Active Players.
- If the number of Proposals and Referenda for Vote this Turn is greater than half the number of Active Players (rounded down), increase Temperature by the number of Proposals.
Then check the value of Temperature for the following conditions:
- If Temperature exceeds a value of 212 at the Beginning of a Turn, all Players gain 10 Points at the End of the Turn.
- If Temperature exceeds a value of 246 at the Beginning of a Turn, all Players may submit one additional Proposal that Turn.
- If Temperature is greater than 451 or less than -459 at the Beginning of a Turn, the Round will end at the end of the following Turn, as long as the Temperature still satisfies the above condition. If this happens, there is no winner.
- If Temperature is less than 32 at the Beginning of a Turn, any players who submitted neither proposals nor referenda that Turn gain points equal to difference (Temperature - 32) (which is a negative number, so the players in question actually lose points).
During a Turn, an Active Player may secretly declare that they are changing the Temperature and choose whether to "turn up the heat" or "chill out man".
At the end of the Turn, each Player who has chosen to change the Temperature is deducted 3 points. This may result in a negative Score.
During the Interim, announce the majority choice and the margin by which it is a majority.
If the "turn up the heat" choice was in the majority, increase Temperature by the Nth triangular number where N is the margin of majority.
If the "chill out man" choice was in the majority, decrease Temperature by the Nth triangular number where N is the margin of majority.
|
( 9 - 2: Enact [306.1] by Ouroboros) ( 9 - 5: Amend [306.2] by Looney) ( 9 - 9: Amend [306.3] by Metaloop) ( 9 - 13: Amend [306.4] by Looney)
-
308.1
Prime Minister
|
Rule
|
|
Keywords
|
|
|
Text
|
Nomicron has a Prime Minister that is elected by the players. The Prime Minister's role is to provide leadership on legislative direction. The rules may define specific duties for the Prime Minister. The Prime Minister earns a salary of 2 points per turn.
An election for Prime Minister shall be called for when no Prime Minister currently exists, or when the current one has served for four turns since last being elected. An election cycle encompasses two turns--during the first turn after an election is called for, players may submit their name for consideration in the election and campaign for the position. During the second turn, players vote on declared candidates using the Smith//Minmax system. The winner of the election shall serve as Prime Minister until they are replaced or are no longer a player.
|
( 9 - 3: Enact [308.1] by Jef)
-
309.1
Noncepts
|
Rule
|
|
Keywords
|
Meta-Noncept
|
|
Text
|
If a mutable rule has been in effect for at least three turns, but has not been invoked or triggered in the last 10 turns (or since its enactment, whichever is more recent)--in other words, the rule's existence has had no effect on the Nomicron gamestate during this time period--then that rule shall be considered a Noncept.
If a player successfully invokes or triggers a Noncept rule, then that player shall receive a bonus of 10 points in addition to the effects specified by that rule (which, obviously, is no longer a Noncept).
|
( 9 - 3: Enact [309.1] by Looney)
-
310.1
Predictions
|
Rule
|
|
Keywords
|
Proposals
Referenda
|
|
Text
|
For any proposal or referendum a player may predict whether it will pass or fail. A player may also chose not to make a prediction. If a player predicts pass and the proposal or referendum passes or a player predicts fail and the proposal or referendum fails that player will gain 1 point. If a player predicts pass and the proposal or referendum fails or a player predicts fail and the proposal or referendum passes that player will lose 1 point.
Additionally players may set a bet between 0 and 20 points inclusive when making a prediction. After determining the outcome of the proposal or referendum (whether it passed or failed) the players who predicted wrong shall lose points equal to their bets and the players who predicted right shall gain points according to the following calculation.
Let G be the point gain of a player who predicted right. Let B be the bet of a player who predicted right. Let T_w be the total bets of the players who predicted right. Let T_l be the total bets of the players who predicted wrong. Let floor() be a function that discards the part of a number after the decimal point.
G = floor((B/T_w)*T_l)
|
( 9 - 3: Enact [310.1] by Silverius)
-
312.1
The Voting Machine
|
Rule
|
|
Keywords
|
Proposals
Referenda
|
|
Text
|
The Voting Machine is an entity that is an eligible voter on Proposals and Referenda.
As many times as desired during the week, a Player may pay a number of points to secretly submit the following information to the Voting Machine time drop:
* The number of a current proposal or referenda open for Voting
* Either FOR or AGAINST.
At the end of the week, just before voting closes, the Voting Machine votes on each current Proposal and Referenda as follows:
* If the total number of points spent on the Voting Machine time drop FOR that Proposal or Referenda is greater than the number of points AGAINST it, the Voting Machine votes FOR that proposal.
* If the total number of points spent on the Voting Machine time drop AGAINST that Proposal or Referenda is greater than the number of points FOR it, the Voting Machine votes AGAINST that proposal.
* If the total number of points spent on the Voting Machine time drop FOR the Proposal or Referenda is the same as the amount spent AGAINST it, or if no points were spent on that proposal or referenda, then the Voting Machine casts a random valid vote on that proposal or referenda.
|
( 9 - 4: Enact [312.1] by BobTHJ)
-
313.1
And They're Off!
|
Rule
|
|
Keywords
|
Noncept
Proposals
|
|
Text
|
For Turns 5 through 7, each Active Player may submit an additional rule-change Proposal, at a cost of 3 points.
|
( 9 - 4: Enact [313.1] by Ouroboros)
-
315.1
Multiple Authors
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
When submitting a Proposal, a Player may credit up to two other Players for the Proposal.
Should the Proposal pass, those Players so acknowledged shall gain 2 points each.
|
( 9 - 4: Enact [315.1] by Metaloop)
-
322.1
Apathy Destroys the Game
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
If no proposals are submitted for 10 consecutive turns, the round shall end immediately. If this happens, there shall be no winner, and a motion to end the game shall be automatically submitted at the beginning of Convention.
|
( 9 - 8: Enact [322.1] by Looney)
-
323.1
Governors and Population
|
Rule
|
|
Keywords
|
|
|
Text
|
Each Player is the Governor of a province, which are inhabited by 'people'. The maximum population a province can hold is equal to the number of houses (H) that province has. Population (P) and the number of houses (H) are natural numbers (zero is excluded, so minimum value of P and H is 1).
A Governor can build houses at a cost of 1 point per 2 houses in his/her province. A Governor can also destroy houses either in his/her own province or other provinces at a cost of 1 point per house. These actions can be performed during a turn and take effect at the end of the turn. If at any time, P exceeds H, P is set to H.
At the end of a turn, after taking into account the above effects, the population evolves as:
P = round( (2*H-P)*(P/H) )
round() rounds the argument to nearest integer. In case P = 0, it is set to 1.
For every province, the initial values are H = 100 and P = 20.
|
( 9 - 8: Enact [323.1] by Metaloop)
-
325.2
Virus
|
Rule
|
|
Keywords
|
Virus and Genes
|
|
Text
|
There is a virus. It has a gene sequence, which determines its properties. The length of the gene sequence is N = 7. The sequence consists of 0s and 1s only. Each player (agent) is located at one of the N locations numbered from 0 to N-1, say n. Each agent may modify the gene sequence as described below.
During a turn, an agent may submit an action to a Time Drop do one of the following: move left (that is n = n-1 mod N), move right (n = n+1 mod N) or toggle symbol at position n. At the end of the turn, actions in the Time Drop are announced, and the gene sequence is updated by the rule: Toggle symbol at position i if an odd number of agents have toggled at i otherwise leave it as it is, for all elements i of the set of integers from 0 to N-1.
The initial sequence is 1010101. The initial location of an agent (including new players) is determined randomly.
|
( 9 - 9: Enact [325.1] by Metaloop) ( 9 - 13: Amend [325.2] by Jef)
-
328.3
Virus Unleashed
|
Rule
|
|
Keywords
|
Virus and Genes
|
|
Blue Law
|
|
|
Text
|
The virus can infect the mutable rules passed during the round (Rules 301 and above). The gene sequence of the virus codes the rule it can infect. Once infected, a rule remains suspended (is inapplicable) for one game week. The dynamic variables, (ex: an entity such as temperature) defined and updated every week by the infected rule, are remembered and are not reinitialized when the rule becomes operational again. But they are not updated and and do not have any bearing on the game as long as the rule is infected.
At the beginning of a turn, after executing all the other rules that have to be executed at the beginning of that turn, read the gene sequence of the virus. Treat it as a binary number with the symbol at position 0 as the Most Significant Bit. Let this number be M. Let R be the number of the rule with the highest number. P = R - 300 (so that only mutable rules passed in this round are infected). r = 300 + (M mod P) + 1 is the number of the rule infected. If no rule exists with that number then no rule is infected.
The rule defining the virus and the gene sequence Rule 325 and this rule cannot be infected by the virus.
|
( 9 - 10: Enact [328.1] by Metaloop) ( 9 - 14: Amend [328.2] by Metaloop) ( 9 - 15: Amend [328.3] by Metaloop)
-
331.1
White Christmas
|
Rule
|
|
Keywords
|
Proposals
|
|
Text
|
If at 0:00 on December 25 (the beginning of the day), in the system timezone of Nomicron (CST), the temperature is 0 or less all players may submit an extra proposal for the next turn.
|
( 9 - 12: Enact [331.1] by Silverius)
-
333.1
Deciphering the Genetic Code
|
Rule
|
|
Keywords
|
Virus and Genes
|
|
Blue Law
|
|
|
Text
|
There is a string of characters known as the Genetic Code. Initially, it is empty. At the beginning of each turn, the ASCII character equivalent to the value of the gene sequence (read with position 0 representing the largest place value, and values descending from there) shall be appended to the end of the Genetic Code.
During the turn, players may submit comments to a time drop. These submissions should be interpetations of the meaning of the Genetic Code. Such meanings can be derived in any manner (acronyms? reading the string as words?).
During each turn, players shall vote on the previous turn's submissions by Smith//Minmax. Points shall be awarded for submissions as follows:
Let n be the number of active players during the turn when the submissions were made (NOT the voting turn). The first-place submission shall earn n points for its creator. The second-place submission shall earn n-1 points, and so on. Players who submitted nothing receive no points. Ties between two submissions shall be resolved randomly (as per Rule 213), but if more than two submissions are tied, the submittors shall receive the average of the points that each would have received if there was no tie, rounded to the nearest integer.
|
( 9 - 12: Enact [333.1] by Looney)
-
336.2
Rune Stacks
|
Rule
|
|
Keywords
|
Referenda
|
|
Text
|
Each player has three rune stacks, which are initially empty. Rune turns are at the beginning, middle and end of every turn. Rune turns consist of a manipulation step followed by an execution step.
During the manipulation step of a rune turn every player may add to one or two stacks a rune (doesn't need to be the same rune in the case of two stacks). Additions must be declared in advance and affect the rune turn which comes up next.
Stacks and sequences are notated as a sequence of runes with optional whitespace and comma's in between them. The last rune (the rightmost rune) is considered the top rune. So in ABC C is the top rune.
If a stack, read from the top (the rune which has been last added) contains an executable sequence of runes during the execution step those runes are removed from the stack and the effect of the associated rune spell is invoked. Note that a spell only matches if it's top rune is also the top rune of the stack (so given a stack ABCDE the sequence BCD doesn't match as D isn't the top rune, but CDE does match).
When a spell is invoked the player has to declare the arguments to it, if any, when declaring which runes to add (if no runes are added the arguments still have to be declared). If arguments are needed for the execution but have not been declared the runes involved will be removed but no effect will occur.
If multiple executable sequences can apply to a stack the longest of those sequences will execute.
Execution of sequences is serialized. First the player with the lowest amount of points executes it's sequences (if any) with stack 1 going before 2 and then 3. After that the player with the second lowest amount of points executes it's sequences, etc.
If multiple players have the same amount of points the player who's nickname precedes that of the others alphabetically goes first, then the player who's next alphabetically, etc.
Runes are 'A', 'B', 'C', 'D', 'E' and 'F' and 'G'. Additional runes may be defined by other rules.
Rune spells define executable rune sequences. Rune spells may be created, revoked and changed using referenda.
Rune spells consist of:
* A title.
* A list of at least 1 and at most 5 rune sequences which would trigger this spell. Every rune sequence must be unique in the rune book.
* A list of what parameters need to be given to invoke this spell.
* A description of it's effects.
* Optionally a commentary text (for example to be used for flavor text).
The rune book is a collection of all current rune spells.
|
( 9 - 13: Enact [336.1] by Silverius) ( 9 - 14: Amend [336.2] by Silverius)
-
337.1
Player of the Week
|
Rule
|
|
Keywords
|
|
|
Text
|
At the beginning of each turn, a Player of the Week shall be randomly selected from among all current Players (causing any previous Player of the Week to cease to be Player of the Week). Until the beginning of the next turn, all point gains and losses for the selected Player are doubled.
|
( 9 - 13: Enact [337.1] by BobTHJ)
|