Proposal : I'm Sorry Dave, I'm Afraid I Can't Do That [Trivial]

[ Rather than specifically banning the Computer from every new Crew-Member task we think of, let's just say that it doesn't count as Crew, for anything beyond Rule 10. (It can still Propose and Vote and things, though, of course.) ]

Remove the sentences "The Computer never Faints.", "The Computer may not perform a Task itself; it is already assumed to be doing all it can." and "The Computer may never carry Tools." from the Ruleset, if they're there.

Remove all reference to the Computer having a Rank, and the Rank of "Computer", from Rule 12 (Ranks).

Replace "Any Crew Member other than the Computer" with "Any Crew Member", in Rule 15.

Add a new Rule, "The Computer":-

The Computer only exists as a central processing unit and a series of sensors, cameras and loudspeakers around the ship - it does not count as a Crew Member, for the purposes of Rules outside the Core Ruleset.

Passed 14 to 0 by Brendan at 2:55 pm GMT on 5.17.2004. +2 to Kevan, +1 to Brendan.

Proposal: Stepping Down [trivial]

Add to end of Rule entitled "Ranks":

At any time, the Captain or First Officer may announce, via a post to the blog, that they are stepping down from their rank. If the First Officer steps down, he immediately becomes an Ensign and the Captain may choose a new First Officer from any Crew Member other than the former First Officer, the Computer, or himself; if this creates a void in another Rank, the Captain must choose an Ensign to fill the Rank. If the Captain steps down, the First Officer becomes the new Captain and may choose a new First Officer from any Crew Member other than the Computer or himself. As above, if this causes a void in another Rank, the new Captain must choose an Ensign to fill the Rank.

By itself, there are a couple holes here, but if the below proposal regarding Rank-Changing passes, I don't think they'll pose a problem.

Passed 9 to 2 by Brendan at 2:50 pm GMT on 5.17.2004. +2 to Axiallus, +1 to Brendan.

Proposal: Career Advancement

Add to the end of Rule entitled "Ranks":

At any time, the Captain, First Officer, or Computer may choose to switch the ranks of two Crew Members such that there is no more than one of any rank other than Ensign; this must be announced with a post to the Blog entitled "Post Reassignment". However, this action requires the unanimous agreement of the Captain, First Officer, and Computer, to be signified by posting a "For" reply to the post. If the Captain or Computer desires a Rank reassignment of the Commander, the unanimous agreement of the Computer and all non-ensigns and non-mascots must be obtained, save the Commander, in the above manner; if the Commander or Computer desires a Rank reassignment of the Captain, the unanimous agreement of all Crew Members, save the Captain, must be obtained, in the above manner. The Computer may not change ranks.

It doesn't quite address everything, but I think it's pretty important to have some provision for this.

Self-killed; failed by Brendan at 2:43 pm GMT on 5.17.2004. -3 to Axiallus, +1 to Brendan.

Proposal: Sing Your Blues Away

Still trying to get the spirits of these poor stranded members up, Shade begins humming a tune...

Add a new field to the GNDT, "Sung". All crew members start with an empty Sung field as of the enactment of this proposal.

Add a new Rule, "Singing":

Any Crew Member that is not fainted and has an empty Sung field may sing to try to raise the spirits of his fellows. To do this, the Crew Member (hereafter reffered to as Singer) should:
1) choose, in his opinion, an appropriately uplifting or moving song:
a) any song that has lyrics is electable, as long as it has NOT been sung by another Crew Member during this Dinasty;
2) create a new post in the blog with the title "[Singer's Name] bursts into song!", and containing a part of the lyrics:
a) as a guideline, no less than eight lines and no more than half the song should be posted. This is not strictly enforced, however;
b) the artist's name and the song's title should preferably be included at the end of the post.

After the song part is posted, each Crew Member that is not fainted, with the exception of the Singer, may EITHER:
1) vote FOR the song, stating his or her appreciation of the song selected;
2) vote AGAINST the song, either because they dislike it or find it is not uplifting.

IMP votes are invalid and irrelevant in this context.

An admin should tally the votes for a song once one of three conditions are reached:
1) the "...bursts into song!" post has been online for more than 48 hours;
2) more than half the active players (i.e., quorum) have voted FOR the song;
3) more than three active players (i.e., 4 or more) have voted AGAINST.

