[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/session.php on line 1035: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3760)
[phpBB Debug] PHP Warning: in file /includes/functions.php on line 4581: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3760)
[phpBB Debug] PHP Warning: in file /includes/functions.php on line 4583: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3760)
[phpBB Debug] PHP Warning: in file /includes/functions.php on line 4584: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3760)
[phpBB Debug] PHP Warning: in file /includes/functions.php on line 4585: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3760)
args.bungie.org - View topic - Alert! EM Anomaly: Cryo Bay 2
View unanswered posts | View active topics It is currently Fri Dec 06, 2019 3:30 am



Reply to topic  [ 15 posts ]  Go to page Previous  1, 2
 Alert! EM Anomaly: Cryo Bay 2 
Author Message
Data [Authenticated]

Joined: Fri Mar 18, 2011 9:37 pm
Posts: 128
Unread post Re: Alert! EM Anomaly: Cryo Bay 2


Sun Mar 20, 2011 12:25 pm
Profile
Data [Conditional]

Joined: Fri Mar 18, 2011 9:56 pm
Posts: 42
Unread post Re: Alert! EM Anomaly: Cryo Bay 2
I've done what I've done for a reason, Captain. I'll tell you what you need to know.

What happened to CN Raschad will only happen to those who have a CNI implanted. They will suffer it to a lesser degree than CN Raschad, however. I'm guessing a splitting migraine. The reason why he suffered more is classified within his medical records.

As for the armor. I can confirm that it matches the Kavacha Personal Powered Battle Armor System that F484 perfectly. The simulations that were run on what it must have looked like after his final known combat activities match on all counts, as do all of the personal modifications he made to his armor.

It does not match the first apparition that was reported, however. That said, given the appearance of F484's armor, even as an apparition, I can safely say that the appearance of the other figure was within the expected statistical probabilities.

And that is all that I will say.


Sun Mar 20, 2011 12:25 pm
Profile
Data [Conditional]

Joined: Fri Mar 18, 2011 4:35 pm
Posts: 42
Unread post Re: Alert! EM Anomaly: Cryo Bay 2
Hive,

Please have PO3 Wolfe recommended for transfer after Dr. Muldoon has cleared her for duty. Until then, she and CN Raschad are to be escorted and guarded by protective detail 24/7. This is for their own protection. I imagine there's already a hushed whisper amongst the crew about them being an 'item', so chalk this up to a lover's spat that got way out of hand. CN Raschad's 'undisclosed' injuries were not intentionally inflicted by PO3 Wolfe and were accidental in nature. The protective detail is to enforce article 247-A, Subsection 2 of the Enlisted Personnel Protocol and Conduct Manual, prohibiting 'romantic or sexual fraternization between crew members and enlisted personnel.' If XO McAllister needs a translation for her own distribution, tell her the guards are "to make sure there ain't no hanky panky rocking the Captain's boat" and to also make sure another 'spat' doesn't happen again.

Have Dr. Muldoon counsel PO3 Wolfe on the subject of voluntary transfer. It's better if CN Raschad believes she chose to leave, in my opinion.

As for the equipment malfunctioning...Do we have any analogue recording equipment? I know it's archaic, but it's worth a shot. Since anything digital seems to be affected by the EM anomalies, perhaps some good ol' fashioned chemical film will stand up to our poltergeist problem.

And since I'm sure Helen is listening, I want to make it clear to one of my crewmen is in the infirmary and another is no longer fit for active duty, both as a direct result of a Shipboard Incident of Foreign Origin, officially making this a matter of personnel safety. As the Commanding Officer aboard this vessel, it is my duty to protect my men through any means necessary. Therefore, I am enacting my priority command status and declaring a state of classified emergency, to be known only to those immediately involved.

And as Captain, I am making the descriptions of the two sets of Kavacha armor directly related to the S.I.F.O. and therefore necessary information in keeping my crew safe. Now, if our frigid little spinster of a spook A.I. wants to pull ONI rank and continue to deny me my rightful use of said data, then I want it known that I shall put in a formal report to the nearest ONI vessel and to Command that I suspect our guest A.I. to be malfunctioning and potentially not complying with the Three Laws, particularly the First and Second Laws, due to her potential harm to shipboard personnel by method of inaction in direct conflict with the C.O.'s attempts to protect his men.

In short, I am the Captain of this vessel, and as Captain I demand to see any and all pertinent information, 'Redacted' or not, that relates in any way whatsoever to the incident in Cryo Bay 2, or I'll make Rampancy look like a case of the sniffles compared to my personal description of Helen's recent conduct. And trust me, what our 'ghosts' look like is beyond pertinent.


