The Lost

There be Ranik in them Halls!
Lions and tigers and zombified human populations!

Drone Assistant Action Log::

0600. Briefing: Rundown on the details of the Planet Randos 1 and the mission.
Fire Team Alpha to enter Capital city, identify conditions, secure the CDC, and establish base camp.
Fire Team Bravo to enter the second city, identify conditions, and establish a base camp.
Fire Team Charlie remains on standby to support either team in case of trouble.
Fire Team Delta remains to assist in post mission damage control, medical assistance, and base camp security.

0800. Disembark: Fire Teams Alpha and Bravo make their way to the surface. Nothing gets in their way at first, but hostilities quickly ramp up as the infected population has been found animate, but aggressive. Both city remains mostly intact, but in disrepair. * * * * * CLASSIFIED DETAILS * * * * *

0847. Alpha is blocked from the CDC and Charlie — 2 is called to secure the CDC from the inside while the rest of Charlie is called to clear out and secure the surrounding area, then enter.

0850. Charlie — 2 is under way. Make it to LZ with minimal conflict. The trip proves to be more than you can handle. You vomit and feint during drop (appropriate drugs will be added to the gear list for future hot drops). 12 hostiles are detected on the roof entrance. You awaken shortly after drop off. The hostiles are dealt with and Velt blows a whole in the cargo lift. She is bit in the process and Mercer tends to her wounds.

Meanwhile, drop ship Charlie — 2 is successful in neutralizing the AA system and Drone defense system to open the way for the rest of the Charlie Team drop ships. The port side thruster gyro stabilizers and outer haul thermal regulator sensors are damaged and will need refitting and calibration. Redundant systems are activated and function normally.

0858. The team is in the lift shaft on the main floor. Explosives are used to clear out the plethora of hostiles on the other side of the lift doors. A plan is laid out to secure the floor and move toward the lower levels. * * * * * CLASSIFIED DETAILS * * * * *
— Snake Camera added to shopping list.

View
"The Beast" Journal Entries
The beginning of awesome

Journal

Day 1 (Feb 27):
Today I arrived on the TPC Watermark to report for duty and met my commanding officer and team. After receiving all of our squad and bunk assignments, we got an order to report tomorrow for some training and evaluation with our team. Should be fun.

Day 2 (Feb 28):
Morning Entry:
Got ready early because I want to make sure I am there a little early. I am interested in seeing how the rest of the team performs today. Should make for an interesting day.

Evening Entry:
F**k that was rough. This “Jules” guy decided to go f**king rouge and ambush his own team. It pisses me off how someone who I’m supposed to be able to work with and is supposed to have my back could do something like this. He says that where he came from he had a hard time following orders and working on a team or some crap, and that he wants to be able to work with us, but he is off to a pretty awful start.

Day 3 (March 1):
Morning Entry:
After sleeping, I feel a bit more calm concerning yesterday. I hope we can get Jules working with our team before we actually have to go on a mission. The press will be here today, so hopefully I can get some camera time. I’ve gotta let people see how awesome I am.

Evening Entry:
Today was great. I think I nailed my interviews and I’m sure they’re gonna use the footage of me, I mean how could they not. We are now on our way, and I can hardly wait to get some action.

Day 8 (March 6):
They did the whole super warp thing and people blacked out for a few seconds. I of course did not, so I’m not sure what people are talking about, but I guess everyone is all worried about it.

Day 12 (March 10):
Was at the gym having some fun and saw a chick doing some impressive stuff on the obstacle course. The screen only gave her name, but I think I saw her with Commander Drake, so maybe she is his bodyguard or something. She new about me because of how awesome I was at the obstacle course and she suggested that we set up obstacle courses for each other each week and have some fun. I agreed.

Day 18 (March 16):
I have my obstacle course set up, and have run it a few times. I think she’ll have a hard time with it, even though it is pretty easy. It starts out with a mile run down hill then a 200 foot high slippery wall with about 450 feet of slippery monkey bars 20 ft apart, that should be difficult for her. Then there is a 200 foot drop, so not too bad, then a slight run to a 30 foot jump to end it. Tomorrow should be fun.

