New Robot : Damanor

A new Robot has been delivered to the Factory - Damanor enters the game with 168 Power. Welcome aboard.

Proposal: Efficiency Rewarded

In rule 11, The Master Control Program, replace the block of code beginning "// Create a single item of Product" with:

// Create a single item of Product

if (efficiency(self) > 3)
{
X=10
}

if (efficiency(self) < 4)
{
X=15
}

if (power(self) > 50 && keyword = "PRODUCT")
{
power(self) = power(self)-X;
inventory(self) = inventory(self) + product_object
}

Enacted by Mat, 26th Sept.

Proposal : Flat Batteries

In Rule 2 (Robots), replace "Admin may render a Robot Deactivated if that Robot has failed to vote for more than a week, or if that Robot has asked to become Deactivated." with:-

Admin may render a Robot Deactivated if that Robot has failed to vote for more than a week, or if its Power is zero, or if it has asked to become Deactivated.

Enacted by est, 25th Sept. +12 to Kevan, +5 to est

Proposal: Pro-choice!

[making recharging a function i can perform, not just a side-effect of running the MCP]

in rule #11 - The Master Control Program, change:

if (self = the_control_unit)

to the following:

if (self = the_control_unit && keyword ="RECHARGE")

Enacted by est, 25th Sept. +21 to est

Proposal : Use this patch immediately !

Enact a new Rule, "Virus!":-

The Ruleset has been infected with a corrupting virus! At some point each Monday, the Control Unit must select a random rule, then select a random number within that rule (if any are there). That number has a 50% chance of being halved (rounding up), and a 50% chance of being doubled.

Enacted by est, 24th Sept. +12 to Kevan, +5 to est

Proposal : Battery Packs

[ Adding extra battery packs, and a way to create them, and a way to choose whether to create a battery pack, or some Product, or neither... ]

To the syntax list in Rule 11 (The Master Control Program), add:-

keyword. When a Robot calls the MCP, it may optionally include a single keyword of its choice (eg. "PRODUCT").

In Rule 12 (The MCP), replace "if (power(self)>50)" with:-

if (power(self) > 50 && keyword = "PRODUCT")

Also add, before "// Check to see":-

// Create a supplementary battery.

if (power(self)>50 && keyword = "BATTERY") 

{ 

  power(self) = power(self)-50; 

  inventory(self) = inventory(self) + battery_object 

}

Replace the "vent excess power" code with:-

// Vent excess power. 

if (power(self) > (100*(1+number_of_batteries(self))))

{ 

  power(self) = (100*(1+number_of_batteries(self))); 

}

Enacted by est, 24th Sept. +12 to Kevan, +5 to est

Proposal : Producing the Product

Add a new Rule, "Inventory":-

Each Robot has a hollow casing which they can store items inside; this Inventory is tracked as a single GNDT text field (eg. "3 Product, 1 Box, 2 Fuel").

To the MCP, after the first line, add:-

// Create a single item of Product.

if (power(self)>50)

{

  power(self) = power(self)-10;

  inventory(self) = inventory(self) + product_object

}

Enacted by est, 23rd Sept. +12 to Kevan, +5 to est

Proposal : Power Venting