In both cases (1) and (2), the song was sung, and the Sung field of the Singer is set to reflect the title and/or the artists that perform the song (whatever is enough to identify the song). Every Crew Member who voted FOR gains 2 health points (from being uplifted), and those who voted AGAINST lose 1 health point (from the suffering). In case (1), the Singer gains 2 health points. In case (2), the Singer, excited with his terrific performance, gains 4 health points.

In case (3), the song was NOT sung -- the opposing Crew Members managed to stop the Singer from continuing. In this case, the Singer loses 1 health point, and no other Crew Members are affected.

Note that cases (2) and (3) might happen in succession. The first one to occur in the timeline counts as the result, independently of the exact time when an admin performs the tally.

The Computer is not affected by singing and cannot sing, although it may suggest a song to other Crew Members (it does not, however, reap any direct rewards from this action).

If the Singer is the Ship's Mascot or any Crew Member with the word Entertainer in his or her rank, Crew Members who vote FOR the song gain an additional health point if the song is successfully sung (they are skilled singers, after all).

Crew Members away on Tasks are still allowed to sing and listen to songs; all songs are transmitted by the crew's intercommunicators.

Failed 6 to 8 by Brendan at 2:38 pm GMT on 5.17.2004. -3 to Shade, +1 to Brendan.

Proposal: Achilles v Tortise [TriviaI]

We've created a contradiction in the ruleset involving victory, fainting, and saboteurs. Rule 11 reads:

11 - Oxygen

Nadil-5's atmosphere has an unusually high oxygen content, and it builds up in the blood of the Crew Members. There is a number called Saturation, which is tracked on the Sidebar; Saturation begins at 0, and increases by 2 every day at 00:00 GMT. Crew Members whose Health is lower than the Saturation have Fainted; Fainted Crew Members may not Declare Victory.

The Computer never Faints.

But Rule 14 reads:

14 - Sabotage?

The Computer may choose to privately contact one or more Crew Members, informing them that they are Saboteurs. If at any point all Crew Members are Fainted and at least one Crew Member is a Saboteur, then any Saboteur may declare victory, in spite of being Fainted

Even though Rule 14 was obviously written so that it would circumvent rule 11, it doesn't. It's also missing a period. I propose we change rules 11 and 14 to read:

11 - Oxygen

Nadil-5's atmosphere has an unusually high oxygen content, and it builds up in the blood of the Crew Members. There is a number called Saturation, which is tracked on the Sidebar; Saturation begins at 0, and increases by 2 every day at 00:00 GMT. Crew Members whose Health is lower than the Saturation have Fainted; Fainted Crew Members may not Declare Victory except under the conditions stated in Rule 14.

The Computer never Faints.

14 - Sabotage?

The Computer may choose to privately contact one or more Crew Members, informing them that they are Saboteurs. If at any point all Crew Members are Fainted and at least one Crew Member is a Saboteur, then any Saboteur may declare victory, in spite of being Fainted.

Passed 12 to 2 by Brendan at 2:34 pm GMT on 5.17.2004. +2 to Trumancapote, +1 to Brendan.

Proposal: Merriment and Joy through Difficult Times

As the sulfuric vapors rise, a shadow comes upon the nearby crew, and concerned frowns spread among them.

Add a new GNDT field, "Morale". Set all Crew Members with an initial Morale equal to 100 when this proposal's passed, and from then on this sentence will only apply to new Crew Members.

Add a new rule to the Ruleset, "Morale":

Each Crew Member has a certain state of spirits, given by his amount of Morale, a number greater than or equal to 0. A Crew Member with 0 morale is said to be in Panic. Crew Members in Panic may not claim victory or engage in Tasks.

Failed by Kevan, 15th of May. -3 to Shade, +1 to Kevan.

Quick!

The first Ensign to comment on this post will be made Ship's Mascot.

Task: Cough, Cough

The drilling had started out so well, almost without a hitch. The crew were having no troubles filling their personal tanks with crude oil from a richly flowing spout. Then, the watchful eye of Shade noticed something a bit strange in the rigging. As he peered down the crack that their drills had made in the surface, he noticed a strange yellow mist slowly beginning to form within it.

Quickly, he went to Science Officer CzarOfCanada, whose best guess as to the makeup of this fog was sulfuric vapors, perhaps coming from within rock cracked by the digging. They didn't look problematic now, but he knew that, if they got much stronger, it would be hazardous to approach the oil well at all.

The question was what to do about it?

-------------------------------------

THE TASK:

Decide what to do about the vapors. If you are one of the people who sign up to help on this task, include what you think the best course of action to take would be. The decision of the highest-ranking officer to work on this task will be the one followed.

