Author Topic: The Month That Could Have Been -- Chapter 17  (Read 4219 times)

Mikisho

  • Guardian (+100)
  • *
  • Posts: 196
  • The Future Refused to Change. We Said Screw You.
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #30 on: June 14, 2009, 08:57:18 pm »
Spoiler video un privated >_> possibly been fixed by the time I post here.

Acacia Sgt

  • Radical Dreamer (+2000)
  • *
  • Posts: 2430
  • Forever loyal to the Acacia Dragoons
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #31 on: June 14, 2009, 09:01:20 pm »
Must... not... watch it...

Anyway, I'm serious, I will wait for when it's time to.

FaustWolf

  • Guru of Time Emeritus
  • Arbiter (+8000)
  • *
  • Posts: 8974
  • Fan Power Advocate
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #32 on: June 14, 2009, 09:06:38 pm »
Eheh...fixed now. :D Just wait till you guys see the final boss, designed especially for the occasion by Darkken.

Mikisho

  • Guardian (+100)
  • *
  • Posts: 196
  • The Future Refused to Change. We Said Screw You.
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #33 on: June 14, 2009, 09:50:09 pm »
Who is the final boss anyway?  I can't see it being King Zeal...  I mean, it could be...  But I would much rather have a lavos type boss.  or maybe you somehow imported the DD from CT:DS, put it on Crimson Echoes, and then replaced Schala with King zeal.... *Drool*....  Oh well, I'm looking forward to it.  We're only 5 days away....  I'm excited....  You sure you don't want to release the next chapter early?

Schala Zeal

  • Radical Dreamer (+2000)
  • *
  • Posts: 2092
  • 7th Elemental Innate
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #34 on: June 15, 2009, 12:56:28 am »
Kind of like the confrontations that LoD characters have.

Miranda faces her mother in venus flytrap form
Haschel faces his daughter possessed by the God of War
Rose faces her dragon Michael
Kongol faces his brother Indora
Albert faces his uncle Emperor Doel
Meru faces the Archangel of the winglies

FaustWolf

  • Guru of Time Emeritus
  • Arbiter (+8000)
  • *
  • Posts: 8974
  • Fan Power Advocate
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #35 on: June 15, 2009, 03:47:04 pm »
Even in its late beta version, the last boss should satisfy a wide range of fans. It's really special. Hahaha, and the beta testers are thinking they're going to see the repaletted mask again...ohohohoh.

RySenkari

  • Guardian (+100)
  • *
  • Posts: 156
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #36 on: June 15, 2009, 05:32:35 pm »
Quote
Even in its late beta version, the last boss should satisfy a wide range of fans. It's really special. Hahaha, and the beta testers are thinking they're going to see the repaletted mask again...ohohohoh.

Thank god you guys changed the final boss from what it was.

This is another reason not to play the alpha. Final boss of the alpha was lame.

IAmSerge

  • Temporal Warrior (+900)
  • *
  • Posts: 964
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #37 on: June 15, 2009, 05:38:38 pm »
Lynx, Serge, Fate, Schala, TD, DD, Lavos, KZ, QZ, Magus, Belthasar, Kasmir, Dalton...

Pick one! any one! =D

Actually I haz no idea what it will be, so... maybe even an incarnation of the flame itself?

Trissum

  • Iokan (+1)
  • *
  • Posts: 1
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #38 on: June 15, 2009, 06:34:16 pm »
The final boss is Kino.

When the Gigasaurs cornered him on the hill, Kino realized his latent powers that stemmed from his mysterious origins and vaporized both of them. By then, Ayla had already fled, so she didn't realize. He was about to follow, but tripped over a rock on the cliff and fell down, landing in the sea. Days later, he washed up to shore, with no memories. He was found by a prehistoric aardvark who cared for him over the next few days, until he was strong enough to go find his memories again.

Upon setting out into the mountains to the east of Singing Mountain, he came upon an advanced version Time Egg which had been dropped by a time traveler from 19,205 AD - by then every biological being had been integrated into FATE in this Keystone timeline. FATE from 19,205 AD altered the mechanics of this Egg slightly so that when Kino touched it, he would be transported to 15,000 AD to be used by FATE to prevent an incident involving certain highly powerful artifacts under the control of DESTINY, a rival computer of temporal control constructed by FATE's opponents in that era in a subplot entirely irrelevant to the Chrono series. However, under this timeline, due to certain actions of Kino, he caused a young time traveler from 15,000 AD to go back in time and accidentally prevent the Prometheus Circuit from being destroyed and in fact causing it to exercise far greater restraint over FATE, thus causing DESTINY to destroy FATE in 15,001 AD.

To reward Kino, DESTINY grants him one wish, which the computer would be able to grant due to its unrestricted hegemony over all of time-space now. Kino wants to regain his memories, and so DESTINY alters the timeline so that Kino does not hit is head upon falling off the cliff, then creates a gate to 15,001 AD where he fell - this new version of Kino succeeds the old one by TB. Having regained his memories, Kino asks DESTINY to return him to his own time, but DESTINY refuses. Kino is enraged, but pretends that he is only mildly disappointed.