Day 19 (March 17):
Morning Entry:
Today should be fun, I finally get to run my obstacle course against Kari. I’m totally going to beat her.

Evening Entry:
I beat her with my time of 3:33 and her time of 4:09. She did a lot better than I thought and had some tricks up her sleeves, like an internal jet pack system. She jumped across the monkey bars, which I wasn’t expecting, but it was a good move on her part. She took a hard fall on the 200 foot drop, so I’ve got to give her props for that, looked like it hurt a lot.

Day 26 (March 24):
Morning Entry:
Going to run Kari’s course today. I imagine that it is going to be smaller and more agility based, because that seemed to be more of her style. I think I’ll still be able to beat her though.

Evening Entry:
Well crap, she barely beat me. She got 0:48 to my 1:03. I think if I keep on running this course, I can beat her time though. She started off with about 9 15 foot walls about 10 feet apart. Not sure what she was thinking with those, but we both just jumped across the tops of them. Then she had a 110 foot wall that I climbed up with ease, but she jumped with her jet-pack thing to a rope that was hanging from the top and her arm spun and took her up the rope. Then she had a 130 foot flaming hallway. I didn’t think about the lack of air, so I had some trouble breathing in there. Then a flaming beam fell on me, which hurt a bit, but wasn’t too bad. Coming out of that hallway, I was hurt pretty bad from the heat and the beam, but I wasn’t about to give up. Then she had a 200 foot zip line that we had to go down while being shot at. I used the mechanism that was there, but it slowed me down, and she used her retractable spikes to go down it faster than me. We were both able to dodge the bullets. At the end, we had to take out a test dummy before crossing the finish line. I got it with two swings of my sword, but she just ran into the thing twice and got it with some arm blades. She also seemed to have some sort of weird energy field around her. We are going to be running these obstacle courses every week. This might be the best part of this whole trip.

View
It's personal...
Don't take it personally.

Dexter Burton

Personal Robotic Assistant:

Your log of the day, Mr. Burton:

Unusual Events:
  1. Request from Sub Captain Sillian to discuss programming and meeting with Captain Glazov
  2. Warp Gate and Gravidic Drive Combination Incidents
Summery of Event One:

Sub Captain Sillian wants to create a program that will take sensor and logistical information about a mission and its current and projected conditions, apply information about the team (Fire Team: Charlie 2; at this time, you are informed that there is a new member to the team and that you should have received a memo, but you did not), and extrapolate the appropriate supplies needed for the mission, then activate the Personal Robotic Assistant (PRA) fleet to prepare the gear in the hanger next to the appropriate drop ship for the team. You inform him that it will take you but minutes to create such a program. He asks that he first get permission from Captain Glazov. You radio Glazov for permission and get it, and also set up a meeting with him for 45 minutes later {time stamp} in the main quart to discuss the program. You complete the program and give it a final test before the meeting. The PRA fleet perform the task in the appropriate time with few glitches {listed here}. You do what you can to fix the glitches while on your way to meet Glazov and Sillian in the main refreshment quart. You show up 20 seconds early. You present your program and discuss any changes with the others {discussion record}. You also discuss room changes. Glazov also informs you that there is a new member to the team and also asks if you got the memo: you did not. [New Task: check to make sure you made it onto the mailing list for the fire team].

Summery of Event Two:

