User:CodeTriangle/Handwriting Nomic (disgusting typed draft)

From Infinite Nomic Wiki

Time[edit | edit source]

All times mentioned in this ruleset are in UTC. Days begin at 00:00 UTC. Weeks begin on Monday.

Each week is divided into two phases, containing the following days:

  • Monday, Tuesday, and Wednesday
  • Thursday, Friday, Saturday, and Sunday

Phases are identified by successive Roman Numerals; the first Phase of the cycle is Phase I.

Sheets[edit | edit source]

A sheet is an image of a writing surface, or portion thereof, which may have inscriptions. Everything on the surface must be hand-drawn or handwritten (perhaps with technological assistance) except for reasonable additions that do not reduce the handmade character. Players should ensure that they are capable of creating and uploading all types of sheets.

The header of a sheet (if any) is a section of text on it, set apart from the sheet's main content.

A stack is an ordered set of sheets.

Cards[edit | edit source]

A card is a type of sheet. Cards should have an aspect ratio approximately equal to 4:3 and should only contain enough detail that they can be reproduced relatively easily on an index card.

A deck is an ordered set of cards.

Rules[edit | edit source]

A rule is a card which governs the state of the game. Rules are in effect continuously. When a player joins the game, they agree to abide by the rules.

A rule's header contains the word "Rule:" followed by the title of the rule, which is used to reference it.

Rules should be kept short to aid in rewriting.

Subrules[edit | edit source]

A subrule is a rule which claims another rule as its parent. The subrule is not part of the parent; instead this relationship is to be used for organizational purposes.

A rule that is not a subrule is a top-level rule

The path of a subrule is [path of parent] -> [title of subrule]. The path of a top-level rule is its title.

Change Cards[edit | edit source]

A change card is a card that describes a change to the gamestate. Types of change cards are defined in subrules of this rule.

Rule Change Cards[edit | edit source]

A rule change card modifies an existing rule in any way other than deleting it, or adds a new rule. It takes the form of a rule card. When applied, if there is a rule with the name described in the image, then that rule is replaced with the rule change card; otherwise that rule is added to the ruleset.

Arbitrary Change Cards[edit | edit source]

An arbitrary change card describes one or more gamestate modifications that do not meet the criteria for any other change card type. When applied, its effects are put into place.

Proposals[edit | edit source]

A proposal is a nonempty deck of change cards duly submitted as a proposal. When a proposal takes effect, the changes described by each of its change cards is applied in sequence and instantaneously.

Players can create a proposal by linking to or attaching the sequence of images in #proposals, optionally specifying a title and/or the proposal's class, which defaults to standard.

Voting[edit | edit source]

At the end of a proposal's voting period, a :+1: or :-1: emoji reaction from a player on the message containing the submission of the proposal represents a vote for or against that proposal, respectively.

Application[edit | edit source]

At the end of its voting period, a proposal takes effect if it is popular (as defined for its type), the message in which it was submitted has not been edited or deleted, and none of its cards have been edited or deleted. If more than one proposal would otherwise take effect simultaneously, they take effect in the order in which they were created.

Standard Proposals[edit | edit source]

The voting period for a standard proposal is the first phase after it was submitted. It is popular if it has more votes in favor than votes against.

A player cannot create a standard proposal if they have already submitted two standard proposals this week.

Urgent Proposals[edit | edit source]

The voting period for an urgent proposal starts at the time it was submitted and ends two days later. An urgent proposal is popular if there are no more than two votes against it.

Urgent proposals are only to be used to correct the game to its intended state and to maintain playability. Urgent proposals may only be submitted by reputable players.

Actions[edit | edit source]

When a rule defines an action that can be taken by posting to the server, it should specify a channel where the action can be taken.

If the rule defining an action does not specify a channel it can be performed in, or that channel does not exist, then it can be performed in #game-actions.

Card-Sending[edit | edit source]

When a rule says that an action can be performed by sending a card, then that action can be performed by attaching or linking to a card unambiguously showing that they intend to do that action.

Reputability[edit | edit source]

Players are considered reputable if they have continuously been a player for the previous seven days or if they have continuously been a player from a time that was within 3 days of the cycle starting.

Tracking[edit | edit source]

A character sheet for a player is a sheet which should act as the basic form of gamestate tracking. It must contain all the information required of it by this or other rules, otherwise it is not a character sheet. Its header shall contain the words "Character Sheet" and the player it was created for.

Self-Updating[edit | edit source]

When a player takes an action that changes one or more values tracked on their character sheet, they must attach or link to a new character sheet that reflects the gamestate as it would be if the changes in that message were effected. This is called "Self-Updating".

Update Notifications[edit | edit source]

When a player takes an action that changes one or more values tracked on another person's character sheet, they shall notify that person through Discord ping so that they may update their own character sheet.

Items[edit | edit source]

Items are entities described as such by the rules. Items are always owned by exactly one entity, and they cannot be owned by any entity that the rules do not allow to own that item. Unless another rule states otherwise, players may own items. When an item's owner cannot reasonably be determined using publicly available information, it is instead deleted.

A list of all items owned by a player is part of that player's character sheet.

Item Actions[edit | edit source]

For an entity to gain an item is for that item to be created in that entity's possession. To grant an entity an item is to create it in that entity's possession.

For an entity to lose an item is for that item to be destroyed from that entity's possession. To revoke an item from an entity is to destroy it from that entity's possession.

For entity A to take an asset from entity B is to transfer it from entity B to entity A.

Trade[edit | edit source]

A trade is an exchange or transfer of items between two entities, with each entity giving a specified finite set of items to the other. Reputable players may trade items with other reputable players. A trade between two players takes place when both players explicitly consent to the trade in #trades within 7 days of each other.

Judgement[edit | edit source]

There shall be a sole Judge, responsible for resolving rules disputes. An incumbent Judge can be removed with the assent of two players, but they should not be removed except for abuse of office. A person can cease being the Judge by publicly stating so.

Requests for Justice[edit | edit source]

Any person can initiate a request for justice by sending a sheet containing a question or statement in #request-for-justice. The proper response to an RFJ is a sheet containing the answer to that question if the RFJ was a question, or the truth value of the statement if if was a statement. Such a sheet should also include the judge's reasoning.

The Judge shall, as quickly as possible, issue such responses each request that is sent. 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.

Overturning[edit | edit source]

Within 4 days of a judge ruling being made, a public vote of confidence on that ruling can be initiated in #request-for-justice; the votes may be cast for a period of 2 days after initiation. A ruling is overturned if strictly more players vote in favor of overturning than affirming. An overturned ruling shall have no bearing on the interpretation of the rules or of the gamestate.

A ruling may be overturned in #request-for-justice by the Judge who made it within one week of being made. When a ruling is overturned in this manner, the Judge shall then issue a new ruling on the initial request, which shall be binding in the same manner as the original ruling.

Election[edit | edit source]

Any reputable player may become a candidate for the Judge by sending a card in the channel #judge-elections. If there are any Judge candidacies put forward during a week, the player whose message is both popular and has the most :+1: reactions becomes the Judge once that week ends. A Judge Candidacy message is popular if it has more votes in favour than votes against. Ties are broken in favour of the player with the earliest text message during that week.