Ruleset 62

From BlogNomic Wiki
Revision as of 05:31, 3 November 2014 by 75th Trombone (talk | contribs) (1 revision)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Core Rules

Ruleset and Gamestate

This is the Ruleset for BlogNomic; all Members of the Staff shall obey it. Section One consists of the "core rules" of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the glossary, which exists solely to clarify the remainder of the ruleset. Rules may be referred to by their type, entire number and name or type and name. (e.g. This Rule may be referred to as Rule 1.1 Ruleset and Gamestate or the Rule entitled “Ruleset and Gamestate").

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Admins may correct obvious spelling and typographical mistakes in the Ruleset at any time, including replacing Spivak pronouns with the singular "they". A typographical mistake is defined as “A mistake in printing, typesetting, or typing, especially one caused by striking an incorrect key on a keyboard.”

Members of the Staff

Anybody may apply to join BlogNomic (if he is not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post announcing his arrival. An Admin shall add his to the roster in the sidebar and the GNDT, at which moment he becomes a Member of the Staff.

A Member of the Staff may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Member of the Staff may only change his name as a result of a proposal approving the change.

Some Members of the Staff are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Members of the Staff who wish to become Admins shall sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

Some Members of the Staff are Idle, and shall be marked as such in the sidebar. For the purposes of the Ruleset, excluding Rules 1.1, 1.2 and 1.8, Idle Members of the Staff are not counted as Members of the Staff. Admins may render a Member of the Staff Idle if that Member of the Staff has asked to become Idle or if that Member of the Staff has not posted a entry or comment for more than 7 days. In the latter case, the Admin must announce the idling in a blog post. Admins may de-Idle a Member of the Staff at his request - the Member of the Staff's personal gamestate retains the values it had immediately prior to his going Idle. If one or more values would be undefined, it is set to the value new Members of the Staff receive, if such a value exists.

A single person may not control more than one Member of the Staff within BlogNomic. If anybody is suspected of controlling more than one Member of the Staff, then a Proposal may be made to remove any number of such Member of the Staff from the game, and to bar the perpetrator from rejoining.

If anybody is suspected of intentionally tampering with the game medium (which is to say, at this time, ExpressionEngine) in an attempt to subvert the ruleset/gamestate or alter the ruleset/gamestate in a way not proscribed by the rules, then a Proposal may be made to remove any such Member of the Staff from the game, and to bar the perpetrator from rejoining.

If anybody is suspected of intentionally spamming BlogNomic, then a Proposal may be made to remove any such Member of the Staff from the game, and to bar the perpetrator from rejoining.

Proposals

Any Member of the Staff may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the "Proposal" category that describes those changes (unless the Member of the Staff already has 2 Proposals pending, or has already made 3 Proposals that day).

Proposals can either be Pending, Enacted, or Failed. When a Proposal is first put forward, it is considered Pending.

Voting

Any Member of the Staff may cast his Vote on a Pending Proposal by making a comment on that entry using a voting icon of FOR, AGAINST or DEFERENTIAL.

If the Member of the Staff who made a Proposal has not cast a Vote on it, his Vote is counted as FOR. If a Member of the Staff uses more than one Voting Icon in comments on a Pending Proposal, his Vote is the last voting icon he uses. If a Member of the Staff leaves the game or goes Idle, his Vote is no longer valid. If a Member of the Staff votes against his own proposal, that vote may not be changed. This is referred to as a Self-Kill.

A vote of DEFERENTIAL is a vote of no opinion, or of faith in the decision of the Writer. The vote will count as the same as the Writer's vote. The Writer cannot cast a vote of DEFERENTIAL. If there is no Writer, a vote of DEFERENTIAL counts as an explicit vote of abstention.

If no Writer has voted on a proposal, a vote of DEFERENTIAL on that proposal does not count as a vote for the purposes of rule 1.5.

Enactment

The oldest pending Proposal may be enacted by any Admin (and the Ruleset and/or Gamestate updated to include the specified effects of that Proposal) if either of the following is true:-

  • It has a number of FOR votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been vetoed or self-killed.
  • It has been open for voting for at least 48 hours, it has more than 1 valid vote, more than half of its votes are FOR, and it has not been vetoed or self-killed.

The oldest pending Proposal may be failed by any Admin, if any of the following are true:-

  • It has enough AGAINST votes that it could not be Enacted without one of those votes being changed.
  • It has been open for voting for at least 48 hours and half or fewer of its votes are FOR.
  • It has been open for voting for at least 48 hours and has fewer than 2 valid votes.
  • The Member of the Staff who proposed it has voted AGAINST it.

Whenever an Admin marks a proposal as enacted or failed, he must also mark his name, and report the final tally of votes (or the fact that the proposal was self-killed or vetoed).

Proposals the Writer has voted to VETO are considered vetoed. Proposals the author has voted against are considered self-killed unless the Writer has voted VETO on them, or they have fulfilled one of the other requirements to fail a proposal before the author’s self-kill vote is placed.

When Writer votes to VETO a Proposal, any Admin may fail that Proposal from that moment on, even if it is not the oldest Pending proposal.

Calls for Judgment

If two or more Members of the Staff actively disagree as to the interpretation of the Ruleset, or if a Member of the Staff feels that an aspect of the game needs urgent attention, then any Member of the Staff may raise a Call for Judgment (abbreviated CfJ) by posting an entry in the “Call for Judgment” category. The post shall go on to describe the issue, and measures that shall be taken to resolve it.

All Members of the Staff may add votes of agreement or disagreement in comments to this entry, using appropriate voting icons (a Member of the Staff's later votes overriding their earlier ones). Unfailed CfJs continue until they reach a quorum of FOR votes, a quorum of AGAINST votes, or if there is no hiatus going on, until four days have passed, and if there is a hiatus going on until two days have passed. After this time, if more than half of the cast votes are in favour, the Gamestate and Ruleset shall be amended as was specified. Otherwise, the CfJ fails. A Failed CfJ has no further effect.

Any CfJ that has no effect on the ruleset or gamestate may be automatically failed by any admin.

Gamestate Tracking

Proposals, Calls for Judgment, and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at http://blognomic.com. Any Member of the Staff may post to the blog at any time, but may only make official posts to the blog when the Ruleset allows it. Posts following the format specified by a rule are considered official posts.

If no Member of the Staff has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than five minutes and has no comments, the author may change the categories as they wish.

Voting and comments are accessible through the link at the bottom of every post.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at http://blognomic.com/gndt/generic.cgi?nomic=blog. Any Member of the Staff may update any Member of the Staff's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged - if a Member of the Staff feels that an alteration goes against the Rules (as they were at the time of the alteration), he may simply undo the effects of that alteration. If such an undoing is disputed, a Call for Judgment shall be raised.

Members of the Staff shall be assigned a password for the GNDT when they join the Nomic.

Dynasties

BlogNomic is divided into a number of Dynasties. Each Dynasty is headed by a single Member of the Staff, known as the Writer, and is named according to the number of Dynasties he has headed (eg. "The First Dynasty of Myke").

The Writer may vote to VETO any Proposal.

Metadynasties

Some Dynasties (called Metadynasties) have no Writer and are named according to the number of Metadynasties of Blognomic (eg. First Metadynasty). Metadynasties may only be started by a successful Proposal, CfJ, or as allowed by another rule.

When a Metadynasty begins, the previous Dynasty ends and all Dynastic rules are repealed. The theme (and appropriate substitution of keywords) may be chosen by any method deemed necessary.

Because there is no Writer, DEFERENTIAL votes are counted as explicit votes of abstention and no one may VETO a Proposal.

Victory and Ascension

If a Member of the Staff (other than the Writer) believes that he has achieved victory in the current Dynasty, he may make a post to the Blognomic weblog in the Declaration of Victory category, detailing this.

Upon doing so, the game immediately goes into Hiatus, if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Members of the Staff”, “Calls for Judgment”, “Gamestate Tracking” and “Victory and Ascension”.

Every Member of the Staff may respond to an active DoV saying whether or not he believes the poster has achieved victory in the current Dynasty (using the FOR and AGAINST icons).

The Declaration of Victory may be resolved after 24 hours, or after 12 hours if the Writer has voted on it. Upon resolution, if a Quorum of Members of the Staff have voted on the DoV and more than half of those votes were in favour, then the DoV passes - otherwise the DoV fails, and if no other DoVs are still pending, the Hiatus ends.

When a DoV passes, all other active DoVs are failed, and a new Dynasty begins with the Member of the Staff who made the DoV as its Writer. (That Member of the Staff may pass this role to another Member of the Staff at this point, if he wishes.) The Hiatus continues until the new Writer posts an Ascension Address to the BlogNomic weblog - this shall specify the Writer's chosen theme for the new Dynasty, and may optionally include a proclamation that any number of Dynastic Rules will be repealed, and that any keywords will be replaced with new theme-appropriate terms.

A DoV may not be started in the period between a passing DoV and that DoV’s Ascension Address. When a DoV is failed, if it has a number of AGAINST votes that exceed Quorum, the Member of the Staff who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

A Declaration of Victory may not also be any other type of Official Post unless the rules concerning that type of Official Post explicitly state otherwise.

Dynastic Rules

Theme

There exists a Dynastic Theme (also known as The Theme) which is a part of the Gamestate, but which may only be changed through Proposal or CfJ. The Theme is described by a single sentence which is only known to The Writer, and whose MD5 hash is “997e169d477054d6f23621e83e46e127”.

Synonyms

Members of the Staff may, for short, be referred to as Staff Members or simply Members.

Guessing

Each Staff member has a non-negative integer number of “Guesses” which are tracked by the GNDT. New Citizens start with 3 Guesses. As a daily action, a Staff member may “Take a Guess” by spending 1 Guess and making a Story Post whose subject starts with “[Guessing]”. The post shall contain in it’s body a text that will be compared to the Theme by the Writer.

If the text to compare has roughly the same words as the Theme, disregarding punctuation, capitalization and exact order of the words, the Writer shall comment that the Guess was correct and the Staff member who took the Guess achieves victory. If one of the words used in the Guess is a synonym of a word in the Theme, the two words shall be considered effectively the same.

In any other case, The Writer shall comment that the Guess is wrong and should include some reasons as to why it was wrong on the same comment. The writer shall also include in the comment the number of words in the guess that appear exactly in the theme (excluding punctuation).

If a guess is dissimilar to the theme in only one aspect and the staff member who made the guess still has at least one guess remaining, then the writer may post the words “follow up” and a new hint in his comment on the guess. If he does this, than no other staff member may post a guess until either 24 hours have passed or the player who made this guess has posted a new guess.

Guesses shall not be more than 20 words in length.

Writer Help

When the Writer votes on a proposal he may include with his vote the words Hot, Warm, Cool or Cold, to denote how closely to the theme the Writer feels the proposal is. The warmer the temperature, the closer to the theme the proposal is. If the Writer includes the word Hot on his last counted vote, and the proposal passes, the author of the proposal gains 1 Guess and the proposal is added to the Theme Hints page.

Cooperation

As a daily action, a Member of the Staff that has at least one guess may spend 5 Credits and 1 Guess to increase the Guesses of another Member by 1. This action can only be taken if both Members are currently on the same Station, and only if that Station is not Jump. As a weekly action, the Writer may increase his own Guesses by 1.

The Zuff Exception

The player called Zuff may not make guesses.

Hints

There exist special proposals called Hints. The Writer may create a Hint by adding the text “[Hint]” at the begining of the title of the proposal. Gamestate changes and Ruleset changes made by a Hint shall be considered to be related to the Theme.

There exists a wiki page called “Theme Hints” that keeps a record of all Hints that have been made. When a Hint is enacted, its contents shall be added to the Theme Hints wiki page under a heading for the date and time of the post.

Ingredients

There exists a wiki document titled “Ingredients” which may be only modified as the Ruleset permits, and that is formatted as a list, known itself as the Ingredient List. As a daily action, a Staff Member may add one kind of edible ingredient to the end of the Ingredient List, provided it is not currently already in the Ingredient List . The names given to Ingredients exist only for the purpose of explicit references to those Ingredients. If a rule refers to the name of an Ingredient in any other context, it is assumed not to be referencing that Ingredient.

At no time shall there exist more that 50 Ingredients on the Ingredient List. If there are at least 20 Ingredients on the Ingredient List, as a weekly action, any Member may “Clean the Fridge” and remove up to 3 Ingredients from the Ingredients List.

Specialties

At the time an Ingredient is added to the Ingredients List, the name of a valid Station may be added in parenthesis after the name of the Ingredient. The name of that Station must match the name of the Station where the Member who added the Ingredient is currently at. Members currently Translocating may not specify a Station in this manner. If a rule would allow a Member to remove an ingredient from the Ingredients List, that action may only be taken if that Member spends 1 Fuel. If the Ingredient’s Station or the Member’s Station is in Maintenance, the action cannot be taken at all.

The Table

Each Staff Member has a table of food, tracked on a wiki document called “The Table” with a section for each active Staff Member.

Rejection

If a Member doesn’t think that a Recipe on eir own table is good enough to be judged, e may Reject that Recipe by writing a bad review of it as a Story Post and removing it from eir Table. If a Member Rejects a Recipe in this manner, that Member cannot reject another one until 72 hours have elapsed. When a Recipe is Rejected, all Ingredients that make it up (according to the Recipes document) get removed from the Ingredients List.

Practice

If a Member has a Recipe on eir table, the Staff Member, thereby known as the Contestant, may start a Practice Session by creating a Story Post that starts with “[Taste]” and removing the Recipe from eir table. The Contestant is also expected to give a short description on the peculiarities of the prepared recipe. If the used recipe was the goal recipe, then the Contestant then obtains 1 Guess. Afterwards, if the goal recipe is cooked again, the Contestant that cooked it gains no Guesses.

The Bowl

Members have a subsection under their Table known as the Bowl, where they may keep ingredients that they have aquired but have not been used. Members cannot keep more than ten Ingredients in their Bowls. Any action that requires a Member to remove an Ingredient from the Ingredients List may instead be performed by removing that Ingredient from that Members Bowl. Members can only put or remove items from their own Bowl, and only as allowed by the rules. At any time, a Member may pay 1 Credit to select one ingredient from the Ingredients List and put a copy of it into that Member’s Bowl, but only if the Ingredient is not associated with a Station or if the Member’s Station is the same as the Ingredient’s Station.

Selling

At any time, a Member may place a Price Tag on a Recipe on eir Bowl. The Price Tag is a text in the form of “[X Credits]” that is appended to the end of a Recipe’s Name. X is known as the Price of that Recipe, and may be a number from 1 to 100. A Price Tag cannot be place on a Recipe that already has a Price Tag.

A Member may Purchase any Recipe with a Price Tag, by transfering an amount of their Credits to the Recipe’s owner, equal to the Price of that Recipe, moving that Recipe into their Table, and removing the Price Tag.

If a Member’s Recipe has had a Price Tag on it for at least 24 hours, that Member may remove the Price Tag from that Recipe.

Recipes

There exists a wiki document called “Recipes” which consists of an item followed by a Station in which it is in demand and one or more edible items such as below.

Recipe (Station) [Rating]: Ingredient #1, Ingredient #2, Ingredient #3

As a weekly action, the Writer may change the Station of as many recipes as he wishes.

Enhancements

Some Recipes may provide enhancements when eaten. An Enhancement is a non-italics text that follows a Recipe on the Recipes wiki document, and which can only be set, added and removed by the Writer, or through a successful Proposal or Call for Judgment. As a daily action, a non-Translocating Member may eat one of the Recipes on their table. Upon doing so, the Member shall follow the instructions laid on the Enhancement’s text. Enhancements are not allowed to change the ruleset, either directly or indirectly.

If a Recipe has no Enhancement, the Writer may add an Enhancement to it at any time.

Cooking

As a daily action, if every ingredient for a given recipe appears on a Member’s Bowl at least as many times at it does in a recipe, that Staff Member may remove one occurrence of each ingredient from eir Bowl for each time it appears in the recipe and add the recipe to his section of the table. (The recipe is not removed from the recipe document).

Writing Recipes

As a daily action, the Writer may add a new Recipe to the Recipes wiki document. Each Recipe must have at least three ingredients and a description. This new recipe is added at the end of the document, and as long as there is no other recipe after it, it is known as the Goal Recipe.

When a new Recipe is created, the Writer shall add 1DICE10 Credits to the Members who created any of the Ingredients that are part of that Recipe. This shall apply only for items that existed prior to the creation of the Recipe. The Writer may also, within a period of 24 hours modify (this includes adding or removing) the value of the Station which is associated to that Ingredient if it appears on the Ingredients List.

Judgement

If a “[Taste]” Story Post or a review of a Rejected Recipe includes a Rating from 1 to 5 Stars and that Recipe does not already have a Rating, that Recipe shall be given that Rating. This is known as Judging a Recipe.

Cosmology

Not all Staff members have originated in our home planet. In fact, many of them have come from distant locations. There is a GNDT column that shall track the current “Station” in which a Member of the Staff is residing. Because interstellar travel is too costly, the values of Station are limited to any one planet or moon located within the Solar System only, and to the special value “Jump”. If at any time, a Staff Member’s Station is set to an invalid value, that Staffer shall change it to its most recent valid value. A Member of the Staff currently in Jump is said to be Translocating. A new staffer starts at a random station determined by rolling DICEX (where X is the number of station found on the Solar Map) and setting eir station value to the station on the Solar Map matching the result.

Victory Lane

If the name of a Station that exists on the Solar Map appears on the Theme, Members of the Staff whose Station is not set to that Station may not achieve victory.

The Highway

There exists an super highway, known as Sol Road, that interconnects many cities from different planets and moons. Members that own a Vehicle may use this Road to, at any time, switch their Stations to any other Station adjacent to it on the Solar Map, without the need for Translocation. However, this requires the Member to Spend 1 unit of Fuel.

Also, at any time, the Writer may announce that one or more Gates are under maintenance by making a Story Post with “[Maintenance]” in the subject and listing one or more Station values, as well as a date of when the Maintenance will end. Members may not use the Sol Road to switch their Stations to values that are under Maintenance, until the Maintenance ends.

Solar Map

There exists a wiki document known as “Solar Map” which lists the possible routes between two stations. Two Stations are considered Adjacent in the Solar Map if one of them appears right before the other one. As a weekly action, a Member of the Staff may add a Station to the Solar Maps. A Station may be added even if it already appears in the Solar Map, as long as this doesn’t cause a Station to be Adjacent to itself.

When a user legally adds a planet to the Solar Map wiki page, that player may increase their credits by 5.

Credits

Each Member of the Staff owns a certain non-negative number of credits, which will be tracked in the GNDT. Each Member of the Staff starts with ten credits, which can be used to purchase various items.

Giving Credit

As a daily action, a Member of the Staff, hereby known as the Giver, may give any amount of credits to another Member of the Staff, hereby known as the Receiver. The giver does that by subtracting a positive amount of credits from his Credits and adding the same amount of credits to the Receiver’s credits. A Member of the Staff may not give away more credits than they own.

Vehicles

There exists a wiki page called “vehicles” which lists all the vehicles which can be purchased. Each Member of the Staff may own 0 or 1 vehicle(s). This is tracked in the GNDT. Vehicles may be added to the vehicles page by the writer, and the amount of fuel each vehicle can carry, their Speed and Endurance is described there. The writer also sets a price for each vehicle in the vehicle’s description. As a weekly action, a Member of the Staff may buy a vehicle by decreasing their credits by the price of the vehicle they wish to buy and changing their current vehicle (including -) to the new one in the GNDT. If this would cause a Member of the Staff’s credit to fall below 0, then it cannot be done. When a vehicle is bought, the Member of the Staff that bought the vehicle gains a number of fuel equal to the maximum amount of fuel the vehicle can carry.

Crash

As a daily action, a Member with a Vehicle (known as the Attacker) may spend X Fuel in an attempt to crash into some other Member (knows as the Target) who has the same Location as the Attacker. The value for X must be at least 2. The attacker shall then add their vehicle’s Speed to X, and roll DICEX. If the result is equal to or greater than the Endurance of the Target’s Vehicle (for this special case, if the Target has no Vehicle, their endurance is considered 3) the Target has Crashed: their Bowl and Table are emptied and 1 of their Guesses is transfered to the Attacker.

Turbo

As a daily action, a Member with a vehicle may start Turbo Mode by making a GNDT comment of “TURBO”. When a Member is in Turbo Mode, they may perform daily actions that require spending fuel as if they where not daily actions, and may instead perform them as long as they can pay their fuel cost. However, they cannot perform more than X such actions, where X is their Vehicle’s Speed, until Turbo Mode is deactivated. Turbo Mode lasts 2 hours, then deactivates itself.

Fuel

Each Member of the staff owns a non-negative amount of fuel, which is tracked in the GNDT. As a daily action, a Staff Member may purchase an amount of fuel equal to their Vehicle’s fuel rating by paying 10 Credits, then setting their Fuel in the GNDT to the fuel rating of their Vehicle. If this would cause a Member of the Staff’s credit to fall below 0, then it cannot be done.

Meals on Wheels

A Member’s Table is considered to be attached to his Vehicle, if he has one. Members with no Vehicle may not post a Declaration of Victory. The Member’s Vehicle and attached Table are considered to be at the same Station as the Member.

Vehicle Actions

Some Vehicles may provide extra benefits to their owner. A Vehicle Action is a non-italics text that follows a Vehicle on the Vehicles wiki document, and which can only be set, added and removed by the Writer, or through a successful Proposal or Call for Judgment. As a weekly action, a non-Translocating Member may activate the Vehicle Action on their Current Vehicle. Upon doing so, the Member shall follow the instructions laid on the Vehicle Action’s text. Vehicle Actions are not allowed to change the Ruleset, either directly or indirectly.

If a Vehicle has no Vehicle Action, the Writer may add a Vehicle Action to it at any time.

The Spaceport

As a daily action, a Member may pay 10 Credits to set their Station to Jump. This is known as Commencing Translocation.

Landing a Jump

A Translocating Staff Member may change his Station to any Station on the Solar Map that is not under Maintenance without spending any Fuel.

Raffle

As a daily action, a Member may spend 3 Credits and roll 1DICE50. Then, that member shall add the ingredient whose number in the Ingredients List matches the result from the roll to their bowl. If the added ingredient appears in a Recipe, that Member may perform this action again in the same day. If there is no ingredient with the number that was rolled, then the Member who rolled gets 1 credit.

Benefits

Whenever a Proposal creates at least one new Vehicle or Recipe upon enactment, the author of that Proposal may, within 24 hours of the passing of said Proposal, increase their own Credits by 1DICE10. Whenever a Member adds a Station to the Solar Map, that Member shall add 1DICE10 to their Credits.

Events

As long as there are no Ongoing Events, the Writer may create a new Event by making a story post whose subject starts with “[Event]”. The text of the post must contain an Itinerary and a Menu. An Itinerary is a list of Stations that appear on the Solar Map, and a Menu is a list of Recipes that appear on the Recipes document. When an Event is created, it is considered to be Ongoing.

A Member who is not already Participating on that Event may get Signed Up for it by paying 5 Credits and owning a Vehicle, and thus become Participants on that Event. Members who Participate in an Event have an additional section on their Table called the Trace. Whenever a Participant changes location, they shall add the name of the new Station to their Trace. When another Event is created, the Traces for all previous Participants are deleted.

At any time that a Participants meets every one of the Victory Conditions, that Participant becomes the First Place. Only the first Participant that meets all the Victory Conditions can be the First Place. The Victory Conditions are:

  • The Participant’s Trace must list the Stations for the Itinerary exactly once. (If other Stations appear on the Trace, it doesn’t matter)
  • The Participant’s Table must contain one of each of the Recipes on the Menu. (If other Recipes appear on the Table, it doesn’t matter)
  • The Participant must have not crashed more than 3 times since becoming a Participant for this Event.

When there is a First Place on an Event, the Event is no longer ongoing and the First Place obtains 3 Guesses, 150 Credits and may set their Location to any valid value once within the next 48 hours.

Lies

There is no Recipe for Cake.

Glossary

This is always at the end of the Ruleset. Its only effect can be to clarify ambiguity.

  • It is noted that where a Proposal would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their writer a banana when enacted would not earn a banana for its own writer, when enacted).
  • Rules which trigger upon the Enactment or Failure of a Proposal are the responsibility of the Admin who Enacts or Fails it.
  • Appropriate Icons: For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a vote of DEFERENTIAL, and an Imperial Seal (currently http://blognomic.com/images/vote/seal.gif) shall represent the Imperial Veto.
  • The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.
  • "Posts" and "comments" refer only to those made to the BlogNomic weblog at blognomic.com
  • A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "Bananas are Blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)
  • Unless otherwise specified, game variables defined to hold numeric values can hold only non-negative integers, and any action that would set those values below zero instead sets them to zero. Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
  • Unless otherwise specified: When "X" is a number, to spend X of a numeric value "V" means to subtract X from V (i.e. replace V with V-X); no action may be taken which requires spending X of a numeric value when the subtraction would result in a number which is illegal as a replacement for that value (e.g. if the value represents a variable which is restricted to non-negative integers, but the subtraction comes up negative).
  • Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.
  • Gamestate is defined as any information which the Ruleset regulates the alteration of, such as Characters’ names.
  • All integers, unless stated otherwise by a rule, are in base ten.
  • If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.

Typographic Conventions

  • Italicized text, also known as Flavor Text, is not considered part of any form of gamestate and may be used to clarify proposals or rules with examples, notes, and flavor text. For example, this italicized text provides an example of the use of italicized text.

Timespans

  • References to "a day" (as an entity rather than a duration, eg. "Sunday") refer to that day in the timezone of the BlogNomic blog, which is considered to be GMT for all purposes.
  • References to a "week" refer to the period of time between the start of a Monday and the end of the following Sunday.
  • All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
  • If a game action is a Daily Action, each Member of the Staff able to perform it may take that action once per day, but not more than once every six hours.
  • If a game action is a Weekly Action, each Member of the Staff able to perform it may take that action once per week, but not more than once every twenty-four hours.
  • Calendar Dates shall be represented in dd/mm/yy (day/month/year) format.
  • For the purpose of all rules, time in Blognomic is in GMT.

Keywords

  • Quorum is equal to half the number of Members of the Staff, rounded down, plus one.
  • Writer
  • Member of the Staff

Dice

References to "YDICEX" refer to Y X-sided dice. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

IEEE

  • The IEEE auxiliary verbs used in Blognomic are:
    • Is required to: "shall";
    • Is recommended that: "should";
    • Is permitted to: "may";
    • Is able to: "can".
Retrieved from "https://wiki.blognomic.com/index.php?title=Ruleset_62&oldid=630"