Discovery Gaming Community
Section 8 - Logs - Printable Version

+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Role-Playing (https://discoverygc.com/forums/forumdisplay.php?fid=9)
+--- Forum: Stories and Biographies (https://discoverygc.com/forums/forumdisplay.php?fid=56)
+--- Thread: Section 8 - Logs (/showthread.php?tid=195021)

Pages: 1 2


Section 8 - Logs - Section 8 - 11-22-2022

[Image: iO7z9dm.png]
Section 8







Login ID: Hawkins
Entry Date: 22 Nov. 829
Location: Unto Nightfall, Error






Emergency jump; unknown system

I still do not know how the Nomads were able to discover [REDACTED], but it matters little. With the new facilities on [REDACTED] operational, the loss of our old base of operations will be but a mild blow to Section 8. That is, of course, assuming Odysseus and the transports reach the new base. Valkyrie Squadron, I regret to report, will not. They gave their lives in defense of the convoy and the Unto Nightfall. We, too, would have been overwhelmed by this final Nomad assault, had I not ordered an emergency jump out of the system as soon as Odysseus confirmed exiting the Helljumper Sector.

As per protocol, the emergency jump was conducted blind, without any input coordinates. We could not risk the Nomads tracking our trajectory to any of our stored destinations. The jump should have nevertheless landed us somewhere within the boundaries of the Sirius sector - the drive's safety mechanisms are designed to ensure as much. However, something appears to have gone wrong. We find ourselves in an entirely unknown system. Astrographical data has so far proven inconclusive, nor do the surrounding stars match any configuration in the Nightfall's onboard database.

[Image: klP2FyBl.png]

Sysops has been unable to establish a connection to the neural net, nor have we been able to contact Odysseus or [REDACTED]. Trasser believes we may have indeed traveled beyond Sirius. I am not so certain. Regardless, we certainly do appear to be lost.

Furthermore, the jump exceeding standard operating parameters overloaded the drive, causing cascading damage and triggering several failsafes throughout the Nightfall's electronic systems. No crew was injured, but the ship is in poor condition. We will need to spend several cycles repairing the most vital systems - particularly the jump drive. For now, however, I am afraid we are stranded here, wherever here is. Until we are able to perform another jump, I will have sysops conduct detailed scans of the system and its stellar bodies. Perhaps we will discover something useful - a means to contact [REDACTED] or a hint as to where exactly we are.

For now, we must remain patient and cautious.

- Hawkins


Attachments: None




RE: Section 8 - Archive - Toaster - 11-23-2022

[Image: iO7z9dm.png]
Section 8







Login ID: Hawkins
Entry Date: 23 Nov. 829
Location: Unto Nightfall, Error






Unknown system cont.

We have been in this system for going on twenty-four hours. So far we have been unable to determine our location. Sysops has failed to establish any connections to either the neural net or Section 8, nor have we encountered any signs of life or activity otherwise within the system. Further, the Nightfall's nav computer seems to be incapable of accurately charting the system as we explore it. Why exactly this may be the case has yet to be determined, though Trasser believes it may be related to damage caused by the power surges we experienced during our jump. If that is so, we should eventually be able to mend the issue and chart a proper map of this place.

In the mean time, we must make due with more old fashioned means of detailing the system's exploration. So far, scans have determined the system to be a binary system made up of two type G8 stars. Orbiting these, we have discovered two planets - one terrestrial, the other a gas giant. The Nightfall's scanners, however, have thus far been unable to gather any detailed information on these. Trasser again blames damaged electronics. Further, we have found two asteroid fields, one of which is contained within a dark nebula. Again, no more detailed analysis is possible. I have so far elected not to explore the nebula. In our current condition, I would rather not risk such an endeavor, especially considering the system's unusual radiation. So far, the Nightfall's shielding is holding, but without the possibility of repair and maintenance, it is only a matter of time before the ship suffers compounding damage.

[Image: WW1GZzBl.png]

For now, we have retreated into the second asteroid field. While we appear to be alone here, there is little point in taking any unnecessary chances by remaining in open space. Repairs of the Nightfall's systems continue, as does further analysis of our findings. The crew remains on high alert with twelve-hour shifts. Regrettably, Solemn's fighter was damaged too badly during our escape from [REDACTED] to be launched. As we lack the means to repair it, we must make due without a fighter escort for the time being. One can only hope that we will not find ourselves in need of one.

- Hawkins


Attachments: None




RE: Section 8 - Archive - Toaster - 11-24-2022

[Image: iO7z9dm.png]
Section 8







Login ID: Hawkins
Entry Date: 24 Nov. 829
Location: Unto Nightfall, Error






Unknown system cont.

Another twenty-four hours have passed without any contact with Section 8 or the rest of Sirius. Sysops and engineering are hard at work repairing the damaged systems, as well as keeping up with increasing radiation damage. We are still unable to generate any sort of map of this system, nor can our sensors seem to gleam any kind of detailed information from any stellar bodies we encounter.

We have discovered two more small asteroid fields, one to what we assume is the system's stellar south-west, the other to the north-west. The latter seems to have formed around the smaller, terrestrial planet. It appears to contain faint traces of water ice, some of which we have mined in order to augment our own ever dwindling supplies, yet we were unable to detect any other resources that might be of use to us.

Our sensors picked up a strong source of gravitational waves within the south-western field. On careful approach, it revealed itself as a gravitational anomaly consistent with a jump hole.

[Image: 9mFHAOA.png]

While the crew was elated to have discovered a possible route out of this system, I had sysops conduct a more thorough analysis of the anomaly. Magnetic and gravimetric readings fluctuated too wildly for any kind of trajectory to be calculated, nor could we determine whether a ship of the Unto Nightfall's size could safely traverse it. For now, we have jotted down the anomaly's location and will continue to explore the system for other means of egress or until engineering manages to get our jump drive operational again.

Trasser suggests that we take a closer look at the gas giant. It appears to be orbited by a complex ring system, which may contain usable resources or, perhaps, further anomalies. I have ordered helm to set a course and approach at half speed to give the crew some time to rest and recover.

- Hawkins


Attachments: None




RE: Section 8 - Archive - Toaster - 11-27-2022

[Image: iO7z9dm.png]
Section 8







Login ID: Hawkins
Entry Date: 26 Nov. 829
Location: Unto Nightfall, Error






Unknown system cont.

Our cautious exploration of this system has continued for another forty-eight hours. Trasser's suggestion to investigate the gas giant and its ring systems proved most prudent. While the resources we found within the orbiting rings were scarce, what we were able to mine greatly expedited the process of restoring the most vital of the Unto Nightfall's damaged systems and repairing the gravest of radiation damage. Engineering once more worked a miracle, though the results of their work are hardly pleasing to the eye. A downside I am willing to overlook, given the circumstances and the fact that the ship's jump capability has been restored.

We continued to avoid the nebula to the system's north-east. Both Trasser and I were uncomfortable with the idea of exploring its depths, though why exactly we could not tell - instinct, perhaps. Instead, we remained in high orbit of the gas giant, letting its gravity guide the Nightfall's course across its circumference, giving us an excellent view of the entire system. Sadly, our sensors remained unable to obtain any detailed readings of our surroundings.

As we orbited the planet, however, we detected something particularly unusual, even by this system's standards. An object circling the gas giant at a lower altitude.

[Image: OM2XIwVl.png]

At first, sysops assumed it was a large asteroid or small moon orbiting the planet. As our orbit took us closer, however, it became apparent that the object was artificial in nature. Our sensors - for all their lauded capabilities - were once more unable to ascertain any details. In fact, what readings we were able to gather suffered corruption and artifacting. Sysops is unsure whether this is due to the system's general background radiation, interference from the planet's magnetosphere, or perhaps an effect originating from the unknown structure itself. Nevertheless, visuals indicated that it was not of human origin or at least not of any design known to Sirius.

Further, comms picked up a strange signal pattern apparently being emitted by the structure but was unable to decrypt it.

While I admit that my curiosity is certainly piqued by this development and I would very much like to investigate this unknown structure more closely, Trasser advises against approaching any further. He is right, of course. Our foremost prerogative at the moment is to depart this system, return to known space, and reestablish contact with the rest of Section 8. We have been lost far too long already and with our jump drive repaired, we have no more time to waste.

While sysops and engineering complete a series of simulated jump sequences to ensure the drive can operate within safe parameters, we will complete one final orbit of the gas giant and deploy a number of probes throughout its ring systems. With any luck, they will survive the system's radiation and we will be able to establish a link with them upon our return to [REDACTED] and calculate coordinates for a future return to this system.

Of course, this depends first and foremost on whether or not we succeed in jumping home.

- Hawkins


Attachments: None




RE: Section 8 - Archive - S8 Operatives - 12-23-2022

[Image: iO7z9dm.png]
Section 8







Login ID: Solemn
Entry Date: 23 Dec. 829
Location: Niigata Star City, Sigma-59






Report: Aniva Nebula

As requested, I finished my excursion to Kusari by inspecting the Sigma-59/Omicron Epsilon jump hole in the Aniva Nebula. Sensor data indicates that it remains stable. No signs of recent traffic, human or otherwise, were detected.

En route to sector 2G from the Sigma-59/Okinawa jump hole I passed by Planet Toyohara. My sensors picked up unexpected readings coming from its vicinity, so I broke off to investigate. In high orbit over the planet, I discovered a small station; its IFF transponder read Yaese Research Station.

[Image: t5rqaF3.png]

It was damaged and decaying, but interfacing with its automated response systems showed that its reactor, docking facilities, and basic life support were still functioning. Hailing the station gave no answer, so I docked for a closer look. The installation appears to be completely abandoned. I found no signs of life or any items of interest on board. I couldn't tell how long it has been since someone set foot on the station, nor what it was used for; though the name suggests that it was looking into Planet Toyohara and the surrounding fragmentary field.

I disembarked, stored the data my sensors and scanners collected, and resumed my flight.

Near the Sigma-59/Omicron Epsilon jump hole, my ship's sensors picked up increased radiation coming from deeper within the Aniva Nebula. Readouts indicated that its origin wasn't far, so I chose to investigate. I discovered two small regions within the nebula's asteroid field containing a variety of rocks different to those that make up the rest of the field. My scanners could not make out whether they also differed in composition, but they appear to be emitting high energy radiation - levels were tolerable.


Maybe the Gas Miners on Niigata know more about this. I will be staying there in case I am to take a closer look at these findings.

That's all.

- Solemn


Attachments: None




RE: Section 8 - Archive - S8 Operatives - 01-18-2023

[Image: iO7z9dm.png]
Section 8







Login ID: Solemn
Entry Date: 18 Jan. 830
Location: Bielefeld Base, Sigma-15






Report: Sigma-15

As requested, I returned to the Sigmas to look out for unusual activity. My timing could not have been better: The orbit of Planet Hammersee, Sigma-15, was crowded. Notably present, among others, were:
  • Caliban (formerly Vincent Abrams)
  • Ridgenose (former Xeno Alliance member)
  • MNS-Amalfi (potentially infected crew)
  • A/)-Revenant (high priority target)

Others included several ships of the Rheinland MND, the Core, and several freelancers. As I arrived, Caliban and the present Core vessels were engaged in combat with Revenant and an Auxesian frigate. Both Revenant and the frigate went down.

Following the engagement, I contacted Ridgenose over a tightbeam frequency to inquire about Caliban and the current goings-on, assuming the former's ties with the latter from when he still went by Abrams remained. Ridgenose wasn't eager to talk at first, but opened up eventually. He confirmed the Alliance commander's information that Caliban is indeed Abrams. He further stated that Caliban is currently involved with the Core, Bretonian intelligence, and the Outcast de Marco. Also that he is still seeking "the Vault" - the presumed information cache guarded by the Sentinels.

Closing the conversation, Ridgenose made a request: that Section 8 share with him the evidence presented to Cobra regarding Vincent Abrams prior to his (failed) termination. In return for this, Ridgenose will gather intel concerning Caliban and the Sentinels and forward it to us. My personal opinion would be to agree to this deal. Ridgenose is now an independent pilot and may prove a valuable asset to us - especially considering how difficult to track Caliban has proven to be. Their former loyalties to each other could be useful in that regard. Even should Ridgenose go back on his end of the deal, little will be lost by giving him access to the files at this point. It can be revoked easily enough.

I wish Emissary had been there to handle the talking. Maybe she could have gotten more out of Ridgenose. Logs of the conversation are attached to this report.

That is all.

- Solemn


Attachments:




RE: Section 8 - Archive - S8 Operatives - 06-17-2023

[Image: iO7z9dm.png]
Section 8







Login ID: Vagabond
Entry Date: 17 June 830
Location: Cairo Station, Omicron Zeta






Priority Report: Overwatch/Liberty Breach of Home Space

Command,

Yesterday at 1950 hours SMT, the Unto Nightfall reported sightings of a Liberty Navy convoy, accompanied by at least one Liberty Security Force ship, in Omicron Nu and Omicron Minor. As I was the nearest pilot, I launched from Cairo Station to investigate. I spotted the convoy, made up of two Bison-class heavy transports, three gunboats, and several snubcraft in Omicron Zeta, preparing to pass through the Omicron Mu jump hole. Several Overwatch ships were with them, and I was preparing to assist them in repelling this obvious breach of our home space, when, well, the lead Overwatch operative, Solantheus, invited them to make the jump. I was shocked but kept my mouth shut, instead following them to figure out what was going on.

It only gets more bizarre from here. The Overwatch vessels guided the Libertonian convoy - again, including an LSF ship - through the Omicron Zeta minefield and out of the Orillion Ice Field, all the way to our very own home world, Akabat. At no point did the Overwatch ships bother patching me into tactical comms (no wonder after what I heard about Odysseus' latest achievements) to tell me what the hell they were up to. I opened a secure channel to secondary agent Nobume Maki instead, who shared my apprehension about having Libertonians waltzing around our home. Together, we ensured that none of our "visitors" strayed from their formation.

Now, when the convoy reached Akabat orbit and Overwatch prepared to transfer unspecified cargo to the two transports, I was expecting some kind of highly confidential technological exchange to warrant the presence of a small Navy fleet and - I can't stress this enough - a Liberty Security Force ship. But the cargo turned out to be ... two ship loads of palladium. I was at a loss.

While the palladium was being transferred, Agent Maki and I kept an eye on the Libertonians. Unsurprisingly, the LSF vessel, gunboat Fort Custer, broke from the formation and attempted to sneak away, but we put a quick stop to that before it get more than a few clicks from the convoy.

Once the transports were ready to go, the convoy turned around and this time the Overwatch vessels showed them the way to the Omicron Minor jump hole. The return journey through Minor and Nu was relatively uneventful, save for the appearance of a lone Nomad warform near Taba Starbase and a Kusari Office of Intelligence scout getting lost in the Wall of Seth. Once approaching the supergate to the Virginia system, the Overwatch vessels and the Libertonian convoy parted ways. Maki and I lingered until all Navy and LSF vessels had made the jump out of Omicron Nu before returning to Cairo Station ourselves.

I'm not sure what to make of all this, so I hope Command can figure out the meaning of it all. From what I can tell, Overwatch just gave the Liberty Navy and Liberty Security Force a guided tour of the Order's home space, all for a gift of palladium. I don't even want to imagine the damage to the Order's internal and operational security this stunt of theirs caused. I'll be keeping my eyes and ears open for any news or explanations for this gross misconduct.

Communication logs and video recordings are attached. That is all.

- Vagabond


Attachments:




RE: Section 8 - Logs - Toaster - 10-13-2023

[Image: iO7z9dm.png]
Section 8







Login ID: Trasser
Entry Date: 13 Oct. 833
Location: Planet Akabat, Omicron Mu






Priority Report: Codename EARHART

This is Commander Maximilian Trasser's report on the preliminary expedition into the newly discovered, presumed extra-Sirian system, codename EARHART.

At 1835 hours SMT, October 12, the Unto Nightfall engaged its jump drive for a "blind jump," opening a hyperspace breach to what conventionally should have been a random location within the Sirius sector. The Point Of No Return, under my command, escorted by field operative Armsman, was to enter the opened breach, traverse hyperspace, and investigate whatever system we entered on the other side. As predicted based on analysis from a previously attempted blind jump, the Point Of No Return exited hyperspace in an unknown location. Due to rapid destabilization of the jump hole, Armsman was unable to follow; the Unto Nightfall was forced to open a second breach, which the operative was able to traverse. While he, too, entered the same location as us, our arrival points were separated by several dozen clicks.

The location, confirmed by visual data comparison with the Unto Nightfall's logs to be codename EARHART, appears to be a starless sector of space. While similar in appearance to locations in the Edge Nebula, we were unable to pinpoint coordinates using known astrographical data, corroborating the hypothesis that EARHART is extra-Sirian.



The EARHART sector


Fascinatingly, the entire sector was littered with debris. Scanner sweeps confirmed the majority of it to be of human origin. Several dozen remains of spaceships were discovered, most of relatively recent date, including the two Libertonian dreadnoughts Fairmont and Whitefield and their escorts, presumed lost in 826 A.S., as well as ships of Rheinland, Kusari, Bretonian, Gallic, and Outcast origin.



The LNS Fairmont



The LNS Whitefield


However, we also discovered wreckage of significantly older make, dating as far back as the earliest days of Sirian exploration: the LCC Bell, dating back to 92 A.S., and the LCEC Ordway, dating as far back as 60 A.S.



The LCC Bell



The LCEC Ordway


At the center of EARHART, we discovered a formation of clearly artificial origin: a series of smaller objects, enveloped by energy fields of a yet unknown kind, forming a ring around a large central structure, consisting of two horizontally segmented, roughly diamond-shaped polyhedrons forming a pylon. Their segments shift by rotating every few seconds. Between the two objects' obtuse points, sensors detected a point of high, extremely concentrated energy. Exact readings were impossible to take, resulting in readout failures across the board. The exact energy output, dimensions, mass, material composition, or temperature of the structure are therefore currently impossible to ascertain. However, it is clear that these structures are not of human origin.



The central structure with surrounding ring formation


Armsman and the Point Of No Return attempted to approach the formation to conduct another series of scans at closer range. However, the smaller structures forming the perimeter seem to serve as a defensive system. They targeted both our vessels and launched kinetic projectiles at incredible velocities and ranges. The Point Of No Return took a direct hit, which overloaded her shields immediately. We aborted our approach, took evasive actions, and retreated out of range of these weapons. Scanners could not determine the composition of the launched projectiles, nor the exact mechanism by which they were launched.

The sector's intense radiation, likely emanating from the central structure, was gradually wearing through both Armsman's and the Point Of No Return's shielding. Nevertheless, I decided to perform a sweep of EARHART's outer reaches. Around the perimeter, we discovered eight further structures of clearly artificial, non-human origin. Consisting of three pairs of connected petal-like "arms" in a ring formation, these constructs vaguely resemble human-made jump gates. While four of these objects were inert, four more were actively containing unstable jump holes. Amazingly, scans showed that two of these led to Sirian systems, Sigma-19 and Zurich. The other two destinations could not be determined. It is possible that these lead to further extra-Sirian systems. As with the sector's central structures, even close-range surface scans were unable to determine the "gates'" material composition.



An inert "gate"


With our ships' shielding rapidly wearing down and radiation damage to their hulls accumulating, I made the decision to abort any further exploration of EARHART. Armsman and the Point Of No Return set course for the gate containing a jump hole to the Sigma-19 system and entered. Despite its unstable nature, we successfully reentered real space intact. The egress point showed signs of extreme instability, likely rendering a return jump through the jump hole to EARHART recklessly dangerous, if not outright impossible. Given the state of our ships, I chose not to make an attempt.

We returned to Omicron Mu at best speed and without any incident to deliver the collected data.

I advise extreme caution regarding future expeditions into EARHART. It is unknown whether further blind jumps will open breaches into the sector, nor whether there will continue to be viable egress routes back to Sirius. Further, the intense radiation and present hostile weapon systems pose a severe threat to any exploratory force.

End of report.


Attachments




RE: Section 8 - Logs - 'Scorpion' - 01-22-2024

[Image: iO7z9dm.png]
Section 8







Login ID: Armsman
Entry Date: 23 Jan 834
Location: Dabadoru Station, Omicron Delta






Romero

As ordered, I met with a fresh contact named Romero.

I conducted this meeting in Minor, away from the major belt of the graveyard and in an empty section of the wider nebula. He is a stubborn and insistent creature. Undoubtedly of Cretan ancestry and carrying all the implications that comes with. Throughout the course of my questioning, despite his erratic behavior, I did not see any signs of what could be described as "compromised" behavior. The subject instead displays a commitment to stand against whatever these "things" are that he cannot understand.

To that end he has requested, numerous times and with the thumping of his fist, information. The kind only we can supply him with. I leave this to the discretion of Command, I emphatically informed him of my lack of authority to brief him regarding anything and advised general caution.

I conclude the subject to be simple minded, or unintelligent in their approach if left uninformed. Additionally, I have little suspicion regarding the subject's status as being compromised, although the Freeport's scanning history will easily verify this and substitute the need for trust.

End of report.


Attachments:




RE: Section 8 - Logs - 'Scorpion' - 03-12-2024

[Image: iO7z9dm.png]
Section 8







Login ID: Armsman
Entry Date: 12 Mar 834
Location: Dabadoru Station, Omicron Delta






Sigma Incident

Armsman reporting after deployment into Omicron Delta to cover Vagabond's withdrawal.

I am acutely aware that my "expertise" is often viewed as too blunt for our otherwise clinical usage. But the Overwatch's recent actions call for some form of corrective measures to be taken if we are to truly be prepared to meet threats across the Houses. Our cause will be hard pressed if we are to find ourselves in a situation of undue scrutiny with our regional partners, the Overwatch is currently making quick work of ensuring most of our partners readily believe us to be misguided imperialists not unlike the warriors of Crete rather than the bulwark against alien invasion that we were once recognized as.

This cannot continue. I humbly suggest that our regional partners be properly informed of the Overwatch's recent tendencies, not just to their respective groups - but to our own forces. Our regional partners must be further advised to cease and desist with all forms of cooperation previously offered to the Overwatch. I will state however that it would be a waste of time to attempt this with the Corsairs as they are likely too committed to expansionism to heed our warning, especially if the Overwatch is so keen to throw their lot in with them.

The Bundschuh, Blood Dragons, and any other group that has offered us steadfast support in the past must be inoculated against Overwatch hysteria, so that we might repair the damage done and secure the regions in which these groups occupy against any unforeseen threats from the ultimate enemy.

End of report.


Attachments:

N/A