The Day Bandit and the Aliens of Space

Turn Three

Rick shakes his head. “I can’t make head or tail of this, Doc. What’d you do to make it print out all this stuff? Is it some kind of transmission from one of these planets?”

Furgee moves back to the pilots area. “OK, before we can think about investigating this area, lets cut the main engines.” He fiddles with the pilot controls to try and deactivate the engines. “Ivy, how long will it be before we can safely leave the bridge? I need to get started on repairs ASAP.”

Tan looks at Furgee “Fix with what exactly? We have no components and no tools, and although I can’t check I’m willing to guess that most of our spare parts, if indeed we had any, were in the cargo bay.” After saying that somewhat haughtily he turn to look at Rick. “It’s not a tranmission, seems that our chief engineers, who’s logs there are. Was not a human and kept his logs in his native tongue. I can’t say I even remember who he was, don’t think I ever met the man.” He strokes his chin for a second in thought before moving over to the console Rick is at and starts using it in an attempt to access the personnel records “I might be able to narrow it down though, should be some records of where he came from at least. Maybe even some medical records”

“I’m sorry,” says Ivy, pelasently, rather too loud now that the hum of the engines has died away”, crew records aren’t available to non-officers at the current time.” “It is now safe to leave the bridge. ETA on cargo hold repairs is four hours, with medical bay access expected within the next two to three days. May I be of any further assistance?”

Turn Two

Tan looks at Furgee suspiciously as he speaks before replying “Did you say Morin friends, what do you know of them?” he then shakes his head as if deciding to forget it and looks back at the console.

Furgee gets out of the pilots chair, answering Dr. Lawrence as he does so. “Spare me the back-seat piloting will ya, we made it away and hopefully they won’t have a clue where we ended up. After all, WE don’t have a clue where we’ve ended up!” He starts scanning computer screens to try and get a handle on what needs to be done. “Hey Ivy, we got any working scanners left? If we have, better let us know what’s in the area.”

Dr. Lawrence tuts at the unknown language the computer spews back at him although he squints slightly as if he vaugely recognises it. “Well this is useless, anyone know how to speak gibberish?” he taps at the computer screen in disgust. “Great the jump drive is down, looks like we might be here for a while lads. May as check what’s out there at the very least to make sure we’re not about to fly into anything.” Tan risks another glare at Furgee as he says this moving to the sensors console and trying to work out where they are and what is near by.

“Hey I think we all just need to calm down,” Rick says, moving over to Dr. Lawrence. “Is the computer’s talking in a different language?” he asks, activating the Language program in his wafer jack. “What’s that all about?”

After a few minutes, Ivy responds,

“Sensors suggest that we’ve left known space, and whilst no definite information can be found there appear to be systems capable of supporting life at 47, 88, and 256 degrees of our current position.”

Turn One

Furgee starts unstrapping himself.

“Who were those guys, more friends of yours Doc?”

He carries on without waiting for an answer.

“Stay on the computers doc, lets us know whats still working, Rick and I shuold try and figure a safe way out of here. Sooner we can get to a locker and get me suited and booted sooner I can start saving our butts.”

Tan glares at Furgee and starts tapping at one of the consoles on the bridge attempting to help Ivy run it’s damage report tests, as well as trying to bring up the logs to find out what the hell is going on. “I told you to take a left at the red moon, Mr Furgurson! A left! Then we would have been able to evade them without needing to jump!”

Meanwhile, Rick looks at the others in confusion, the post-stasis fog not having completely worn off yet. “Where are we now, Ivy? Are we safe at least?”

Ivy’s response is not a reassuring one. “I’m really not sure, Rick. My navigational subsystem’s seem to be broken.”

“Damage reports indicate serious structural damage to the jump drive, cargo holds, and the medical centre, however auto-repair systems should ahve sealed off most of the damage elsewhere and access to all areas of the ship not locked down will be avaialable shortly. “

The Beggining

With a stomach-churning lurch, the Day Bandit ends a jump. Red lights and flashing sirens slowly subside as Ivy calls for everyone to be calm in the most reassuring manner possible, “Attention. Major structural damage recorded. Please do not panic. Repair assesment is underway. Leaving of the bridge is not advised due to high risk of explosive decompression. Thank you for your assistance.”

Welcome to your Adventure Log!
A blog for your campaign

Every campaign gets an Adventure Log, a blog for your adventures!

While the wiki is great for organizing your campaign world, it’s not the best way to chronicle your adventures. For that purpose, you need a blog!

The Adventure Log will allow you to chronologically order the happenings of your campaign. It serves as the record of what has passed. After each gaming session, come to the Adventure Log and write up what happened. In time, it will grow into a great story!

Best of all, each Adventure Log post is also a wiki page! You can link back and forth with your wiki, characters, and so forth as you wish.

One final tip: Before you jump in and try to write up the entire history for your campaign, take a deep breath. Rather than spending days writing and getting exhausted, I would suggest writing a quick “Story So Far” with only a summary. Then, get back to gaming! Grow your Adventure Log over time, rather than all at once.


I'm sorry, but we no longer support this web browser. Please upgrade your browser or install Chrome or Firefox to enjoy the full functionality of this site.