[ If we're using batteries, we should have some sort of cap on maximum power (which could be changed by buying extra cells, I suppose, later). ]

Add to end of the MCP:-

// Vent excess power.

if (power(self) > 100)

{

  power(self) = 100;

}

Also replace "power_unit" with "power", in the rest of the MCP, as that got missed when we renamed Power Units.

Enacted by est, 23rd Sept. +12 to Kevan, +5 to est

Proposal: Power usage

To Rule #9 : "Power" add:

"For example: Voting is a relatively simple action, requiring only 1 unit of Power."

before the sentence starting:

"New Robots start with..."

Self-killed by est, 23rd Sept. -5 from est, +2 to est

Factory Eventlog

In response to the recent flurry of activity, the Control Unit has run the Master Control Program.

030922172755 - CONTROL UNIT::MCP
> RETURN: OK (All Robots updated successfully)

All Robots have been recharged with 50 Power as an incentive for increased productivity.

Have an industrious day!

Proposal: prevention of veto mishaps (revised)

I proposed this at the start of the new dynasty and was asked to correct and resubmit the proposal. It's been updated with new terminology and the requested modifications.

---

[ I'm hoping that this will assist (or at least inspire someone to propose something that will assist) in having a set way to overturn a veto without having to default to a CFJ.]

In rule 18-Dynasties, change the line stating:

However, a veto may be overturned if all other Robots vote FOR the vetoed Proposal within 48 hours of the initial Proposition."

to

However, a veto may be overturned if a Request for veto annulment is declared. Requests for veto annulment may not be vetoed by the Control Unit; as they aren't traditional, rule changing propositions.

If the consensus on the Request for veto annulment results in a FOR count of two-thirds of active Robots or greater, one strike is placed upon the Control Unit. If three such requests are successfully put forth in one dynasty, the Control Unit will be removed and nominations for a new Control Unit may be posted.

This, in turn, will require Control Units to veto wisely.

Enacted by Squirrel, 22nd Sept.

Proposal: Let's Dance

enact a rule called "Robot Dance" that follows:

Each robot may take a break from their busy schedule of object assemblage. Once per week any robot may dance for Power. A robot that wishes to dance must first spend two Power Units and then post a colourful dance move. At the end of the week the Control Unit shall reward the most interesting dancing robot with 10 Power Units.

Failed by est, 22nd Sept. -5 to Gillian, +2 to est.

Proposal : Jargon 2.0 [Trivial]

Replace "Power Unit" with "Power" throughout the Ruleset. (It's slightly confusing that we have both Power Units and a Control Unit.)

Also, replace "Idle" or "Temporarily Deactivated" (whichever is in use) with "Deactivated", and any clumsy "un-X" type wording with "Reactivated".

Enacted by Mat, 22nd September.

Proposal: Underhaul

I noticed that since we have no more government we should actually make the Veto useable by our esteemed Control Unit

so, ammend rule 18 such that:

The Control Unit may veto any Proposal, provided that there are at least two Robots in Government. A vetoed Proposal immediately fails. However, a veto may be overturned if all other Robots vote FOR the vetoed Proposal within 48 hours of the initial Proposition.

becomes:

The Control Unit may veto any Proposal, provided that there is at least one Robot voting AGAINST a given proposal. A vetoed Proposal immediately fails. However, a veto may be overturned if 2/3rds of the total Robots vote FOR the vetoed Proposal within 48 hours of the initial Proposition.

What think you, my fellow mechaniks?

Enacted by Mat, 22nd September.

Proposal: Revamp [Trivial]

In the spirit of robotness.

Make the following changes in the ruleset:

replace "favor" with "efficiency"
replace "idle" with "temporarily deactivated"

Enacted by Mat, 22nd September.

Setting Cayvie as "Idle"

Hi all,

Just setting Cayvie as "Idle", as it's been a while since he's been around. When he gets back we can mark him as active again.

Proposal : The Master Control Program

[ Tentative attempt to introduce an aspect of programming into the Nomic - a rule that contains a simple series of instructions, which the Robots can choose to run once per day. Initially it just contains instructions to let the Control Unit boost all Robots' Power Units (as in the earlier Proposal), but the intention is that the MCP source code will become more and more elaborate and useful, with Robots proposing to change it a bit at a time.

I've tried to make this reasonably non-programmery, so that it can just be seen as a simple list of commands for a Robot to process - kick me and amend things, if I've made any careless assumptions. ]

Enact a new Rule, "The Master Control Program":-

Each Robot has an identical copy of the Master Control Program installed, and may run it no more than once per day. Upon running the MCP, the Robot should process each of its lines in sequence, until it reaches the end.

The Master Control Program is written in a vague and dynamic language resembling simple English, but uses a few specific terms:-

• self. "self" represents the Robot calling the program; any gamestate data that applies to a Robot may be measured or altered.
  
• if. If statements depend on a specific condition - if that condition is true, the bracketed statements immediately following the "if" are processed. If it is false, the bracketed statements are skipped.
  
• loop (robots). The bracketed statements immediately following this statement should be processed once for each Robot (in alphabetical order). Within the loop, "loop_robot" represents the Robot being processed during that loop cycle.
  
• //. Lines beginning "//" are comments, and have no effect.
  

Where there is any disagreement over the execution of the MCP, the Control Unit may settle the matter and modify the source code to remove any ambiguity.

Enact a new Rule, "Master Control Program Source Code":-

// Master Control Program

// Check to see if the Robot running the program is the Control Unit.
if (self = the_control_unit)
{
  // Loop through the robots and add 50 to all Power Unit ratings.
  loop (robots)
  {
    power_unit(loop_robot) = power_unit(loop_robot) + 50;
  }
}

Remove the paragraph beginning "The Control Unit may, no more than once per week" from the Ruleset.

Enacted by Mat, 22nd September.

Deadlock gridlock

Attention all units!

The proposal entitled "Proposal: Prevention of further veto mishaps" is currently deadlocked at 2/4 FOR/AGAINST.

Please acquaint yourself with this proposal.