Over the next decade, Kino begins a human resistance against DESTINY's rule, culminating in the use of background radiation from the very edge of the observable universe to disrupt DESTINY's time-probing abilities - in the resulting confusion, the last aspect of the computer's interface is destroyed, and all copies are corrupted. With DESTINY out of the way, Kino's resistance breaks into the central physical fortress of the humans under DESTINY's sway and help him use the time machine to return to his time.

Needless to say, he discovers he no longer can live comfortably in such a primitive environment after only a week in the southern village he arrived at, and so becomes angry and bitter at the world. He decides to wander as a hermit for the rest of his life - but when he goes to the mountain where he was found as a child, he discovers a gate. When he goes through it, he discovers his origin - he was a lost child from a futuristic Zeal-esque society imbued with natural magic, kidnapped and placed there by the computer which replaces DESTINY in 20,000 AD - ANOTHERPSEUDOSYNONYMOFDETERMINISTICFUTURE simply so that he could engineer both FATE and DESTINY's downfall, giving ANOTHERPSEUDOSYNONYMOFDETERMINISTICFUTURE complete rule over space-time. Knowing now that all his life he has been a pawn, he begins discreetly gathering power and building supercomputers of his own. When he senses the disturbance to the Frozen Flame resulting from the events you have seen in Crimson Echoes, he travels there using the incomprehensibly advanced technology he has developed using his inhuman skills, replaces the Frozen Flame with a copy, and steals the real Frozen Flame to further increase his own power.

He does similar things with other sources of magical energy throughout time, until ANOTHERPSEUDOSYNONYMOFDETERMINISTICFUTURE becomes aware of him. It sends agents to destroy him or erase him from the timeline, but he has become immune to all such aspects of space-time - his very existence is outside of time now. He still can be killed like a mortal - he has not subverted that weakness yet, but magic is harmless against him, and his technological wonders easily can destroy any would-be assassins. Kino himself appears in 20,000 AD and destroys ANOTHERPSEUDOSYNONYMOFDETERMINISTICFUTURE - "travels to" would have been an incorrect term, as he is outside the timeline.

Finally, he decides to confront the party, his once-friends, in Chronopolis: He wants to make them suffer for everything that he has gone through. He then plans to destroy all of space-time. He does not realize they had nothing to do with it; he is half-crazed, inhuman now. He appears in Chronopolis and using his god-like powers, makes the entire party and everyone present writhe in agony.

But then, he accidentally trips and falls into the ocean, and drowns from sheer surprise that he could still trip. Everything he ever did and every effect he had on the timeline is erased due to the fact that he had removed himself from the timeline.

Yourgingerestfan

  • CC:DBT Dream Team
  • Magical Dreamer (+1250)
  • *
  • Posts: 1403
  • im ginger ....your ginger ....were all ginger !
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #39 on: June 15, 2009, 06:58:25 pm »
Umm ..if this is true .....thanks for spoiling >.> (sarcasm)
If not congratulations you have great imagination !

FaustWolf

  • Guru of Time Emeritus
  • Arbiter (+8000)
  • *
  • Posts: 8974
  • Fan Power Advocate
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #40 on: June 15, 2009, 10:02:35 pm »
Damn it Trissum, why didn't you just go all the way and spoil the fact that Kino merges with Alfador to create the last boss, SupahCat!?  :lol:

Yeah Ry, the last boss of CE is one for the ages, methinks.

Mikisho

  • Guardian (+100)
  • *
  • Posts: 196
  • The Future Refused to Change. We Said Screw You.
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #41 on: June 18, 2009, 02:42:25 am »
Great, now you got my hopes all up and high.  This boss better be phenomenal...  I predict that it will be Schala Holding the frozen flame.  Just because apparently it is a different boss from the Alpha.  I assume in the Alpha the decision had not been made to put Ayla back in as a playable character, as they would still be planning to put Schala in.  However, when they decided to put Ayla back in as a PC, they couldn't just get rid of Schala.  They decided that they would tie up the loose ends and show us how she merged with the DD to create the TD we all know and love.  She's already been sent to the DBT, and that is where You know who, and you know what forced theirway into...  I'm calling it now.  Schala and the frozen flame.

RySenkari

  • Guardian (+100)
  • *
  • Posts: 156
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #42 on: June 18, 2009, 02:46:10 am »
At the risk of getting chewed out for playing the alpha, Ayla was playable in the alpha.

Mikisho

  • Guardian (+100)
  • *
  • Posts: 196
  • The Future Refused to Change. We Said Screw You.
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #43 on: June 18, 2009, 02:58:09 am »
I'm not gonna lie, I have it too >_>...  Though I'm trying to keep it on the DL <_<....  shhh....  But it doesn't matter, that just means they hadn't gotten around to implementing Schala yet...  IT WILL HAPPEN!!!...  Also, earlier were you saying that you BEAT the Alpha?  What about the game stopping glitches I've heard about?

RySenkari

  • Guardian (+100)
  • *
  • Posts: 156
    • View Profile
Re: The Month That Could Have Been -- Chapter 17
« Reply #44 on: June 18, 2009, 03:34:14 am »
I've beaten the original game hundreds of times, I have in and out knowledge of work-arounds and such that I was able to apply to my playthrough of the alpha to get around the show-stopping bugs. Plus, I kept several save files I could use to go back and forth every time I screwed up. Playing the alpha does give you an appreciation of how much work the guys did to get to the 98% stage, though I can't bring myself to play the thing anymore now that I've seen the real deal :(