KEYWORDS: None
NUMBER OF CREW MEMBERS REQUIRED: 9
EFFECTS: To be determined.

Pesky Computer

I took the Blowtorch for myself, being the Engineering Officer and all. But the pesky computer won't let go. The GNDT won't let Cayvie have no tools. I don't know how to fix this, but if an admin could look at it...

Call for Judgment

Cayvie enacted "Proposal: The Age-Old Question" that should not have passed, in my opinion, given the following passage:

Rule 5

"If a Crew Member leaves the game or goes idle, their Vote no longer counts."

... Satyreyes' vote FOR his proposal should not have counted, bringing the tally down to 8 FOR and 8 AGAINST, at which point this passage kicks in a fails the proposal:

Rule 6

"If the oldest pending Proposal's FOR votes exceed or equal Quorum, or if it is more than 48 hours old and more than half of its votes are FOR, then any Admin Staff may mark that Proposal as Enacted, then update the Ruleset and/or Gamestate to include the specified effects of that Proposal."

If that is debatable due to timing issues then perhaps a reading from this will help:

Rule 2

"For the purposes of all other rules, idle Crew Members are not counted as Crew Members."

and rule suggests that the proposer is a Crew Member but according to Rule 2 the proposer is not a Crew Member:

Rule 5

If the Crew Member who made a Proposal has not cast an explicit Vote on it, their Vote is counted as FOR.

I know this is quite debatable as we have, I believe, a precedent such that when an individual goes idle and there are pending proposals prior to his/her idleness that we have counted their votes when enacting or failing a given proposal. I submit to you that we were wrong in doing so as outlined in the above passages and that if enough people actually agree with this CFJ that this ambiguity should be clarified in the ruleset through some proposal at a later date. So, I suggest that the enactment be reversed and that rule 14 be removed from the ruleset, does anyone agree?

Proposal: The repaired fixer

Enact a rule title "Transfers" that reads:

The medical bay has equipment that can be used to trasfer Health from one Crew Member to another, but use of the equipment requires the supervision of either the Medical or Science Officer.

The donating player posts to the BlogNomic Blog with the title "Transfer" stating which Officer is being asked to supervise, which Crew Member is receiving the transfusion, and how much Health is being transfered. The receiving player and the supervising Officer must vote for the tranfer within 72 hours for it to succeed. Officers may not supervise transfers they are otherwise involved in.

If the receiving Crew Member is fainted, their vote is an automatic "for," which cannot be changed while they remain fainted. If the supervising Officer is fainted at anytime between the initial request of the transfer and it success, the transfer automatically fails. A failed transfer has no effect.

If a transfer succeeds, any Crew Member involved in the transfer may record it in the GNDT, so long as it has not been previously recorded.

A transfer supervised by the Medical Officer, due to extensive training, occurs on a 1:1 basis. The Hippocratic Oath required of Medical Officers does not allow them to authorize transfers great enough to cause the donating Crew Member to faint.

In a transfer supervised by the Science Officer, because of relative inexperience with medical equipment, the receiving Crew Member gains only 2 Health for every 3 Health the donating Crew Member loses (rounded down). However, as Science Officers do not take the Hippocratic Oath, they allow transfers great enough to reduce the donating Crew Member's Health to ten less than the Saturation Level.

Enacted by Kevan, 15th of May. +10 Health to Ornithopter, +2 to Kevan.

Advertisement

A brief plug for a Nomic-type game that might be of interest to those who were around in the First Dynasty of Keitalia - Rumble is a super-hero power-inventing bidding game that ex-player Ben created a few years ago, and that I was plundering a bit during the Dynasty. We've recently set up a mailing list for playing the game online, and it seems to be working out alright - a new game is soon to begin, if anyone's interested.

Proposal : Tidying the Toolbox [Trivial]

[ Polishing the "Tools" rule a bit, and also changing it so that Crew can only steal Tools from lower-ranking Crew Members. ]

If the Proposal "Disco Inferno" unaccountably failed, this proposal shall have no effect.

In the "Tools" rule, replace "There exist several tools for Crew Members to use on the ship. The tools are:" with:-

There exist several Tools which Crew Members may carry around (as tracked in the GNDT), some of them requiring fuel to activate. Any Crew Member may pick up a Tool which exists in the game but isn't carried by anyone, and may drop a Tool they are carrying, or give it to someone else. Crew Members may also permanently commandeer Tools from lower-ranking Crew Members.

