Re: [s-b] Blueprint Creation

["Jamie Dallaire" <bad.leprechaun@xxxxxxxxx>]

Right. I don't think you can just withdraw an action like that. I OBJECT to
0x44's first attempt to create a blueprint titled "Count Ferdinand von
Zeppelin's Patented Airship". There, now it is withdrawn. 0x44, you should
resubmit this attempt again because right now there is something
conflicting. I therefore OBJECT to 0x44's second attempt to create a
blueprint with the above title. Someone else join me so he can redo it
before the end of the nday?

Here's the problem I think: Something that happens "on nday 12" (Rule 7)
happens at the start of nday 12. The effect of floating eliminates the
possibility of taking damage during that nweek. You should either include
some notice that specifies the precedence between taking 10 damage at the
start of nday 12 and not being able to take damage. Or just make the damage
happen at the start of the next nweek to remove the contradiction.

Billy Pilgrim


On 1/11/08, 0x44 <bnomic@xxxxxxxxxxxxxx> wrote:
>
> Without two objections within two ndays, and as a game action on behalf of
> the Ministry of Goods, I intend to create the following non-unique
> blueprint:
>
> {{
>      Blueprint Title: Count Ferdinand von Zeppelin's Patented Airship
>      Device Title: A Dozen Weather Balloons.
>      Power: Float
>           Effect: The owner is "floated out of range" of any game
> action which would cause them to suffer hit point loss, and cannot suffer
> hit-point loss until the end of the nweek. On nday 12, there is a 10% chance
> (rolled by the Ministry of Play on the Nomic Dice Bot) that the balloons
> will pop ((dumping the owner unceremoniously to the ground)),  causing the
> owner to lose 10 hit points. The device is destroyed at the end of the nweek
> that this Power was Triggered.
>           Conditions: The owner has not triggered the Float Power within
> the past nweek.
>           Trigger: Game Action by owner; declaring eir intention to use
> the device power, and paying an m100 operating cost.
>   }}
>
>
> // That should fix Codae's objection.
>
> --
> --
> 0x44;
>
> _______________________________________________
> spoon-business mailing list
> spoon-business@xxxxxxxxx
> http://lists.ellipsis.cx/mailman/listinfo/spoon-business
>
_______________________________________________
spoon-business mailing list
spoon-business@xxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/spoon-business