Well seeing as the game hasn't even started yet, and all this is is backstory, I doubt us continually saying:

is going to really change how much exposition he's going to give us. I could be wrong! But I don't think he'll sacrifice backstory/exposition just because I'm saying to just let him do his thing.

Just cut to the chase and do
>Remember backstory, recant to invisible nonexistent audience.

I think we should read everything we come across, so that we can be prepared for something for a change.

Anyone wondering why this is going so slow, it's because of a few things.
1. I am taking a short reprieve from RtD.
2. I'm waiting for some other story stuff to conclude
3. I'm a lazy bastard
4. I'm goddamn sick as hell
5. Got a shitload of primarily school related IRL stuff to deal with
So yeah.

Thus why we let Hyper do his thing. He'll present them in due time. Hyper, after what you just did, if we ♥♥♥♥♥ at you, we need to be punched in the collective testicles/ovaries.

I'm so pumped for some hardcore mecha action.

*sigh*

I never said he'd sacrifice any, but perhaps you'll get useful information or background facts. The limit is his imagination; as a practiced gm, he is liable to have fairly high limits.

>RUN COOFAC.TXT

Not COOLFAC.

How about

Since that's the only thing that seems relevant to this story.
("The White Blur" is Fiona's Mech if you didn't know already.)

Let's open these directories alphabetically, shall we?

WAIT is not a command we should be using, we're not building a program.

@Yoman: I think that COOFAC.TXT is the backstory for this, and it's not like this is actual updating, hyper could just stop doing this farce and give us all the info, but dragging this out will be good for him as it means he is resting more from his year long adventure.

It's only so we have time to read the thing before the next action.