Sun Mar 20, 2011 2:51 pm
Profile
Data [Conditional]

Joined: Fri Mar 18, 2011 9:56 pm
Posts: 42
Unread post Re: Alert! EM Anomaly: Cryo Bay 2
You're actually threatening me? And you're quoting protocol in the same message? How amusing.

Special Operations Protocol 485-D Subsection 14
Any operation that results in the possible discovery of a Class 6 Weapon of Mass Destruction will not be disclosed to unauthorized personnel until clearance is given directly by HIGHCOM.

Materiel Security Protocol 214-A Subsection 7
Any equipment which is deemed sensitive in nature and of vital security to the stability of the UNSC and any human colony is to be released on a need to know basis only[...]

WMD Retrieval Protocol Sec
#^&!!CNTU.&*($&@($^)))@.A234TRPLK#%^@#**F

It stood about two hundred and ten, maybe two hundred and twenty centimeters. I'm not sure. Sort of a dark green. The chest was angular and wide. It felt masculine. It was like... It was like the armor was secured to the body glove and itself. Does that make any sense? The bodyglove was almost rigid, in a way, with lines in it to help with movement, I think. But it was tight and form fitting. Thick, too, by the looks of it. I mean, except for general size, I couldn't tell what was underneath. Um, the left shoulder had a large pauldron, is that what it's called? Larger than the right. I mean, it stuck up higher, and was wider too. Higher than the shoulders. The visor on the helmet was blue... God, you're going to clean all this up before you show the Captain, right? ...Okay, okay. Um... Yeah, the visor was sort of blueish. It was angular, too, like it didn't curve. Kind of like the old ODST armor, you know? Only smaller. Like it was only meant to cover the eyes, not the whole face. There were... I don't know, blocks on the sides, and up top. Some sort of sensor suites, I think. I mean, that's what it reminded me of, when one of the boys who has to check the really little stuff attach that kind of crap to their suits. Or maybe it was a comms array. Or maybe it was just there for show, I don't know. Legs? The armor was angular on them, too. The knee guards were small. The boots were... I don't know, armored boots? I mean... No, no there really wasn't anything special about the legs. They looked fairly beat up, though. The knee guards were so small I almost didn't see... No, wait! There was something on the right leg. Like an armored holster on the thigh or... Wait, wait! On the chest! There were places to attach webbing. Like, built into the armor. Um... On the shoulders, sort of behind the head, it looked... They came up oddly. I mean, they were small enough across that I could have grabbed each one firmly, but they must have come up to the chin or so. No, higher. No, more like the ear. Yeah, they came up to the ear or around there. There was something on the arm... No, the right. It had, like, a laser designator or something coming off the arm guard. I don't know... No, no, the helmet was pretty flush with the visor. Still angular, but curved. But I thought I saw tubes in it. Not, like, through it or anything, but around the jawline on either side was a tube that was briefly visible. It looked damaged, like something had been ripped off. The whole damn thing looked damaged. I mean, all the armor was gone from the left arm. His left, not mine. Mid-bicep, maybe. About here... Yeah, exactly. Yeah. But on the bodyglove thing, you could see the mounting points, where the armor was supposed to attach or something. But the armor on the arm, it looked kind of melted or something. No, like it had been blown off and carryover heat had melted it a bit, or the rest of the armor had been vaporized or something. No, not drippy, but it was rounded and smooth. No idea, sorry. The thing could have been made from tin for all I know. Patterns? Um, there was a bit of one on the back of the hand. It reminded me of the stubs on gloves in fighting games. Does that make sense? Um... That's about it as far as patterns go. I mean, seriously, they expect me to describe something like this?

88$#*>>&!(^246G%A2))GF=@IDO8390%@)X375!#r all crew.

In short, Captain, you'll get your information when I get a message directly from HIGHCOM telling me that you're authorized for it. Now, if you don't pardon me, I have work to do.


Sun Mar 20, 2011 11:40 pm
Profile
Data [Authenticated]

Joined: Sat Mar 19, 2011 4:26 am
Posts: 76
Unread post Re: Alert! EM Anomaly: Cryo Bay 2
Helen.

To paraphrase an old vid I once saw as a child: When it comes to the safety of my crew, there's me and then there's God.

We are the Space Bees. NOT the Space Mushrooms. If you have any theories about these anomalies, including how to prevent them from injuring my crew, it would be best if you were up front. Unlike some of the units you may (or 'may not') have been assigned to, my people are not expendable.


Mon Mar 21, 2011 12:02 am
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 15 posts ]  Go to page Previous  1, 2

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by STSoftware for PTF.