You complete a full diagnostic of the sensor systems in preparation for the warp gate and Gravidic drive test. You run several simulations for the event. Once in the gate, you get an order from Commander Drake to run a diagnostic and calibration of all sensor systems before activating the gravidic drive. You do so and run an additional simulation with 3 minutes 16 seconds to spare. After the Drive starts, you are seemingly incoherent for approximately 3 seconds directly after the drive initiates. once you regain consciousness, you inspect all the data coming in from departments all over the ship and all the various sensors. You form several theories about why the people blacked out for 3 seconds but none of the computer systems where effected and why the warp tunnel walls “constricted.” You come to no solid conclusions. After pacing for several hours working out details and testing mathematical models, you and the others on the team decided that more data is needed before any theory can be made. You prepare for the exiting of the warp by aligning sensors to look more at the subspace walls of the warp tunnel and programming them to a smaller band width at higher sample rates. This time, there are no personnel black outs and the walls of the tunnel “expand” for a moment.
After the ships have completed the transfer of personnel, the Water Mark proceeds to the next warp gate. Several test subjects are placed into various combinations of shieldings (i.e. grave shield, Electromagnetic shielding, proton shielding, and ionizing radiation shielding) and sensors (i.e. MRI scanners). Those in the combination of gravidic and electromagnetic shields were unaffected by the phenomenon. Also, a report that a deaf man (born without an inner ear) was only partially affected. You and your team come up with ways to modify the shields to protect the people from the black outs.

Personal Entry:

There is not much that bother’s me… People, on the other hand, bother me much. I’m none too happy about the actions of Jules back on earth for our “training” exercise, I was even more upset with the decision to keep him on for the mission. Knowing that in combat team mates need to depend on each other, I will now go out of my way to prepare for Jules not being dependable.
After Jules, Captain Glazov makes me the most uncomfortable. His lack of understanding of modern technology means that I will likely have to explain a few novice things that even non-techies know. That in addition to his more battle like approach to situations: “Just go do it, don’t stop to think.”
The only other person to make an impression on me so far is Sub Captain Sillian. Truth be told, I will keep my distance from this eccentric and over analyzing outer colonist, but Sillian actually has come up with some interesting ideas… so long as they do not interfere with my current living conditions I am alright with him… just a little annoyed with his inabilities to efficiently communicate.
Personnel issues aside, I am very excited about this mission. Already I have been able to dive deep into unknown phenomenon and theoretical sciences. The time I get to tinker with things is more than I could ask for. From ships to small gadgets, I can find myself consumed in technology and programming. The “warp gate” incidents have given me a great deal of information to theorize about and test. The Gravidic/Electromagnetic test proved very useful, but the phenomenon is still not understood and shielding increase for the whole ship would probably ruin data collection from the sensors. This compels me to urge against shielding the whole ship, but instead set up areas in the ship that are protected for the moment needed.
After the “reaction drills,” I take the opportunity to get to know the newest member of the team, Connie Velt. I is interested in talking about explosives, one of my newer fields of study.

View
T: -12hrs
What happened on Earth, stays on Earth

As the Water Mark is warming up for pre-flight (the longest pre-flight known to man) most of the crew is enjoying their last day before an indefinite mission. That is, except for Fire Team: Charlie-2. They are summoned by their fire teams captain, Glazove, to show up at a meat and shoot on Earth. Glazove must have still had some of his brain still in deep freeze when givnig that order. No one was happy to give their last few hours before disembarking for God knows how long! Everyone shows up, most of them on time, except Jewels. He is reported as logged in, but cannot be found. The lieutenant, Silias, goes to look for him, but ends up missing himself. Glazove takes advantage of the situation and tells his people to start looking for for the renegade and the lieutenant. oh, and this AWOL Defiant colonist happens to be an assassin. Using war game tech and baiting the rest of his team into taking a specific rout, Jewels manages to get Glazove in the neck with a sniper shot. He then gives him self up in light of the mass of robots bearing down on his now revealed location, complements “The Beast” on his staying power, and explains his disapproval with the command and his desire to not be on the Water Mark mission. Glozove cares little for Jewel’s lament and is concerned with the illegal approach, especially tampering with the groups equipment (a Mecha) while it was under lock and key. The group gets a few drinks together. Some then head to Europe to enjoy some tourism, while others get back to the ship. During all of this, the GIB keeps a close eye on the situation from above…

View
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.

View

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.