The Computer may never carry Tools. When a Crew Member goes Idle, they drop all of their Tools.

The Tools that exist are (with their available quantity in brackets):-

Reword "Blowtorch" to:-

Blowtorch (1): The Blowtorch costs one unit of lowgrade fuel per use.

If the Computer has the Blowtorch, it drops it.

Enacted by Kevan, 15th of May. Timed out 8 votes to 3. +3 Health to Kevan.

Proposal: This'll fix him!

Repeal any sentences dealing with the transfer of Health between Crew Members. [The ruleset is down at the moment, so I'm playing it safe.]

Enact a rule titled "Tranfusions" that reads:

The medical bay has equipment that can be used to trasfer Health from one Crew Member to another, but use of the equipment requires the supervision of either the Medical or Science Officer.

Unless currently fainted, the Medical Officer automatically supervises Health transfers. Due to extensive training, transfers under the Medical Officer's supervision occur on a 1:1 basis. The Hippocratic Oath required of Medical Officers does not allow them to authorize transfers great enough to cause the donating Crew Member to faint.

If the Medical Officer is fainted, and the Science Officer is not, the Science Officer automatically supervises Health transfers. Because of relative inexperience with medical equipment, the receiving Crew Member gains only 2 Health for every 3 Health the donating Crew Member loses (rounded down). However, as Science Officers do not take the Hippocratic Oath, they allow transfers great enough to reduce the donating Crew Member's Health to ten less than the Saturation Level.

If both Medical and Science Officers are fainted, then there may be no transfers.

[I phrased it as "is fainted" rather than the prefered "has fainted" to allow a revived Medical/Science Officer to supervise transfers.]

Failed by Cayvie on 5.14.2004. -3 to Ornithopter, +1 to Cayvie.

Task: Shaking It Up

(seismic activity detected)
[run RichterScale]

RICHTERSCALE OUTPUT 16:53:28 5-12-3004
>RichterScale: 2.3
>Epicenter Location: 1.3 km NNE

------------------------------

Meanwhile, in the lab...

CzarOfCanada, while Kevan and Shade watched closely, examined the soil samples in the Matter Magnifier. He did indeed find evidence of life: there were several small, almost microscopic, things that looked somewhat like flatworms. However, they all appeared completely dead. On closer examination, he discovered that they were be carbon-based lifeforms with silicon exoskeletons.

------------------------------

THE TASK:

The Computer has realized, with the seismic activity and the existence of carbon-based life, that this planet probably has reserves of oil. As the necessary equipment is on the ship already, the Computer thinks it would be prudent to begin a test drilling. After all, the ship doesn't need that much fuel to run, and with modern equipment, fuel is easy to synthesize from crude oil.

CREW MEMBERS REQUIRED: 10
KEYWORDS: Engineer

GAMESTATE/RULESET EFFECTS:
To be announced.

-------------------------------

TASK COMPLETED.

Under the capable guidance of TrumanCapote, the crew set up a working oil pump with surprising ease; not even any injuries during the process. The seismic activity has continued to increase in intensity, however, which has caused some worries about the stability of the station.

GAMSTATE/RULESET EFFECTS:
Any crew member who worked on this may add up to 5 Low Grade Fuel to his or her GNDT value.

Additionally, add the following to rule 15, Fuel:

Any Crew Member other than the Computer may, once per day, add 5 Low Grade Fuel to their GNDT value, from the oil rigging.

Any Crew Member, can choose, at any time, to transfer any positive integer amount of his or her Low or High Grade Fuel to any other Crew Member.

The ship requires 10000 High Grade Fuel to travel one light-year. Any Fuel in the Computer's possession is considered to be in the ship's engine.

Saturation calculation

First of all, why is the saturation at 4? I set it to 2 at GMT midnight, and only one midnight has gone by since its passing.
Is there some way for a javascript to be added that automatically calculates the saturation? it seems quite easy to do at the moment.

Proposal : Job Done [Trivial]

[ Fixing the slightly careless immediacy of Task resolution, clarifying that Crew can't join an already-completed Task, and specifying (now that the Computer wants secret effects) that the Computer alone must process the results of the Task. ]

In Rule 13 (Tasks), replace "Task is completed, with the effects that were specified" with:-

Task is completed - no further Crew may perform it, and the Computer must process its effects before posting further Tasks

Passed by Cayvie at 19:25 GMT on 5.14.2004. +2 to Kevan, +1 to Cayvie.

Proposal : Hands-Free, Lungs-Free [Trivial]

To Rule 13 (Tasks), add to the end of the fourth paragraph:-

The Computer may not perform a Task itself; it is already assumed to be doing all it can.

And to Rule 11 (Oxygen), add a new paragraph:-

The Computer never Faints.

Passed by Cayvie at 19:17 GMT on 5.14.2004. +2 to Kevan, +1 to Cayvie.

Later, guys! --Satyr Eyes

Lately I'm catching myself taking the game personally, which is a sure sign that I need a break! (And it's not because I'm Ship's Mascot, I promise.) I'll be back, hopefully, once schoolwork gets a little lighter. I've put myself on the Idle list in the saved template, but I'm having trouble republishing the blog, so I'll leave that to someone else.

Peace out, yo!

Task - Soil Sample

[run lifeform scan]

LIFEFORM SCAN RESULTS 05:52:55 05-12-3004
Biomass Detected!
[list: lifeforms within 100 m]
>Humanoid - 17, totaling 951.32 kg
>Unidentified - approx. 1.4e6, totaling .004kg

Unidentified Lifeform Detected!

------------------------------------------------

THE TASK:

The Computer desires soil samples to be brought into the laboratory and analyzed, to discover more about this unidentified lifeform.

CREW MEMBERS REQUIRED: 5
KEYWORDS: Science

GAMESTATE/RULESET EFFECTS:
Each Crew Member who takes on this task will suffer a 50% chance of losing 1d6 Health.
Each Ensign who takes on this task will gain 3 Health.
(these effects will be explained if this task is completed)

The character string " - these must be clearly stated in the post" will be deleted from rule 13. Come on... wouldn't it be more exciting if you didn't know what would happen if you took on a task? I'm not going to do anything silly like give Octave 1000 Health for no reason.

------------------------------------------------

Processed by Kevan - Kevan and Czar took 1 damage each, and Shade sustained 5 and gained 3.

Proposal: Task Rewards

Those who work hard earn the right to extra care in the med bay. Append the following to the rule entitled Tasks:

If you are a part of a team that successfully accoplishes a task, you gain 5 health. If you are a key officer in this task you instead gain 10 health.

Failed by Cayvie at 19:16 GMT on 5.14.2004. -3 to CzarOfCanada, +1 to Cayvie.

Ranks

[list: crewmember ranks]
>Captain - Hobbes
>First Officer - Royce
>Computer - Cayvie
>Science Officer - CzarOfCanada
>Medical Officer - Damanor
>Engineering Officer - TrumanCapote
>Navigation Officer - Ornithopter
>Mess Officer - Kevan
>Ensign - Axiallus, Brendan, ChinDoGu, kahbn, Keitalia, Octave, Aaron, Yagyu_Jubei, Shade
>Ship Mascot - SatyrEyes

In case anyone's wondering, I used the random number generator at www.random.com to assign these

Proposal: Disco Inferno

Create two new GNDT fields, Low Grade Fuel and High Grade Fuel. Each Crew Member's Low Grade and High Grade Fuel will be set at 15 when this proposal is passed, and then this sentence will repeal itself. Also add to the Ruleset a new Rule: Fuel:

There exists two types of fuel on the ship for use. The two types are high grade and low grade fuel. A Crew Member may use two units of Low Grade Fuel to create one unit of High Grade Fuel.

Add a new field to the GNDT, Tools. Create a new item to be tracked in the field Tools, Blowtorch. Add rule Tools to the ruleset:

There exist several tools for Crew Members to use on the ship. The tools are:
- Blowtorch: The blowtorch begins in possession of the Computer and then this sentence repeals itself. There is only one Blowtorch on the ship. Any Crew Member may take the blowtorch from another Crew Member and put it into his GNDT field, Tools. The Blowtorch costs one unit of lowgrade fuel per use.

Passed 9-8 by Cayvie at 20:05 GMT on 5.13.2004. +10 to TrumanCapote, +2 to Cayvie.

(the wiki seems to be wonky lately; i'm not sure if my edits were saved successfully)

Proposal: The Age-Old Question

When enacted, this proposal shall be construed to consist only of its nonitalicized text.

So Cayvie, why are we here? Why didn't we make it to Terra Nova?
>system records indicate unplanned fuel shortage necessitated emergency landing
Yes, but why did our fuel run out so early?
[run retrieval protocol]
>RETRIEVAL OUTPUT: 05-11-3004 20:43
>unable to verify cause of fuel shortage
That's odd. Do you remember when fuel first fell below mission parameters?
>memory failure in sector 01010110
What is the cause of the memory failure?
[run system diagnostic]
>DIAGNOSTIC OUTPUT: 05-11-3004 20:45
>unable to verify cause of memory failure; memory banks may be compromised
Compromised? By what? Or whom?
>memory failure in sector 01010110
Well, that's real helpful.
>beggars can't be choosers, meatbag
Ha ha. Who did your AI, anyway?

Add a Rule, "Sabotage?":

The Computer may choose to privately contact one or more Crew Members, informing them that they are Saboteurs. If at any point all Crew Members are Fainted and at least one Crew Member is a Saboteur, then any Saboteur may declare victory, in spite of being Fainted.

Passed 9-8 by Cayvie at 19:56 GMT on 5.13.2004. +10 to Satyr Eyes (except he's idle), +2 to Cayvie.

Proposal: Crew Member Titles

Add a list of titles to Rule 2:

Titles can be awarded by the Computer or by majority vote by other Crew Members. The current list of titles is as follows:

^: The Crew Member with the carat has won the Jimmy Tiberius award of Crew Membering Excellence.
(): The Crew Member with the empty parenthesis is known as the Mad Fremen Crew Member.
:*|: The Crew Member or Crew Members with the colon-asterisk-pipe are known as the Amazing Dagobah Champions.
_o/: The Crewmember with the underscode-oh-slash "arm up" signal is known as the Avid Red Shirt Ensign or Avid Red Shirt Officer, as deemed appropriate.

Errr, would people who voted "nay" on this one just because it was, err, well, invalid, please reconsider? Thanks in advance. >:)

Err 2: please disconsider. This proposal has been self-killed due to inadvertent unadvised tampering with. Sorry for any inconvenience. Please proceed to the next proposal and have a nice day.

Failed (self-kill) by Cayvie at 05:21 GMT on 5.12.2004. -3 to Shade, +1 to Cayvie.

Proposal : Now You're Well Again, and There's Work To Do

Enact a new rule, "Tasks":-

The Computer will periodically announce Tasks that it requires the crew to perform for it, to assist the repair and running of the ship; these are made as entries to the BlogNomic weblog, with a subject line of "Task : {Title}".

Each Task requires a specific number of Crew Members to perform it (at least one), may have one or more defined effects on the Ruleset or Gamestate upon completion (which may include random numbers and conditions), and may have a number of descriptive keywords (such as "Medical" or "Engineering") - these must be clearly stated in the post.

Crew Members may declare their intention to perform a Task by responding to its post with a comment that includes a FOR vote. As soon as a sufficient number of Crew Members have declared such an intention, the Task is completed, with the effects that were specified.

If a Task remains pending and unperformed for 48 hours, then it expires with no effect.

If "Rank and File" passed, add the following paragraph after the third paragraph of the new "Tasks" rule:-

If any word of an Officer's Rank appears in the keyword list for a Task, that Officer counts as three Crew Members, for the purposes of performing that Task.

Passed 11 to 2 by Cayvie at 03:40 GMT on 5.12.2004. +10 to Kevan, +2 to Cayvie.

Proposal : Rank and File

Enact a new rule, "Ranks":-

Each Crew Member has a Rank, which (as a result of some temporary life-support-blip amnesia) defaults to Ensign - all Ranks other than Ensign are referred to as Officers. If an Officer's Rank is unassigned, then the Computer may consult its data banks and assign that Rank to any Ensign. The Computer always has the rank of "Computer".

The Ranks are, in descending order:-

• Captain.
  
• First Officer.
  
• Computer.
  
• Science Officer.
  
• Medical Officer.
  
• Engineering Officer.
  
• Navigation Officer.
  
• Mess Officer.
  
• Ensign.
  
• Ship's Mascot.
  

Passed 11 to 2 by Cayvie at 03:32 GMT on 5.12.2004. +10 to Kevan, +2 to Cayvie.

Idolitry

Nice redeign, Blogger.

I'm going on holiday for a week. Much as I hate to miss the first week of the dynasty, I look forward to seeing how far you've got when I get back.

Try and make it a game this time :)

Proposal : Di-Nitro-Bi-Oxalide

The air of the planet Nadil is poisonous to human life forms.. And the ships limited supply is fast running out. Create a GNDT entry for the ship, and add a new GNDT Column "AIR" All players have 0 Air and the ship begins with 25.4 air.

Create a new rule entitled "Hull Breach"

Once per week, the computer will deduct from the air reserves of all players 0.1 units of air. Should any player have no air to be deducted in this way, the air is instead taken from the ships reserve. Should there be no air remaining in the ships reserve at this time, all players who did not have air available suffer 10 points of health loss.

Additionally at this time the computer deducts 1.0 units of air from the Ship, due to leakage from the hull damage

Failed 6 to 9 by Cayvie at 01:30 GMT on 5.12.2004. -3 to ChinDoGu, +1 to Cayvie.

hey

hey, I'm new here. I'm actually friends with Cayvie. He's been trying to get me to join for like 3 cycles of the game now. I guess I finally caved. I remeber seeing that there's a prize for him for doing so, so I'm just letting people know that he's responsible for me being here. Oh, and behold the might of the Czar's mounties, bwahahahaha.

Proposal: Woooozy...

When enacted, this proposal is considered to consist only of its non-italic text.

>input identity
Aw, did you break your retinal scanner? I'm Satyr Eyes.
>input password
******
>input command


Delete the list of titles in Rule Two.


>command delete: acknowledged
[file deleted]
Thank you. Can you tell me why you've brought us out of cold sleep?
>affirmative
Cayvie, you know we've discussed this. Remember my lecture on giving relevant answers to my questions?
>affirmative; system response precipitated by critical fuel condition, 05-10-3004, 06:20:23
Then... this isn't Terra Nova?
>negative
Well, horse pies. I suppose we'll need to gather more fuel. Cayvie, why do I feel so lightheaded?

Add a Rule, "Oxygen":

Nadil-5's atmosphere has an unusually high oxygen content, and it builds up in the blood of the Crew Members. There is a number called Saturation, which is tracked on the Sidebar; Saturation begins at 0, and increases by 2 every day at 00:00 GMT. Crew Members whose Health is lower than the Saturation have Fainted; Fainted Crew Members may not Declare Victory.

Passed 9 to 0 by Brendan at 5:44 pm GMT on 5.11.2004. +10 to Satyr Eyes, +2 to Brendan.

New Crew Member

(new lifeform detected)
>class: humanoid
>name: CzarOfCanada

Redefinition of Terms

[term replacement initiated]
>"Haxxor" => "Crew Member"
>"Poet" => "Computer"
>"Ware" => "Health"
[term replacement successful]

Ascension Address

[run diagnostic scan]
DIAGNOSTIC SCAN OUTPUT: 05-10-3004 03:44:13
>deflection shields = 25.1: Good
>air = 30.2: Good
>fuel = 1.5: WARNING! Low Fuel!

(front sensors triggered)
[run optical scan]
OPTICAL SCAN OUTPUT: 05-10-3004 04:35:45
>object identified as planetoid
[checking galactic database]
>planet identified as Nadil-5

DESCRIPTION OF NADIL-5

Diameter: 22,010.31 km
Surface Gravity: .5112 G
Atmosphere: 50.3% N 41.4% O 4.9% S 3.0% Ne .3% C
Lifeforms: None known

[run diagnostic scan]
DIAGNOSTIC SCAN OUTPUT: 05-10-3004 06:20:23
>deflection shields = 25.1: Good
>air = 25.4: Good
>fuel = 0.2: WARNING! Critical Fuel Emergency!

[initiating emergency landing on Nadil-5]
>landing successful: minor damage to hull, rear thrusters

Declaration of Victory

I won, apparently.

I think I have to make a declaration of victory... and we do go into a hiatus now, I believe.

Ballot Box

This is the duly-posted election notice, under which voters should record their choices for Emperor, before 23:59 GMT on May 10, pursuant to Rule 11.

It is 00:00 GMT on May 11 and voting is now closed. The winner, by two votes to zero, is Cayvie.

Congratulations to the new Poet! You may post an Ascension Address at your leisure.

Break (in the Haxx0r and billiards sense)

In Rule 11, Support Network, change:

Once all active Haxx0rs have designated their support, or when 5 Mays from enactment has passed

to:

Once all active Haxx0rs have designated their support, or when 5 days from enactment has passed

And -- hmm, what's this? It would seem that we are five days from enactment! Fancy that! I guess that makes Cayvie and Royce the candidates. Rather nice that they don't have to choose running mates, since neither is a Bach candidate. And -- by Jove! -- the election will end in, what, fifteen minutes? What impeccable timing!

w00t

Break (Formerly known as "hatxx0rati0n")

I feel that musicians as a whole are underrepresented in BlogNomic. As a result, I make the following change:
In Rule 11 - Support Network

Each Candidate must choose a running-mate and a communications officer.

becomes

Bach Candidate must choose a running-mate and a communications officer.

If anyone can do that to get Sergei Rachmaninoff into this ruleset, I'll give you all my Warez.

BackBlog, where have you gone?

Okay, is it just happening to me, or have others of you completely lost BackBlog? I haven't been able to leave comments from my home computer for several weeks now.

BackBlog still works on the computers at school, but I can only get to those about every other day - not to mention they're all POS's. Does anyone have any suggestions? Does it have to do with the browser settings on my machine at home? Help!!

Idle players

Udelar and est have been set to idle for nonvoting. Quorum is 9.

In honor of the passing of "Hats are not 1337," I'd like to refer you all here.

Thank you for your time.

Proposal : Quantium Mechanic [Trivial]

Update the rule "Hey, y’all! Watch THIS". Replace the section which reads...

A player’s Audience will always be an integer greater than zero

with

A player’s Audience will always be an integer greater than or equal to zero

Vetoed by Cayvie.

Proposal: 1337ing It Up (trivial)

Okay, there were, as I feared, a few oversights in my earlier proposal.

Be it resolved that Kevan is politely requested to fix the bug in the GNDT wherein the WarezRunning and Running fields are not allowed to contain discrete values.

At such time as the aforementioned bug is resolved, "Tailor Ware" shall be replaced with "Stimware" in the GNDT, "Sailor Ware" with "Swimware", "Captain's Ware" with "Headware", "Birthday Ware" with "Firewall", and "Lemon Rabbit Stew" with "Lemon Cyberdust".

Amend Rule 20 to read:

All Haxx0rs are haxx0ring beneath the noses of un-1337 policemen who do not understand that information wants to be free.

Each Haxx0r has a Notoriety representing how many law enforcement officers are concentrating their attention solely on them at any given time. A Haxx0r’s Notoriety is equal to their WarezRunning? times their Criminality (rounded down). Both Audience and Criminality are tracked in the GNDT.

A Haxx0r’s Notoriety will always be an integer greater than zero. If the total Notoriety of all Haxx0rs would exceed 5000 at any time, all Haxx0rs’ Notoriety will be reduced equally until the total is again less than or equal to 5000.

Criminality may be any number greater than or equal to zero with no more than two decimal places. Certain techniques may alter the Criminality of the Haxx0r performing them or of another Haxx0r. As methods are devised, they should be appended to the end of this Rule in the following format:


Name of Technique. Cost: X This Technique has certain effects, etc.

Satyr Eyes receives no Warez from this Proposal's passage. The 2 Warez he would otherwise receive may optionally be claimed by ChinDoGu, conditional on his fixing the paradox noted in the previous post while employing game terms consistent with this Proposal.

Vetoed by Cayvie.

Paradoxical Observation

Well. We have just created a paradox. Does that mean the blog comes to an end.

A player’s Audience will always be an integer greater than zero. If the total Audience of all players would exceed 5000 at any time, all players’ Audience will be reduced equally until the total is again less than or equal to 5000.

So, My audience value must be >0

Each player has an Audience representing how many spectators are concentrating their attention solely on them at any given time. A player’s approval rating is equal to their HatsOn? times their Enjoyability (rounded down). Both Audience and Enjoyability are tracked in the GNDT.

so my audience value must be 0 (Sincemy hatson is 0 and my enjoyability is undefined)

What happens now?

New Player...?

On the stage, the wearers of a thousand hats danced and danced as their audience looked on in wonder at their feats. Not a man in the crowd was not enraptured by the performers' display of skill.

What better way than to keep the rabble content and unsuspicious than with perpetual hat dancing? This had been the reasoning long, long ago, when the BlogMatrix had first been constructed.

But now there was a problem. The machinery was sparking. In a colossal oversight, the source code to the BlogMatrix had been left accessible to those inside it. No one had ever meant for the BlogMatrix to be self-amending, but now it was, and the world teetered on the brink of another revolution.

Inside the network, a sentient program scanned the BlogMatrix. For a moment, the hat dancers saw a pale, unfamiliar face in the crowd. But in the next moment it melted away -- and those on stage wondered whether it had ever been there at all.

Say hello, and goodbye, to Shade.