Topic: Star Trek: The Cassius Incident Q&A Subject: well...
I will probably go ahead and post again. I've PMed Ody to let him know that he can backpost to catch up.
Posted on 2012-10-26 at 04:07:08.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: psh
Don't be silly. Mac drinks coffee, not lattes.
Posted on 2012-10-25 at 20:03:40.
|
Topic: Voyages of the Rocinante - Firefly RPG QnA Subject: whatevah...
Rociante has been a rock star for too long. Trek is getting some new girl on the block love, but this baby is going nowhere.
Posted on 2012-10-25 at 19:38:20.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: ^^^^^^
Exactly what Eol just said. Don't sweat the details of deck locations, names for thingamajigs, etc. We're HAPPY to help you with that stuff.
Worry about your character's personality and how they react to situations, and you'll be fine.
But post!
Posted on 2012-10-25 at 13:50:40.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: thing is...
...it's easy (especially with some of the amazing players in this game) to worry so much about crafting the perfect character, the perfect post, the perfet reactions... that the game just loses the fun. It becomes a chore.
Then, you get to where you don't want to post, you lag behind, then you start to feel overwhelmed at everything going on.
Keep it simple. Where is your character when the floor starts swinging around like crazy? What does she think about it? What does she do?
That's all there is to it.
If you want to expand on this, nobody will argue. If you feel like bringing in an NPC or two, go for it. But don't feel like you have to do those things - just cover the basics, let your character's personality show through, an the rest will take care of itself.
edit: tons of typos, even for me
Posted on 2012-10-25 at 03:42:37.
Edited on 2012-10-25 at 13:23:52 by t_catt11
|
Topic: Star Trek: The Cassius Incident Q&A Subject: psh
No worries.
And don't worry about being perfect! Just post.
Posted on 2012-10-25 at 03:32:04.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: nope
It's a timestamp error. Alacrity's post clearly leads into the hits on the Discovery. I'm betting he did a cipy/paste on the date part just to get the header format, then overlooked editing the time.
Posted on 2012-10-25 at 03:28:50.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: outstanding
Two of the best color guys in the game **AND** a Zombies reference? Priceless.
Posted on 2012-10-25 at 03:25:32.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: excellent
Excellent first round of posts so far. This is exactly what I was hoping for. Seeing the events through various eyes, getting the "people" feel of things... perfect.
I of course don't want to rush things; though I'd like to post again, I will give everyone a good chance to mke their own posts, first.
Posted on 2012-10-24 at 23:03:42.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: yep
You have the gist of it. Alpha shift, weekdays, is when your senior staff would usually be at their primary spot (bridge, sickbay, etc). Of course, being a department head means that you probably do work long hours.
With that being said, there are many times when this may not apply; MacTavish might have a junior officer on the bridge while he works in his office, performs inspections, etc. If we're simply puttering along between star systems, Captain Blair may well be in his ready room as opposed to sitting in the big chair. And so on.
Posted on 2012-10-24 at 22:30:30.
Edited on 2012-10-24 at 22:31:20 by t_catt11
|
Topic: Star Trek: The Cassius Incident Q&A Subject: woo!
Ah, Mac... how I've missed ya!
Those posts never fail to cause me to grin.
Posted on 2012-10-24 at 20:21:45.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: yep
That would be three hours after the end of their shift, with the next not happening for thirteen hours. So sure, beta shift folks might be at ten forward.
Posted on 2012-10-24 at 19:57:46.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: well
Duty shifts consist of three eight hour watches. 0800-1600 is the day (Alpha) watch, 1600-2400 is the evening (Beta) watch, 0000-0800 is the night (Gamma) watch.
Of course, every officer won't be on duty every single day. It's up to each department how they fill the various shifts.
Some officers (Operations Chief is a good example) may split their time between a bridge watch and managing a department.
Posted on 2012-10-24 at 19:43:17.
Edited on 2012-10-24 at 19:43:53 by t_catt11
|
Topic: Star Trek: The Cassius Incident Q&A Subject: heh
Glad you approve. I decided to try to curtail the "several weeks of posts without actually doing anything" that Trek games seem to encourage.
Posted on 2012-10-24 at 18:52:57.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: yep
Lieran's area is not directly affected - this would be crew quarters (deck 20), enginering labs, impulse engines.
Of course, being woken this way is not fun for anyone...
Posted on 2012-10-24 at 17:58:35.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: also...
If you have questions, ned help, etc... feel free to PM me and/or Eol.
Posted on 2012-10-24 at 17:49:45.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: ..and we're live!
Okay, folks... we are live!
In this type of situation, it (obviously) doesn't matter if you are on or off duty. Department heads are expected to proceed to their post with all possible haste; other officers will have assigned stations.
It's not yet 3:30 AM, so I would expect that pretty much everyone will have been asleep.
Please post accordingly.
Posted on 2012-10-24 at 15:46:36.
|
Topic: Star Trek: the Cassius Incident Subject: Star Trek: the Cassius Incident
Stardate: 2368.07.08
USS Discovery, main bridge - 0313
Thomas Ames was enjoying a rare moment in the big chair; bridge shifts of any sort for him had been rare enough of late as it was, but chances for the junior officer to have the conn were about as common as deep Klingon discussions about their feelings. With that being said, he found himself a little less sharp than usual, no doubt owing to the fact that on a normal day, he would be asleep right now. Ames stretched, stifled a yawn, and ran fingers through his close-cropped hair.
Once the initial novelty wears off, he mused, sitting here is actually a little... boring. Ames studiously focused on the slow movement of the stars on the viewscreen, looking for any sort of distraction.
The tedium of the graveyard shift was interrupted as the deck suddenly pitched wildly, throwing quite a few crewmen from all over the ship to the ground. Indeed, Ames himself barely managed to avoid landing on his face - and he had the luxury of a sturdy chair to hold on to. As less fortunate members of the bridge crew tried to regain their footing, the lieutenant reacted quickly.
"Ensign Martin, what the hell was that?" he demanded.
The young operations officer frowned initially, but then, her expression quickly changed to one more closely associated with nausea as she examined the console. "Damage reports are rolling in, sir..." she began in a shaky voice, "looks like something hit us, and hard. Multiple decks affected, structural integrity concerns on decks twenty through twenty-four."
Lieutenant Ames' mouth went dry as the adrenaline kicked in. "Any idea what caused it?" he queried.
"None, sir," Martin answered. "There's nothing on the sensors. No indication of any obstructions we could have struck."
Now, an icy blade of fear pierced Ames' gut. An attack, he mused. Has to be. From a cloaked opponent, most likely. "Shields up!" he barked at the tactical Ensign on the rim. "Red alert."
"Shields up," Enign Soileau cofirmed. Immediately, the alarm klaxons began sounding and the red lights started their steady strobe.
"Martin, give me full scans of the immediate vicinity, "Ames ordered. "Something has to be out there."
Suddenly, the deck violently pitched again.
************************************************
Stardate: 2368.07.08
USS Discovery, main bridge - 0316
The turbolift doors hissed open to admit a fully dressed Captain Blair. "Mister Ames, report!" he demanded. "What have you done to my ship?"
Ames wilted slightly, despite fully knowing that he had done no wrong. "Situation unknown, sir. We appear to have taken two direct hits from an unidentified assailant." As he reported, he vacated the captain's chair. "Shields are up, and we are scanning the area, but have been unable to locate any sign yet as to who or what is causing this."
How did he get out of bed, get dressed, and get here so quickly? Ames wondered. Does the man never sleep?
Posted on 2012-10-24 at 15:41:33.
Edited on 2012-10-24 at 16:08:08 by t_catt11
|
Topic: Star Trek: The Cassius Incident Recruitment Subject: updates
I have accepted Astrid as a junior engineering officer.
Just about to launch this game. Hold on, folks... this will be fun (I hope).
Posted on 2012-10-24 at 04:02:50.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: cool
Works for me, Duncan.
Posted on 2012-10-23 at 21:32:57.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: hrm
That does present a problem, doesn't it? I had overlooked the fact that we had a counselor between Averaci and Markus who actually posted a few times.
I guess that Venn had to have served... so I'll consider it a temporary/stopgap assignment until a permanent counselor (Markus) could be assigned.
Posted on 2012-10-23 at 19:47:35.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: no problem
Retcon is a comic book term - it means "retroactive continuity". In other words, we change the past to fit a current storyline.
I don't like the idea of so many officers changing in and out so quickly, timeline wise, so we're changing history, so to speak.
Posted on 2012-10-23 at 17:35:53.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: yep
That makes sense to me. We did get a few posts from Venn, but I think that counselor still falls into retcon territory. I just don't see a counselor coming on for a month, two months, then leaving.
Posted on 2012-10-23 at 16:13:16.
|
Topic: Star Trek: The Cassius Incident Q&A Subject: timeline
Our new mission date is going to be in July of 2368.
The last game/mission was April of 2368. There was some crew turnover at that time, which presents some interesting continuity questions. Namely, we had new PCs at multiple department head positions: Chief Engineer, Chief Medical Officer, Ops Chief, Helm, Security chief - all of which are once again filled by new characters.
Of those spots, our Chief Engineer was extremely active, and the Chief Medical Officer less so. The other three were hit or miss at best.
It's not really practical, story wise, to have officers turning over so quickly. Therefore, here are my rulings on handing this.
Chief Engineer had been on board for some time. Following that mission, Commander Kennedy accepted a transfer elsewhere. Commander Pantanko assumed this role in May of 2368.
Doctor Solkar was badly injured on that mission and had to move to a non-starship location for long term recovery. Doctor Synklar has been on board since roughly the end of April, serving as our Chief Medical Officer.
The other department heads are hereby retconned out of the Discovery timeline altogether. This means that the rest of you also (a) came on board either in April or May of 2368, and have been here for 2-3 months, or (b) have been here even longer - some time stretching back to early 2367. Pick one and include that in your bio. Might be good to post this info here to the Q&A thread, as well, so that everyone knows how long your character had been here.
If this absolutely will not work for the character concept that you have, let me know and we'll work something out.
Posted on 2012-10-23 at 15:34:37.
Edited on 2012-10-23 at 15:35:34 by t_catt11
|
Topic: Forum activity Subject: wow
The top five topics are actually starting to rotate pretty regularly. Will wonders never cease?
Posted on 2012-10-23 at 14:09:12.
|
|