[X] Plan: Strengthen the Foundations
WARNING! THE FOLLOWING INCIDENT REPORT IS CLASSIFIED: IF YOU DO NOT POSSESS AT LEAST LEVEL 3 SECURITY CLEARANCE, PLEASE BE ADVISED THAT VIEWING THIS IS CONSIDERED A CRIME.
Incident Report Tekka - Omnit - Lelbit
Location: Warp-Space Lane to Broken Edge, Broken Edge Rim
Infraction: Violation of Prime Directive
Ship # 0001 END ENDEAVOR
Attending Captain: Kyte Wy
Status: PENDING REVIEW
Incident Details: At approx 168 hours into journey, crew began to hear unknown noise. Initially believed to be shared auditory hallucination caused by typical warp-space turbulence, noises were dismissed and ignored as is normal protocol: crew were permitted extra hours sleep to compensate psychologically. At approx 230 hours, noise grew larger, and was noted as not being like standard auditory hallucinations: instead of expected exhortations of violence and other unpleasant intrusive thoughts, noise was noted as being akin to whale-song by chief attending mystek officer.
It was at this point that it was noted that warp-turbulence was receding, causing overall speed to pick up. Data was recorded, causing side effect of phenomena to be discovered: spikes in 90% of all major subsystems (Please see attached file for list) causing tripled engineering shifts to compensate for damage caused by phenomina.
At approximately 260 hours, control over navigational systems was lost as attending Machina went offline, the spirit complaining of 'headaches' in the preceding hours. It was at this point that that multiple other spirits were put into standby mode in order to prevent damage, with engineering working to disengage the warp-drive, increasing their shifts again. To compensate, all crew were put on standby and mobilized to help. Further, the mystek division was given double shifts: protective rituals and rites intended to protect the spirits of the ship and ward against whale-song phenomena.
At 300 hours, the ship crashed into a unknown (small) moon-sized organism believed to be the source of the whale-song, both of us violently exiting warp-space near Broken Edge system rim, the latter plowing through multiple large asteroids, before the latter corrected itself. At time, Endeavor was crashlanded in temperate forest area.
At 301 hours, we would come under attack by the natives, identified to be of the same species as Green Giant. Technological development would prove more advanced, the attackers having access to iron and steel weaponry and plate armor, but not nearly advanced enough to make them a significant threat were it not for their numbers and physiological robustness. Unfortunately, semi-lethal force was required to deter native hostility as neither sedatives nor tasers proved effective.
At 340 hours, we brought communications partially back online. The Green Giants were at that time dragging their people back to their lines. As per protocol, we allowed them to retrieve their wounded and dead: a task largely left to a newly identified secondary species that more closely resembled a sort of scrawny, roughly Tekket-sized simian-oid with extremely pronounced facial features, largely dressed in a roughspun substance scans indicate as extremely similair to wool (most common outfit observed on species: brown cap, light brown tunic, dark brown trousers, twine belt).
Attempts to communicate with Simianoids occurred: thankfully, we had manage to roughly decipher their language with our communicators at this point. The sentients, who seemed to have been sent for corpse disposal, were largely unwilling to talk: 90% complained that if the 'big gitz' (term was deemed untranslatable: seems to be an expression of fear) saw them chatting, they'd "'av our 'ides!". Translator was apparently only working at partial capacity.
Remaining ten percent were willing to answer questions in exchange for food. We had apparently crashlanded on a gargantuan space-borne leviathan large enough to host its own small civilization. This worldbeast, an ancient voyager of the stars, was known simply as Monstro to its teaming inhabitants, who piloted the beast around 'lookin' fer a right good scrap: apparently, we were the first one th' Cheefs (the political leader, who appears to be a sort of warlord) had found in awhile, so the 'big gitz' were itching for a fight.
One of them, upon being fed a piece of candy by a member of science division out of pity after explaining that its normal job was to feed corpses of its fellow 'grotz' (which seemed to be the name of the species) to animals after they had worked themselves to death in the iron foundries, asked to be taken with the ship as it left.
WHAT DECISION DID THE CAPTAIN MAKE?
Note that as they've authorized the use of lethal force against a technologically undeveloped civilization, Kyte is already in trouble with the Directorate. Currently, they are likely to get a slap on the wrist.
[ ] The Captain allowed it: The intelligence they had given had proven useful, and what accounts it gave of life on this world didn't indicate the 'grotz' were treated with anything approaching dignity and empathy, and the Directorate DID have laws for allowing the rescue of refugees. Besides, technically speaking, it wasn't a violation of the prime directive: as shown by them crashing their whale into the Endeavor, the inhabitants of Monstro did in fact have space travel in addition to warp travel: the Directive never specified that it had to be technologically assisted space travel. A loophole that would land the captain in extreme hot water (and one that would likely be closed immediately), it would likely cause her to get a citation for improper conduct and some form of formal penalty for the action, but it would be accepted.
Gain 1 Grot Refugee. Kyte lands in hotter water with Directorate.
[ ] The Captain suggested the Grot bring his friends: What they were describing was essentially slave labour, and Kyte couldn't find it in herself to not try and rescue a few souls from that fate. While the Captain couldn't do anything about the conditions of the world, they could at least liberate a few of the Grotz using the aforementioned refugee laws: it would likely result in her sitting before a Fleet tribunal, of course, because there was no way the Directorate would let her get away with such a flagrant violation of the prime directive.
Gain many Grot Refugees. Kyte will likely be charged with a major violation of the Prime Directive.
[ ] The Captain said no: The Grot was a unknown lifeform. There was no guarantee it could even digest the same proteins as Tekket, much less survive in Tekket society, to say nothing of potential contagions, a completely alien psychology, etc. While the natural instinct was to help, one shouldn't let that outweigh good sense. An unpopular decision with the crew, but a necessary one. The fact that this would leave said loophole open longer would be left unsaid.
Do not gain 1 Grot Refugee. Crew discontent grows.
Meanwhile, what did the Engineers focus on? Select two:
[ ] Power: The ship was currently operating on auxiliary power. The spikes forced the primary reactors to go offline: if they could safely be re-activated, it would drastically increase the odds of a successful escape by providing enough energy to run more systems at full capacity: it would also help with keeping the ship secure.
[ ] Engines: The Engines had been badly damaged in the crash: while they were already being repaired by the Mag-Assembly protocol, a great deal of damage had been to complex systems specifically, reducing overall efficiency to 1/4th: theoretically enough to lift off, but perhaps that margin could be improved.
[ ] Gravity: The anti-gravity systems of the Endeavor were one of the major things that kept your ships from tearing themselves apart when they moved. Damage wasn't horrible, but even at 4/5th capacity, it meant that when you launched there would be considerable damage from the stress of escaping Monstro's gravity well.
[ ] Communications: Right now, it wasn't just power that was at a premium: by bringing comms back on, the engineers would free up a massive amount of bandwidth, enough to hopefully allow the spirits of the ship to piggyback on the systems, letting you rouse them from their forced dormancy.
[ ] Weapons [Nuclear Weapons]: A missile was ultimately just a shuttle with a payload. And a payload was just a clumsily designed reactor. By flash-converting the ships nuclear arensal into more thrust and more power, the ship would have to sacrifice her strongest weapons to do this, but escape would be far more likely.
What would the Mysteks do?
[ ] Rouse the Machina: The Endeavor only had a few Machina in its crew: Navigation, Power, Security, and one in the main Mag-Tek Altar. Each of these technomantic spirits could prove the difference between life and death, with their arcane abilities being capable of empowering the ship to greatly improve performance.
[ ] Rouse the Drones: Meanwhile, the Drones were far, far more common: enough to effectively double the workforce, and right now, all hands on deck were needed. If they were brought back online, it would mean the repair of the ship would go immensely faster and the security team would be greatly reinforced.
[ ] Ward against the Whale-Song: Warding rituals were still primitive, but with a bit of creativity and lifeforce, it should be possible to at least muffle the Whale-Song, reducing the mayhem it was causing with your systems and spirits, even if only somewhat.
[ ] Invigorate the Ship: The Ship's spirit had proven resistant enough to the Whale-Song that it was fully awake, still exhibiting the same dim awareness. Perhaps by performing an emergency infusion of life-force, the Ships spirit could be invigorated to help shield against the whale-song.
((((()))))
Meet Monstro, the biggest void whale in the Reach.