Ruleset 64

From BlogNomic Wiki
Jump to navigation Jump to search

Core Rules

Ruleset and Gamestate

This is the Ruleset for BlogNomic; all Scripters 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.”

Scripters

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 Scripter.

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

Some Scripters are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Scripters who wish to become Admins may 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 Scripters 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 Scripters are not counted as Scripters. Admins may render a Scripter Idle if that Scripter has asked to become Idle or if that Scripter has not posted an 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 Scripter at his request - the Scripter'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 Scripters receive, if such a value exists.

A Scripter must abide by the rules of fair play in Glossary section 3.6.

Proposals

Any Scripter may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the "Proposal" category that describes those changes (unless the Scripter 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 Scripter 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 Scripter who made a Proposal has not cast a Vote on it, his Vote is counted as FOR. If a Scripter uses more than one Voting Icon in comments on a Pending Proposal, his Vote is the last voting icon he uses. If a Scripter leaves the game or goes Idle, his Vote is no longer valid. If a Scripter 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 Producer. The vote will count as the same as the Producer's vote. The Producer cannot cast a vote of DEFERENTIAL. If there is no Producer, a vote of DEFERENTIAL counts as an explicit vote of abstention.

If no Producer 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 Scripter 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 Producer has voted to VETO are considered vetoed. Proposals the author has voted against are considered self-killed unless the Producer 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 Producer 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 Scripters actively disagree as to the interpretation of the Ruleset, or if a Scripter feels that an aspect of the game needs urgent attention, then any Scripter 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 Scripters may add votes of agreement or disagreement in comments to this entry, using appropriate voting icons (a Scripter'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 Scripter 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 Scripter 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 Scripter may update any Scripter's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged - if a Scripter 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.

Scripters 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 Scripter, known as the Producer, and is named according to the number of Dynasties he has headed (eg. "The First Dynasty of Myke").

The Producer may vote to VETO any Proposal.

Victory and Ascension

If a Scripter (other than the Producer) 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 “Scripters”, “Calls for Judgment”, “Gamestate Tracking” and “Victory and Ascension”.

Every Scripter 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 Producer has voted on it. Upon resolution, if a Quorum of Scripters 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 Scripter who made the DoV as its Producer. (That Scripter may pass this role to another Scripter at this point, if he wishes.) The Hiatus continues until the new Producer posts an Ascension Address to the BlogNomic weblog - this shall specify the Producer'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 Scripter 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.

Fair Play

The following are BlogNomic’s rules of fair play. If any of the rules are found to have been broken, a proposal or CfJ may be made to remove the perpetrator from the game, and bar them from rejoining.

  • A single person should not control more than one Scripter within BlogNomic.
  • A Scripter should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
  • A Scripter should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
  • Instead of deleting content from a blog post which has at least one comment, the content should either be struck through with <strike> tags, or replaced with a link to a copy of the same content on the wiki.
  • A Scripter should not edit their own blog comments once posted, nor those of any other Scripter.
  • A Scripter should not edit the "Entry Date" field of a blog post.
  • A Scripter should not make or edit a post such that its title does not broadly match its URL title.
  • A Scripter should not make a DoV primarily to delay the game by putting it into Hiatus.

Dynastic Rules

Royalties

Each Scripter has a statistic called Royalties which is tracked in the GNDT. This represents the amount of money the Scripter is due to receive when the film is complete. A Scripter’s Royalties is a non-negative integer. New Scripters start with a Royalties value of 0.

Acts

The Producer may make a new Act by posting a Story Post with “[Act X]” in the title, replacing X with the numeral of the new Act (which is the numeral of the last Act to be created plus one, or 1 if there is no previous Act); the Story Post posted is the Drawing Board of the new Act. In the Drawing Board post the Producer shall give a summary of the start of the Act no longer than 15 words, for example ‘Protagonist in office block trying to find killer of wife’, and a Target Body Count (which is a non-negative integer). Acts are not Finished when they are created.

If a Scripter has not yet created a Scene for an Act that is not Finished, he or she may do so as a daily action, by rolling DICE5 in the GNDT to get their Scene’s Body Count, then posting a comment to the Drawing Board describing their Scene, and including the total of all the Act’s Scenes’ (excluding those that are Cut) Body Counts.

The description of a Scene requires a Title (text which cannot exceed five words), a Script (a text summary of the scene which cannot exceed 50 words), and the Scene’s Body Count. Scripters are encouraged to write a script that reflects the Body Count they have rolled. The Royalties statistic of a Scripter who creates a Scene increases by the Body Count of the Scene they create.

After 72 hours, the Producer may declare the Act to be Finished, by posting a comment to the Drawing Board containing the phrase ‘That’s enough’. Once the total of all the Act’s Scenes’ (excluding those that are Cut) Body Counts equals or exceeds the Target Body Count of the Act, any Scripter may declare the Act to be Finished, by posting a comment to the Drawing Board containing the phrase 'That's enough’. A wiki page shall then be created, called Act X (replacing X with the numeral of the Act), containing each Scene that is not Cut in the Act, in the order they were posted (the Title of a Scene being its Header, and its Description and Body Count being under that header).

Stunt Casting

A Scripter may choose to Stunt-Cast a Scene by rolling an extra DICE12024 in the same GNDT comment as their die roll for the Body Count.

The Actor at this list of American film actors whose number matches the result of this die roll is the Stunt-Cast Actor for this Scene, and their name should be mentioned in brackets after the role they are playing, in the Scene. (For example, “The getaway car runs down a street vendor (Christopher Walken) and speeds into the night.") A Scene may only have one Stunt-Cast Actor.

The Scripter should then find the Actor on IMDB by searching for that Actor’s name at http://www.imdb.com/search ("Cast / Crew Name Search”, using “Actors only” or “Actresses only” as appropriate) and taking the first result that exactly matches the name given on the list.

  • If the Actor is listed as alive, the Scripter should count the number of awards that the Actor has won or been nominated for, according to their IMDB page. The Scripter may add that number to the Body Count of the Scene (unless this would add more than ten, in which case the Scripter may only add ten).
  • If the Actor is listed as dead, then the Actor shall be listed in the Script as "(someone like [name])" (where [name] is the Actor's name), and the Scripter receives no Royalties for this scene.
  • If no such match exists, then the writing crew shrug and no bonus is awarded.

Climax Acts

Once there are 5 Finished Acts, when the producer creates an Act, he may add the keyword 'Climax' in the title, before "[Act X]" (replacing X with the numeral of the new Act as usual) Body Count for all the scenes (and thus the number of deaths in the script for those scenes) are doubled in that Act, as are Popularity gains and losses resulting from rule '2.5 Best in Show Votes' from that Act.

Punchlines

A Scripter may add a Punchline to a Scene by adding the text “[PUNCHLINE]” within the Script of that Scene. Then, the Scripter shall add a section called Punchline where they will write down the full text of the punchline. A Punchline can only be added to a Scene if the Body Count of that Scene is less than 4.

The Finale

Once there are 6 Finished Acts, when the Producer creates an Act, he may add the keyword 'Finale' in the title to make the new Act the Finale. Once the Finale has been created, no more Acts can be created.

The Finale is not like a normal Act. Scripters posting Scenes for the Finale should write a Scene that single-handedly finishes the movie.

The Finale differs from a normal Act in the following ways:

  • As scenes will not be compiled in chronological order when the Act is Finished, when writing a Scene a Scripter should write as if their Scene will be the only Scene in the Act. (This is because only the Scene that wins Best Finale Scene will be included in the production, as the ending of the movie.)
  • No Target Body Count is given by the Producer for a Finale. The Act Finishing condition based on Target Body Count does not apply.
  • Scenes have a Body Count of the Scene creation roll plus 10. (Note that a Scripter's Popularity is still added to this roll, as Rule 2.6 Popularity.)
  • The Finale's Scene's Scripts can exceed 50 words. They cannot exceed 100 words.
  • Continuity claims should not be made about Scenes contradicting previous scenes in the Finale, as there are no continuity errors possible as any posted Scene is an independent ending.
  • No wiki page is created when the Finale is Finished.

The Awkward Aftermath

When the Finale becomes Finished, Scripters may not vote how the rule Best in Show Votes would normally allow them to. Instead, a Story Post shall be created by the Producer called ‘The Awkward Aftermath’, to be known as the Vote Post; this will link to this rule’s text. When the Vote Post is created, the dynasty enters the Voting Stage.

Each Scripter has a statistic called ‘Vote’, tracked in the GNDT. Scripters start with no value for this statistic. While the dynasty is in the Voting Phase, as a daily action, a Scripter can change their Vote statistic to the name of any Scripter other than themselves who posted a Scene to the Finale that was not Cut.

48 hours after the Vote Post has been created, while the dynasty is in the Voting Stage, the Producer may declare in a comment to the Vote Post that the dynasty has entered the Bribery Stage. 72 hours after the Vote Post has been created, if the dynasty is still in the Voting Stage, any Scripter may declare in a comment to the Vote Post that the dynasty has entered the Bribery Stage. When the dynasty enters the Bribery Stage, it leaves the Voting Stage.

Each Scripter has a statistic called ‘Bribe Value’, tracked in the GNDT. Scripters start with a Bribe Value of 10 + their Popularity, rounded up. When the dynasty enters the Bribery Stage for the first time, each Scripter’s Popularity is set to their own Popularity rounded up, and each Scripter’s Bribe Value is (again) set to 10 + their Popularity. While the dynasty is in the Bribery Stage, a Scripter may Bribe another Scripter (the Recipient) by spending X Royalties, where X is at least the Recipient’s Bribe Value. They then change the Recipient’s Vote statistic to the name of any Scripter (who posted a Scene to the Finale that was not Cut) other than the Recipient, and increase the Recipient’s Bribe Value to the Royalties they spent to make the bribe, plus 1, plus their own Popularity statistic. (Scripters are considered to have 0 Popularity when making bribes if their Popularity is below 0.)

72 hours after the dynasty enters the most recent Bribery Stage, the Producer may declare in a comment to the Vote Post that the dynasty has left the Bribery Stage, and that Movie Completion has been achieved. 96 hours after the dynasty enters the Bribery Stage, if the dynasty is still in the Bribery Stage, any Scripter may declare in a comment to the Vote Post that the dynasty has left the Bribery Stage, and that Movie Completion has been achieved. Scripters are said to have voted for the Scripter named in their Vote statistic, if any. When Movie Completion is achieved, if there is not a tie, the Scripter with the most votes of this kind is titled the 'Finale Winner', and their Scene they created in the finale alone is placed on a wiki page titled “Final Act”; the other Scenes in the Finale are placed on a wiki page titled “Alternative Endings”. If there is a tie for most votes, Movie Completion is no longer said to have been achieved, the Royalties of each Scripter are increased by 15, and the dynasty enters the Bribery Stage again. The 'Finale Winner' may achieve victory in the current Dynasty.

A Scripter who joined the game after May 5th 2009 (or unidled after that date) may not change their ‘Vote’ statistic, nor have it changed by another Scripter, nor may they bribe any other Scripter.

Continuity

If any Scripter feels that one or more Scenes in a non-Finished Act contradict a non-cut Scene in a Finished Act, or contradict an earlier non-cut Scene in the same Act, or contains subliminal advertising, he or she may call a halt to the scripting process by posting a comment on that Act that starts with an AGAINST icon, and the word “CONTINUITY!” in capital letters. The rest of this comment should explain which Scenes need to be dropped, and why. Upon doing this, the Act enters Development Hell.

While an Act is in Development Hell, new Scenes may not be added to it, nor may its Scenes be challenged by the mechanic in the previous paragraph.

The Producer may remove an Act from Development Hell by either agreeing or disagreeing with the objection that put it there, in a comment on its Drawing Board. If he agrees with the objection, the Scenes that the Scripter suggested be dropped are now Cut. If the Producer disagrees, then the Scripter who raised the objection is snubbed - if they had a Scene in this Act, they lose all of the Royalties they gained from it; if they didn’t, they may not gain Royalties from any scene they add to this Act.

If a Scripter has been snubbed in regard to their objection about a particular Act, they may not call a halt to the scripting process on that Act again.

The Cutting Room Floor

Whenever a Scene becomes Cut, the Scripter who created that Scene has their Royalties reduced by the Body Count of that Scene.

Best in Show Votes

Once an Act has been declared Finished by the Producer, all Scripters who contributed to that Act may vote on which Scene they feel fitted best into each of the following categories, each of which has a Popularity award:-

  • Best Scene (+1 Popularity)
  • Worst Scene (-1 Popularity)
  • Best Use of an Signature Prop (+0.5 Popularity)
  • Best Supporting Actor (+0.5 Popularity)
  • Best Music Arrangement (+0.5 Popularity)
  • Best Original Punchline (+0.5 Popularity)
  • Worst Original Punchline (-0.5 Popularity)

(A Scripter cannot vote on a Scene which didn’t use a Signature Prop, for “Best Use of an Signature Prop”; nor can they vote on a Scene which didn’t include Stunt Casting, for “Best Supporting Actor”; nor can they vote on a scene which had no Punchline, for Best Original Punchline or Worst Original Punchline; nor can they vote on a scene which didn’t include Theme Music, for Best Music Arrangement.)

Scripters may only vote for one Scripter per category, and may not vote for themselves. Once the votes have reached 50% of the contributing Scripters, the Producer may declare voting to be closed. The Scripter (or Scripters if there is a tie) who receive the most valid votes in each category have their Popularity adjusted as specified, for that category.

Popularity

Popularity is statistic tracked on GNDT, represented by a number . Scripters must add their Popularity (rounding it down to the nearest whole number, and regardless of whether or not it is negative) to their roll for number of Bodies in a Scene. This can result in 0 Bodies, and the player should narrate it as such. This cannot, however, result in a negative amount of Bodies. All new players start with 0 Popularity.

Props

There exists a wiki document called, "Action Props" which contains a list of props which may be used during a Scene. Each Prop has a name and a Challenge Rating, which is an integer equal to the number of words in the name of the Prop.

As a daily action, a Scripter may add a new Prop with a Challenge Rating of DICE5 to the Action Props list; or instead of this, may increase or decrease the Challenge Rating of an existing Prop by adding or removing one word from its name, respectively. When adding or removing a word from the name of a Prop, a Scripter may change the order of words in the Prop's name. If the Challenge Rating of a Prop becomes zero, it is removed from the Action Props list.

Props with a Challenge Rating of 10 or more are called Signature Props.

Using Props

A Scripter may use one (and no more than one) Prop in a Scene by including a Prop section on their Scene specifying the name of the used Prop, and including the name of the Prop as part of the Script. A Scripter may not use a Prop that has been used previously on the same Act (scenes that have been cut do not count for this purpose).

Theme Music

Whenever a Scripter creates a scene, e may decide that a particular song would nicely fit in with the action. Thus, that Scripter may add a section to their scene called “Theme Music” followed by the name of a song and its artist (optionally followed by an hyperlink to a page where the song may be legally listened to).

There exists a wiki document called “Movie Soundtrack” which shall list each one of the Songs (including their respective artists and attached hyperlinks) which have been included in Scenes that have won the Best Music Arrangement Popularity Award for their Scripters. Anybody may update this document, but only with the information allowed by this rule.

Bonus Features

The Producer may occasionally make a request for a bonus feature to be produced. He does this by making a post with a title that takes the format “BONUS: x”, where x is the type of bonus feature that he wants to see made, drawn from the list in this rule. The Producer may request each bonus feature no more often than once per Act.

This request is valid for 48 hours after the time of posting. In this time, each Scripter may produce and submit no more than one valid attempt at satisfying the Producer’s request, which is to be either posted or linked to in a comment to the original post. At the end of this 48 hour period, the Producer may judge one of the attempts to have been the most satisfying. The Scripter responsible for this attempt gains 2 points of popularity, and the winning attempt is archived on a wiki page entitled “Bonus Features”. If the producer decides that none of the attempts were satisfying, or if no attempts were submitted, then all active Scripters lose 0.5 popularity points.

Types of bonus feature:

  • Gag reel: The Scripter may chose any scene from the current unfinished act. If there is no current unfinished act, they may chose any scene from any act. They must then re-write the scene, in no more than 100 words, detailing a take that was unusable for amusing reasons.
  • Making Of documentary: The Scripter may chose any scene from the current unfinished act. If there is no current unfinished act, they may chose any scene from any act. They must then draw the scene (using MS Paint or an equivalent program). This drawing should show a moment of action and should include at least one fatality.
  • Cast interviews: The Scripter may chose any stunt-casted actor from the current unfinished act. If there is no current unfinished act, they may chose any stunt-casted actor from any act. They must then write a short dialogue between that actor and an interviewer (no more than 8 lines each) talking about something utterly unrelated to the project.

Subliminal advertising

A Scripter may add subliminal advertising to their scenes. The manner in which they chose to do so is of their own choosing, but it must be present in the content of the scene, must be observable when pointed out, and must encourage the purchase of an actual, real-world product.

If a Scripter notices subliminal advertising in another Scripter’s scene before the Act is declared to be closed, they may raise a Continuity claim as per rule 2.3.

When the Act is declared to be closed, any Scripter who has an uncut scene which contains subliminal advertising may declare the advertising. They should do so by posting a comment in the voting thread for that Act, outlining the nature of the advertising. The Producer may award 5 Royalties to any Scripter who he feels has implemented a worthy piece of subliminal advertising, to a maximum of 5 Royalties per Scripter per Act.

Taking the Initiative

As a daily Action, a Scripter whose Popularity is higher than that of each other Scripter may steal the Producer’s chair by posting a blog entry to that effect, and reducing their own Popularity by 1.

Upon doing so, that Scripter may consider themselves to be the Producer for the purpose of any Dynastic Rule (except for “Bonus Features”, “Subliminal advertising”, and “The Awkward Aftermath"), for the next hour.

Plot Holes

At any time while an act is in Development Hell for a reason other than Subliminal Advertising, any Scripter that has not submitted a scene for that act may take the act out of Development Hell by Suspending Disbelief. In order to Suspend Disbelief, that Scripter must spend 3 Royalties and create a Scene (even if rule 2.3 Continuity would prevent it) that meets all of the following requirements:

  • The script of the scene must contain a dialog or punchline in which the current state of the preceding uncut scenes is explained in a manner that does not contradict earlier uncut scenes.
  • The scene must not contain subliminal advertising.
  • If a Prop is used on that scene, the name of the Prop must be part of the explanation.
  • If Theme Music is used on that scene, the explanation must be part of the lyrics (songs without lyrics can’t be used).

If the Scene fails to meet any of these requirements, it becomes cut immediately.

Whenever a scene that Suspends Disbelief remains uncut at the time the act that contains it becomes Finished, a Plot Hole is created.

Non-Idle

Players cannot be idled in the current dynasty.

Players are permitted to veto the proposal ‘Veto Bait’, in accordance with the passing of the proposal Veto Bait (http://blognomic.com/archive/veto_bait/)

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 author a banana when enacted would not earn a banana for its own author, 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 published 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.

Flavor Text

  • When posting a blog entry, a Scripter may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

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 Scripter 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 Scripter 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 Scripters, rounded down, plus one.
  • Producer
  • Scripter

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_64&oldid=634"