change rule 2.10.1:

2.10.1 Heisenberg Snare
Requirements: Target Traveller is within this Traveller’s range, and this Traveller has an influence greater than 10 (the target traveller may be this Traveller emself).
Action: This traveller reduces eir Influence by 10. Target Traveller gains a Heisenberg Loop.
The Target Traveler may lose this Heisenberg Loop after 96 real world hours.

where to lose is the opposite of to gain, meaning to manually enter the gndt and remove an asterisk.
e can only lose Heisenberg Loops if e gained them by a Heisenberg Snare at least 96 real world hours ago.

change rule 2.6.1:

2.6.1 Temporal Uncertainty
Some Travellers may be in one or more Heisenberg Loops, denoted by one asterisk per Loop after eir Influence in the GNDT.

when a Traveller is in one loop e is “out of time”.
when a Traveller is in two loops e is a “rellevarT lamron” (and is not “out of time”).
when a Traveller is in three loops (or more) e has a “melt down” (and is not “out of time” or a “rellevarT lamron”).

2.6.1.1 out of time
when a Traveller is “out of time”:
1)e can not preform “Marching Time”.
2)local proposals have no effect on em.
3)e can not change, create or remove Node Events.
4)e can not vote on local proposals.

2.6.1.2 rellevarT lamron
when a Traveller is a “rellevarT lamron”:
1)upon preforming “Marching Time”, e will move one day backwards instead of one day forward.
2)arrow of time reversed: e is known as rellevarT. see below
3)when posting or commenting, e will write backwards.
example: .sdraekcab etirw lliw e ,gnitnemmoc ro gnitsop nehw(3
this doesn’t includes templates and comments in the gndt.
4)when creating or redescribing a node event in the wiki, the description will be written backwards but the time and the keywords will be written forwards (only the description is effected).

special rules for backward writing:
1)when a proposal that was written backward is enacted, the enacted text will be written backwards.
2)if a rule has two meaning, one when reading forward and another when reading backward, the forward version takes precedence.
3)the voting mechanism is not effected: when voting, the last vote takes precedence.
4)any violation of backward writing will be a chronocrime (see 2.9.4).

2.6.1.3 melt down
when a Traveller has a “melt down”, e can not post or vote exept for voting on a Call for Judgment untill e resolves the melt down (e can post in the gndt or comment in general).

2.6.1.4 melt down resolution
a traveller can resolve a melt down by following all these steps
1)post “DICE3 resolve meltdown” in the gndt.
2)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 nodes containing the travellers name as a keyword are deleted.
the last sentence does not apply to nodes with the [TIME BOMB] keyword.
3)remove all asterisks (Heisenberg Loops) from eir gndt.
(melt down resolved.)

arrow of time reversed: change rule 2.7 to

Subrules of this Rule are known as Local Rules. Their titles may only be of the form “X (Y)” where Y is a Game Date in Standard Form; the date Y is the Local Rule’s Locale. Any non-rellevarT Traveller whose Temporal Location is before a Local Rule’s Locale is not counted as a Traveller for the purposes of that Local Rule. Any rellevarT whose Temporal Location is after a Local Rule’s Locale is not counted as a Traveller for the purposes of that Local Rule.

Local Proposals do not count towards the two-Proposals-pending or three-Proposals-per-day limits, although a Traveller may not submit more than one Local Proposal per real-time day.

Any Proposal with a subject of the form “X (Y)” where Y is a Game Date in Standard Form is called a Local Proposal, and the date Y is the Local Proposal’s Locale. No Traveller may make a Local Proposal with a Locale that is not in eir Range. No non-Arbiter Traveller may vote on a Local Proposal that is not in eir Range. Any Local Proposal which (upon Enactment) would alter any part of the Ruleset, except for the creation or alteration of Local Rules with the same Locale as the Proposal’s Locale, instead has no effect upon Enactment. Any non-rellevarT Traveller whose Temporal Location is before a Local Proposal’s Locale is not counted as a Traveller for the purposes of the Gamestate being updated to include the specified effects of the Proposal. Any rellevarT whose Temporal Location is after a Local Proposal’s Locale is not counted as a Traveller for the purposes of the Gamestate being updated to include the specified effects of the Proposal.

When a Traveller votes on a Local Proposal, e must include eir current TL in the comment containing their vote for their vote to be counted.

When this Rule is Repealed, remove all occurences of “, or the oldest pending non-Local Proposal, ” from the Core Rule “Enactment”.
.
.
.

(the 3 points means that the subrules follow after.)

add a subrule to the The Laws of time:

2.9.4 Don’t Break the Flow of Time
A rellevarT may not break the writing rules in 2.6.1.2 rellevarT lamron.