Another idea for the Time of Unparallelled Darkness
Posted: Sat May 12, 2007 7:56 pm
This was posted in the WotC forums here, so if you've already read that, then there's not much new here. I just wanted to condense the very weird idea I had for a ToUD.
Brief outline:
Azalin could cause something entirely catastrophic for Ravenloft by screwing around with time travel in specific ways. It's well known that you can force time to snap back and forth in a logical loop by doing things that create paradoxes.
I'll go into more detail later, but if you assume a) that Azalin can send things or ideas or information back in time, then it's possible that b) he could influence his past self to do things in a different way that causes time to endlessly repeat itself in Ravenloft.
This would essentially create a closed loop where once the last time unit is used up, the Ravenloft Universe would snap back to where Azalin did his meddling and then progress from there as usual, then reach the end and snap back, repeating ad infinitum.
Plotwise, this fits in well with the idea of a lich who has gotten tired of trying to escape and has decided to break the Universe if he can't leave it. It's also one of the few things I can think of which is actually WORSE news than a Grand Conjunction.
Details:
An example: I go back in time to kill my grandfather before I was ever conceived. This will create a "bow-tie" snap, as the Universe infinitely alternates between two contradictory timelines:
T1: HMB is conceived and born. He grows up, leads a dissolute lifestyle, and then somehow commandeers a time machine in 2007 and goes back in time to 1940, when his grandfather is a young boy. HMB kills his grandfather and does not even think twice of the consequences. (He's a bit stupid that way.) He either uses the time machine to get back to 2007, or he stays in 1940 Taiwan and enjoys the whole Sino-Japanese war thing. It doesn't matter to the timeline - a paradox is born.
T2: The Universe progresses in a different way now. HMB's grandfather never grows up, never marries, and never sires HMB's father. HMB's father never does anything because he never existed. Then, come 1980, HMB is never born. The Universe goes on happily until 2007, when it needs somebody to go back in time to kill HMB's grandfather.
This is impossible now because HMB doesn't exist. Therefore, the relevant date in 2007 comes and goes with no time travel attempt, and HMB's grandfather survives an assassination attempt that was never made.
The Universe snaps back to 1940 as HMB's grandfather lives happily on, siring HMB's father who sires HMB, who goes back in time and ungratefully tops his grandfather. And so on forever alternating between the two contradictory timelines once the Universe reaches the relevant date in 2007.
Very good, HMB, but what's this got to do with the ToUD?
Azalin has already sent people back in time before. He's very careful about it. Consider From the Shadows, where he only sends the PCs' consciousnesses back in time (i.e. nothing material, which is a strict no-no in time travel). He also chooses a time and place where their actions don't disturb too much. They occupy bodies of people who will all die anyway.
Ultimately, when Azalin manipulates time in this way, he limits the possible aftershocks of what his servants do, so nothing contradictory happens.
So far, so good.
But what if Azalin decides to do something to himself in the past? Say Azalin decides to do something very drastic, e.g. prevent himself from ever becoming darklord of Darkon.
This would be very bad. Because Azalin has been darklord of Darkon for very many years and done lots of things, changing something so early and so fundamental means the alternate timeline will be vastly different. Worse still, in order to prevent the altered Universe from snapping back to the point of the contradiction, you'd need an Azalin or somebody else being around in 755 (or whatever the present day is) and being able to send changes back in time to prevent Azalin from becoming darklord!
This is very difficult, however. Imagine my grandfather analogy. Say HMB decides to tell a friend about his plan and asks his friend to use the time machine to send a barrel of lit TNT beside his grandfather's corpse after HMB has killed him.
Apparently, this would seem to prevent a loop, right? HMB kills his grandfather, then a TNT barrel destroys the remains. Then HMB is never born, and the grandfather survives, but then a lit TNT barrel comes through and renders him dead.
However, there is a fatal flaw in this plan. The friend's activities are still dependent on HMB telling him what to do. Thus, if HMB's grandfather died, HMB would never have existed to tell the friend what to do. Thus, we would still be caught in a loop.
As you can see, it is very hard to avoid a loop. The preponderance of the likelihood is that one will occur, and in order to make sure that one doesn't, you have to take special steps.
Now apply this to Azalin. Say in 755 he's feeling upset and decides to send magical energies back in time to 735 and kill his past self for good. (He does something bad to the phylactery and then something bad to his corporeal existence, destroying both.)
This is a classic bow tie snap. Azalin755 casts the spells and Azalin735 dies. Darkon progresses in mourning for the loss of their king for 20 years... whereupon the Universe checks to see if anybody can go back in time to 735 and kill Azalin, and it realizes that nobody can!
So it snaps immediately back to 735, assuming that Azalin735-2 survived the nonexistent assassination attempt by Azalin755-1. This will continue infinitely. If Azalin735-2 then survives to 755, he'll go back in time to kill Azalin of 735, and the pattern repeats again. Ravenloft's Universe timeline would be trapped in a 20-year recurring cycle, never progressing beyond 755 - the year that Azalin Broke Time.
This already constitutes a Pretty Bad Situation. In order to break the cycle and restore the normal flow of time, not only do the PCs need to a) make sure Azalin of 735 is killed, but they must ALSO b) do so before 755 occurs. (Because the timeline snaps back at 755, any plan they might have that extends beyond that point is doomed to fail because it can never be realized before the snap.)
Assuming the PCs have some high level magic, they might be able to time travel too - but they'd have to be very careful because changes they make could automatically cause the pattern to disrupt. Given the best case scenario, they'd have a period of time equal to the difference between the earliest point and the latest point (in this case, roughly 20 years) to plan and execute.
In this scenario, a PC would probably want to enter the timeline shortly after 735, and preferably in the Universe where Azalin survives (but eventually plots to go back in time and kill himself). This is possible if they go to the timeline where Azalin died in the 735 assassination, but they will find it harder as a practical matter to create a situation that would kill him and his phylactery (because both would already be dead - although this is not fatal to an endeavor).
Azalin survives 735 and goes on to do stuff to himself in 755:
PCs should arrive in timeline at 735 and then figure out what's going on. They have 20 years to observe and plan and execute. It doesn't really matter what year they actually execute, as long as it's before the date of 755.
Execution: Go back in time and do whatever Azalin755 does to Azalin735, preferably after 735. (Technically, the PCs could actually go back in time before 735 and kill Azalin, but that introduces potential aftershocks.) They must kill Azalin, and the best way to do it would be to create an unavoidable death trap for him and his phylactery within seconds of the time that Azalin755 would have done so anyway.
That way, it doesn't matter whether Azalin755 exists or not. The task of killing Azalin735 has been accomplished by an outside force, and Azalin 755 is no longer needed to do it.
Time will flow naturally after the PCs destroy Azalin735, all the way to 755, and beyond, because there is no longer a paradox to resolve.
Very late edit: Of course, the PCs could ALSO disrupt the loop by interfering with Azalin755's actions so that Azallin755 never succeeds in manipulating time in the first place. This is much simpler than going back in time and trying to kill Azalin735, but it's an imperfect solution at best. Azalin755 could undertake to interfere with time at any point after 755 if he wants to, starting the whole process over again.[/i]
Brief outline:
Azalin could cause something entirely catastrophic for Ravenloft by screwing around with time travel in specific ways. It's well known that you can force time to snap back and forth in a logical loop by doing things that create paradoxes.
I'll go into more detail later, but if you assume a) that Azalin can send things or ideas or information back in time, then it's possible that b) he could influence his past self to do things in a different way that causes time to endlessly repeat itself in Ravenloft.
This would essentially create a closed loop where once the last time unit is used up, the Ravenloft Universe would snap back to where Azalin did his meddling and then progress from there as usual, then reach the end and snap back, repeating ad infinitum.
Plotwise, this fits in well with the idea of a lich who has gotten tired of trying to escape and has decided to break the Universe if he can't leave it. It's also one of the few things I can think of which is actually WORSE news than a Grand Conjunction.
Details:
An example: I go back in time to kill my grandfather before I was ever conceived. This will create a "bow-tie" snap, as the Universe infinitely alternates between two contradictory timelines:
T1: HMB is conceived and born. He grows up, leads a dissolute lifestyle, and then somehow commandeers a time machine in 2007 and goes back in time to 1940, when his grandfather is a young boy. HMB kills his grandfather and does not even think twice of the consequences. (He's a bit stupid that way.) He either uses the time machine to get back to 2007, or he stays in 1940 Taiwan and enjoys the whole Sino-Japanese war thing. It doesn't matter to the timeline - a paradox is born.
T2: The Universe progresses in a different way now. HMB's grandfather never grows up, never marries, and never sires HMB's father. HMB's father never does anything because he never existed. Then, come 1980, HMB is never born. The Universe goes on happily until 2007, when it needs somebody to go back in time to kill HMB's grandfather.
This is impossible now because HMB doesn't exist. Therefore, the relevant date in 2007 comes and goes with no time travel attempt, and HMB's grandfather survives an assassination attempt that was never made.
The Universe snaps back to 1940 as HMB's grandfather lives happily on, siring HMB's father who sires HMB, who goes back in time and ungratefully tops his grandfather. And so on forever alternating between the two contradictory timelines once the Universe reaches the relevant date in 2007.
Very good, HMB, but what's this got to do with the ToUD?
Azalin has already sent people back in time before. He's very careful about it. Consider From the Shadows, where he only sends the PCs' consciousnesses back in time (i.e. nothing material, which is a strict no-no in time travel). He also chooses a time and place where their actions don't disturb too much. They occupy bodies of people who will all die anyway.
Ultimately, when Azalin manipulates time in this way, he limits the possible aftershocks of what his servants do, so nothing contradictory happens.
So far, so good.
But what if Azalin decides to do something to himself in the past? Say Azalin decides to do something very drastic, e.g. prevent himself from ever becoming darklord of Darkon.
This would be very bad. Because Azalin has been darklord of Darkon for very many years and done lots of things, changing something so early and so fundamental means the alternate timeline will be vastly different. Worse still, in order to prevent the altered Universe from snapping back to the point of the contradiction, you'd need an Azalin or somebody else being around in 755 (or whatever the present day is) and being able to send changes back in time to prevent Azalin from becoming darklord!
This is very difficult, however. Imagine my grandfather analogy. Say HMB decides to tell a friend about his plan and asks his friend to use the time machine to send a barrel of lit TNT beside his grandfather's corpse after HMB has killed him.
Apparently, this would seem to prevent a loop, right? HMB kills his grandfather, then a TNT barrel destroys the remains. Then HMB is never born, and the grandfather survives, but then a lit TNT barrel comes through and renders him dead.
However, there is a fatal flaw in this plan. The friend's activities are still dependent on HMB telling him what to do. Thus, if HMB's grandfather died, HMB would never have existed to tell the friend what to do. Thus, we would still be caught in a loop.
As you can see, it is very hard to avoid a loop. The preponderance of the likelihood is that one will occur, and in order to make sure that one doesn't, you have to take special steps.
Now apply this to Azalin. Say in 755 he's feeling upset and decides to send magical energies back in time to 735 and kill his past self for good. (He does something bad to the phylactery and then something bad to his corporeal existence, destroying both.)
This is a classic bow tie snap. Azalin755 casts the spells and Azalin735 dies. Darkon progresses in mourning for the loss of their king for 20 years... whereupon the Universe checks to see if anybody can go back in time to 735 and kill Azalin, and it realizes that nobody can!
So it snaps immediately back to 735, assuming that Azalin735-2 survived the nonexistent assassination attempt by Azalin755-1. This will continue infinitely. If Azalin735-2 then survives to 755, he'll go back in time to kill Azalin of 735, and the pattern repeats again. Ravenloft's Universe timeline would be trapped in a 20-year recurring cycle, never progressing beyond 755 - the year that Azalin Broke Time.
This already constitutes a Pretty Bad Situation. In order to break the cycle and restore the normal flow of time, not only do the PCs need to a) make sure Azalin of 735 is killed, but they must ALSO b) do so before 755 occurs. (Because the timeline snaps back at 755, any plan they might have that extends beyond that point is doomed to fail because it can never be realized before the snap.)
Assuming the PCs have some high level magic, they might be able to time travel too - but they'd have to be very careful because changes they make could automatically cause the pattern to disrupt. Given the best case scenario, they'd have a period of time equal to the difference between the earliest point and the latest point (in this case, roughly 20 years) to plan and execute.
In this scenario, a PC would probably want to enter the timeline shortly after 735, and preferably in the Universe where Azalin survives (but eventually plots to go back in time and kill himself). This is possible if they go to the timeline where Azalin died in the 735 assassination, but they will find it harder as a practical matter to create a situation that would kill him and his phylactery (because both would already be dead - although this is not fatal to an endeavor).
Azalin survives 735 and goes on to do stuff to himself in 755:
PCs should arrive in timeline at 735 and then figure out what's going on. They have 20 years to observe and plan and execute. It doesn't really matter what year they actually execute, as long as it's before the date of 755.
Execution: Go back in time and do whatever Azalin755 does to Azalin735, preferably after 735. (Technically, the PCs could actually go back in time before 735 and kill Azalin, but that introduces potential aftershocks.) They must kill Azalin, and the best way to do it would be to create an unavoidable death trap for him and his phylactery within seconds of the time that Azalin755 would have done so anyway.
That way, it doesn't matter whether Azalin755 exists or not. The task of killing Azalin735 has been accomplished by an outside force, and Azalin 755 is no longer needed to do it.
Time will flow naturally after the PCs destroy Azalin735, all the way to 755, and beyond, because there is no longer a paradox to resolve.
Very late edit: Of course, the PCs could ALSO disrupt the loop by interfering with Azalin755's actions so that Azallin755 never succeeds in manipulating time in the first place. This is much simpler than going back in time and trying to kill Azalin735, but it's an imperfect solution at best. Azalin755 could undertake to interfere with time at any point after 755 if he wants to, starting the whole process over again.[/i]