Quote:
Originally Posted by Darekun
While it is perfectly logical* to think it would open a can of worms, that's the same logic that replaces DelayedRippleEffect with alternate universes.
|
Well, not exactly. The way Delayed Ripples work in this universe is that they force an Isolated (suited) character (or one with Temporal Inertia, if it matters) to spontaneously 'move' from the Original timeline to the Altered one (without moving forward or backward in time).
Quote:
Originally Posted by Darekun
The whole logic of DelayedRippleEffect is that there is only one time line, and at the end of the movie there is only one causal chain. (And it kind of imports SanDimasTime by reference.) |
Not necessarily one timeline (see above).
Quote:
Originally Posted by Darekun
Within the logic of DelayedRippleEffect, I think the last change(as measured in SanDimasTime) wipes out all others.
|
Sort of yes, but not quite. If character jumps from +0 to -5, changes something, returns to +0, lives on to +1 for the changes to catch up, jumps to -7, returns to +1, waits to +2, then the changes of -5 and -7 are combined (s/he can't jump twice to -5 anyway).
At this point, while irrelevant for the module, it seems that I should demand that a suit should remain sealed all the time in the past
and, upon returning to the 'future'/'present' (the initial departure point)
until all his Ripples catch up with him.
Quote:
Originally Posted by Darekun
If that means traveler at risk, then as the page says, looks like it's going to be a RaceAgainstTheClock to SetRightWhatOnceWentWrong(or at least, someone needs to retrace someone else's steps).
|
Assuming the suits stay sealed, traveler will not be at risk (unless the altered timeline is deadly to him once it catches up, such as if actions in the past result in there being a fire in the future/present where the traveler is when the ripple catches up). The world, however,
is at risk - from the PoV of the traveler anyway.