Friday, August 25, 2006

Proposal: Tidy up, without spilling it this time

Vetoed upo ascension.—Chronos

Adminned at 26 Aug 2006 08:07:31 UTC

Aran’s Heisenburg Loop effect is much messier than the rest of the ruleset.  I’d like to fix that up - and I warrant that I haven’t changed the effect of the rule - just the spelling, punctuation and grammar.

Remove all the subrules of “Temporal Uncertainty” and replace them as follows.

Add a subrule titled “Out of Time” with the following body.

When a Traveller is “out of time” the following restrictions apply to em.

  • E cannot perform “Marching Time”.
  • Local proposals have no effect on em.
  • E cannot change, create or remove Node Events.
  • E cannot vote on local proposals.

Add a subrule titled “rellevarT lamron” with the following body.

When a Traveller is a “rellevarT lamron” the following effects apply to em.

  • Upon performing “Marching Time”, e will move one day backwards instead of one day forward.
  • e is known as a rellevarT (see below).
  • When posting or commenting, e will write backwards.  This does not apply to templates or GNDT comments.   Example: .sdraekcab etirw lliw e ,gnitnemmoc ro gnitsop nehW
  • When creating or redescribing a Node Event, the description will be written backwards but the time and the keywords will be written forwards.

(No other aspects of game play are reversed.  e.g. When voting, the last vote still takes precedence.)

Special Rules for Backward Writing.

  • When a proposal that was written backward is enacted, the enacted text will be written backwards.
  • If a rule has two meanings, one when reading forward and another when reading backward, the forward version takes precedence.

Add a subrule titled “Melt Down” with the following body.

When a Traveller has a Melt Down, e cannot post or vote exept for voting on a Call for Judgment untill e resolves the Melt Down.  However, e may post in the GNDT or comment in general.

Add a subrule titled “Melt Down Resolution” with the following body.

A traveller can resolve a Melt Down by performing the following actions.

  • Post “DICE3 resolve Melt Down” in the gndt.
  • Where the result of the DICE3 is d:
    • if d=1 the traveller sets eir tl to 1419/11/26
    •  
    • if d=2 the traveller sets eir influence to DICEX where X is eir current influence.
    •  
    • if d=3 all Node Events containing the travellers name as a keyword are deleted except Node Events with the [TIME BOMB] keyword.
  • Remove all eir Heisenberg Loops (by removing the relevant asterisks from eir GNDT entry).

Comments

ChronosPhaenon:

25-08-2006 16:33:16 UTC

for

Bucky:

25-08-2006 16:40:56 UTC

against due to effect:
1)You can remove all your own Heisenberg Loops by resolving someone else’s Melt Down

Hix:

25-08-2006 18:38:34 UTC

(Hiatus begins - voting on Proposals is prohibited)

Thelonious:

26-08-2006 14:45:26 UTC

(Hiatus ends)

against (S-K) and veto