Login

S8 Operatives · 03-23-2024, 11:04 AM,

Section 8

Login ID: Solemn
Entry Date: 23 Mar. 834
Location: Planet Akabat, Omicron Mu

After Action Report: Omicron Minor

Yesterday, 22 Mar. 834, at around 1900 hours SMT, Cairo Station picked up a massive energy spike originating from the northern Pohnpei Nebula in the Omicron Zeta system. Command decided that local Section 8 units should investigate while a task force was organized to fend off a potential alien attack. I was joined by operative Wendigo. We performed a quick sweep of Omicron Zeta and encountered a flotilla of Nomad warforms and infected vessels. Being heavily outnumbered and outgunned, we broke off our patrol and returned to Omicron Mu to relay our findings to the task force. While we were reporting the alien activity, Cairo Station informed us of a second, stronger energy spike from the direction of the Omicron Minor system. Anticipating an alien incursion, the task force set out, with our fighter complement taking point. Operative Armsman was assigned command of our strikecraft.

Arriving in Omicron Minor, the task force set course of Planet Toledo and the Graveyard, hoping to intercept any Nomad forces outside of the system's asteroid field. In Toledo's orbit, we encountered not only the alien flotilla Wendigo and I came upon earlier, but also several wings of Libertonian snubcraft - including elements of the First Armada and the Alaska Security Force - as well as a number of Core fighters and bombers. Ignoring the human trespassers, we engaged the alien forces at once.

Of note: The RNC Einbeck - the same Rheinland cruiser Vagabond recently encountered in Sigma-17 and Omicron Delta - appeared to be attempting to perform scans of the Isis' wreck. To what end, I don't know. The Einbeck was quickly dispatched by friendly forces. However, the ship and her crew are clearly compromised.

The Libertonian and Core units assisted with fending off the alien incursion. But, unsurprisingly, the useless traitors turned on our forces as soon as the Nomads were pushed back. Our fighter wing was massively outnumbered while the rest of the task force was harassed by Core warships joining the fray. Eventually, we were overwhelmed by enemy snubcraft and my ship was disabled. Luckily, I was able to disappear amidst the Graveyard's wreckage and await SAR. How the battle finally turned out, I don't know. But my guess is that the aliens' plan - whatever it was - was halted.

Operative Wendigo, formerly Knave, performed well. Emissary is right. He may be of some use.

That is all.

- Solemn

Attachments:

Video Recording

Section 8 - Content & Feedback

Toaster · 06-06-2024, 03:38 PM,

Section 8

Login ID: Hawkins
Entry Date: 06 Jun. 834
Location: Unto Nightfall, Ontario

Priority Report: Planet Sudbury, Ontario

On June 1, contact to one of our long-range probes in the Ontario system broke off. While this was initially dismissed as a simple malfunction, the rapid failure of the remaining four probes deployed across the system alerted our analytics team aboard the Atum. Analysis of the received data immediately prior to loss of contact revealed energy readings similar to those detected four years ago during the Pulse event originating from a point within the Ontario system. The Unto Nightfall was deployed to investigate.

Immediately following our departure for the Ontario system, the Atum received and forwarded an emergency broadcast originating from Fort Ramsey. The message indicated a hostile presence in the system, disconcertingly including Nomad warforms, as well as confirming suspicions of a hyperspace pulse being the cause of the probes' malfunctions.

Arriving in-system, the Unto Nightfall rendezvoused with Xeno Alliance Commander Cobra, who insisted on showing us rather than briefing us on the apparent cause of the system-wide blackout. We were joined by the warship FRS Roanoke and made best speed towards Planet Sudbury - a barren world with no atmosphere, located in the stellar northwest of the system. Our sensors picked up considerable traffic on the far side, and Cobra informed us that there was heavy fighting between local Xeno units and elements deployed by the Liberty Security Force, Technocracy, Bounty Hunters Guild, Lane Hackers, as well as Nomad warforms. We were further informed that the LSF battlecruiser LeHigh and a heavy DSE construction ship had arrived in-system via the partially repaired and hastily reactivated California jump gate.

Approaching Planet Sudbury, our scanner array began detecting unusual energy readings originating from its surface. The source of these readings appears to be an enormously powerful energy field, several hundred kilometers in diameter and visible to the naked eye, forming a hemispherical dome over a vast stretch of the planet's surface.

SysOps immediately commenced a detailed scan of the energy field and its source of emission, however, after several days of continuous scanning, observation, and analysis, even the Unto Nightfall's newly fitted Mark I Wiretap array could neither penetrate the energy field, determine its exact source, not discern what lies underneath. Scans were, however, able to discern that the dome formed by the energy field reaches under the planet's surface. The field's immense energy output caused significant wear and tear on our scanner and sensor suite, resulting in several malfunctions. While field repairs have thus far patched the damage our hardware has taken, spare parts, which the local Xenos are unable to provide, are already running low.

Further, Commander Cobra relayed anecdotal evidence of the field responding to certain audio frequencies. It is known that some artifacts of the Daam K'Vosh progenitor race respond to harmonic waveforms, i.e. musical notes, suggesting that the energy field and its source, too, are of Daam K'Vosh origin. The immense energy output - beyond what our own sensors could read - rules out any human-made construct, nor does it seem likely that it is Nomad in nature. Our own testing with modulated scanner frequencies emulating musical tones, however, resulted in no discernible alteration to the energy field's behavior.

Further discussion with Commander Cobra revealed that the local Xeno forces are under considerable pressure from the numerous newly present hostiles and that reinforcements from the Order were required. I informed him that the majority of Section 8's assets are currently occupied with ongoing operations and that the Order's resources were stretched similarly thin to his own. However, he insisted that the Order provide some form of support if it intended to secure the site of the planetary anomaly and prevent it from falling into the hands of the Liberty Security Force or Technocracy.

My personal recommendation is as follows: While the hunt for the infected battlecruiser Wyoming is of top priority, these new developments surrounding Planet Sudbury are of too great a significance to ignore. Whatever lies beneath the energy field is almost certainly of alien, likely Daam K'Vosh, origin, and must therefore not fall into the wrong hands, i.e. those of any party other than the Order. Commander Cobra has already expressed his desire to claim whatever is covered by the field for the Xenos' war efforts, believing it may be a technological cache. It stands to reason that the other present parties, particularly the Liberty Security Force and the Technocracy, share this assumption. While the energy field has thus far proven impenetrable by scanners and impervious even to heavy weapons fire, should the Order not act, it is only a matter of time before another party succeeds in gaining access to what lies beneath. Further, the sudden appearance of Nomads in the Ontario system - and thus in the immediate vicinity of major population centers in the California and Colorado systems - is a grave development almost certainly brought on by the activation of the energy field. Section 8 must secure the site and the alien threat must be thwarted before it can grow out of control and threaten Liberty's population.

Attachments

Belmont · (This post was last modified: 11-03-2024, 06:11 PM by Belmont.)

Section 8

Login ID: Captain Emrys Belmont
Entry Date: 09 OCT 834
Location: Ontario

Priority Report: Planet Sudbury, Ontario

Four days ago, our long range sensors detected a high-energy signal originating from Planet Sudbury. The Unto Nightfall launched from Fort Ramsey at once with the goal to investigate. The source of the signal was plain to see - quite literally.

The anomalous structure beneath the planet's surface appears to have entered a second phase of activation and has started emitting a high-intensity beam of energy into deep space. Initial calculations indicate a vector towards the galactic west. Astrometric analysis further suggests that the beam may intercept the neighboring Coronado system, though an exact vector cannot currently be determined due to the beam's unusual energetic nature. The light emitted by the beam remains within the visible spectrum for a length of circa thirty-five klicks before rapidly shifting into the non-visible spectra. Comparative analysis of the beam indicates readings consistent with patterns usually only found in the immediate vicinity of jump holes and jump gates and within hyperspatial tunnels. Due to this, I believe the energy beam may be propagating at a relative speed faster than light.

Where exactly the beam's energy is being drawn from remains undetermined, though visual scans indicate that it may be drawn directly from the planet's matter. I will have to leave the more detailed interpretation of the captured data to Analytics.

Radiation levels around Planet Sudbury and within the immediate vicinity of the anomaly and energy beam remain heightened but non-threatening. Close-up inspection of the planet's surface revealed further activity below the anomaly's energy shield. Images captured by our high resolution camera suite show a structure emerged from the planet's surface. Its geometry appears to resemble that of a pyramid or ziggurat. Due to the energy shield's all but impenetrable nature and intense interference, it is not yet possible to tell whether the structure is the source of the energy beam, nor what its purpose may be otherwise.

The cause for the the anomaly's sudden could not yet be ascertained, though reports from the Xenos indicate that the activation of the energy beam and emergence of the pyramidal structure on the planet's surface coincided with heavy fighting between LSF, Technocrat, presumed infected, and the Atum's own forces in orbit. It is possible that the anomaly's behavior is a result or even a reaction to this activity. Again, I will leave detailed interpretation to Analysis.

I have communicated with the Xeno Alliance's commander, Damien Morreti. He is well aware of the situation and the absolute necessity to establish complete control over Planet Sudbury through the expulsion of Libertonian, Technocrat, and alien forces. Combat will continue to be primarily handled by the Xenos, while it falls to us to carry on observation and analysis of the Sudbury anomaly.

I have relayed orders to Operative Prophet to scan the Coronado system for any traces of the high-energy beam.

Attachments

---

Belmont · (This post was last modified: 11-03-2024, 06:12 PM by Belmont.)

Section 8

Login ID: Captain Emrys Belmont
Entry Date: 12 OCT 834
Location: Ontario

Priority Report: Reconnaissance, Coronado

Upon the completion of Operative Prophet's task to reconnoiter the Coronado system, I am reporting following findings.

Shattered planetoid

Scouting the Coronado system for any potential traces of the high-energy beam being emitted by the Sudbury anomaly in the neighboring Ontario system, Operative Prophet came upon an exceptionally large formation within the Barrier Rim nebula. Located circa 20 klicks below the stellar plane, it appears to be the shattered remains of either an exceptionally large asteroid or a small planetoid.

Shattered planetoid

Operative Prophet's fighter is not equipped to conduct detailed geological analysis, so that collected data is limited to visual and basic surface scans, as well as electromagnetic readings. The formation consists of several large fragments, at a glance consistent with other rocky bodies found throughout the Barrier Rim. At the center of the formation, however, lies what appears to be a frozen core. Despite extreme closeup scans, the exact composition of this body could not be determined by Operative Prophet.

Frozen core

Of particular note are the following:

Firstly, the formation exhibits extremely heightened electrical activity, presenting as cascading lightning bolts flashing between and around the fragments. These electrical discharges are of sufficiently low voltage to not pose a threat to properly hardened vessels, though standard civilian craft may be damaged if struck directly.

Secondly, the asteroid's / planetoid's core is laced by a system of caverns. These are large enough for small craft to enter and explore. Operative Prophet, upon doing so, discovered an inner core within the frozen outer shell. This inner core, paradoxically, emits significant thermal radiation - not, however, to a degree that would pose a threat to spacecraft. The composition of this inner core could not be determined.

Hot inner core

Review of our astrographical database did not return any mention of this shattered planetoid. It is possible, of course, that it has not been previously discovered due to its well hidden location within the Barrier Rim. The cause of the planetoid's destruction is currently a mystery, as are the source of the electrical activity throughout the remains and the thermal activity within the inner core.

Alien gate

Three days ago, Vincent 'Caliban' Abrams approached the Unto Nightfall with a report of unidentified activity around the Knossos-type Nomad jump gate within the Barrier Rim. Abrams claimed that the structure was "rebuilding itself." The Unto Nightfall performed a hyperspace jump to the Coronado system to investigate and, if necessary, secure the site of the Nomad gate. Upon arrival and rendezvousing with Abrams and the Xeno Alliance Commander Cobra, the Unto Nightfall conducted a close inspection of the gate's remains.

Knossos-type jump gate

No activity - either alien or human - was observed. The gate itself remains derelict. Electromagnetic readings indicated heightened levels of radioactivity within the immediate vicinity of the ruins, though this is not unusual for technology of alien origin.

Abrams' claim regarding the Nomad gate could not be verified.

Conclusion

The sudden discovery of the unusual planetary fragments and the admittedly unverified claim by Abrams regarding sudden activity around the Nomad gate are likely unrelated to the activation of the Sudbury anomaly. However, there is a chance that these developments are not mere coincidence. Particularly Abrams' report on the Nomad jump gate seems uncannily well-timed when coupled with the calculated vector of the Sudbury anomaly's high-energy beam. I believe close observation of these matters should be a priority, and I have instructed Operative Prophet accordingly. Should the opportunity present itself, the Unto Nightfall will deploy to the Coronado system to perform more detailed scans of the shattered planetoid.

Attachments

Communication logs

Belmont · (This post was last modified: 11-03-2024, 06:12 PM by Belmont.)

Section 8

Login ID: Captain Emrys Belmont
Entry Date: 2 NOV 834
Location: Sigma-59

Incident Report: Operative Prophet

Yesterday, at 2044 hours SMT, we lost contact with Operative Prophet in the Shikoku system. He was en route to Noshima Freeport to rendezvous with a local informant. Twelve hours after loss of contact, our informant reported that Prophet had not yet arrived. Assuming he was ambushed by bounty hunters or Kusari authorities en route, I requested deployment of an SAR party from the Atum.

Two hours ago, Whistler squadron sited a debris field not far from Shikoku’s southern Keiun cloud. Serial numbers on the remains match Prophet’s ship. A sweep of the sector found no escape pod. A local police patrol forced Whistler squadron to retreat before a more thorough search could be conducted.

I have listed Operative Prophet as MIA. Should he not reestablish contact within seventy-two hours, he will be listed as KIA. The Atum has agreed to keep Whistler squadron on standby for extraction.

Attachments

---

S8 Operatives · 02-02-2025, 09:23 PM,

Section 8

Login ID: Lancer
Entry Date: 2 FEB 835
Location: Omicron Mu

Priority Report: Operation Heavy Rain

After two days of intense fighting throughout the Wall of Seth, Carthage stands!

As ordered, I redeployed to bolster the Fort's defenses and engaged the enemy. The Kusarians threw everything and the kitchen sink at us, but we ultimately succeeded in repelling their assault. I scored a few confirmed fighter and bomber kills myself, at the cost of several Anubises that ended up FUBAR, but that's small price to pay, if you ask me, and I'm certain High Command will agree, given the circumstances. Battlecruiser Sia took considerable damage but was able to withstand the assault and return to the drydocks for repairs. The Kusari flagship, IKN Hakodate, was destroyed for good. As it turns out, a battleship of that tonnage isn't made to fight in a dense asteroid field. The Naval Forces aren't fool enough to waste a ship so recklessly; it is all but certain that the Wild had their hand in her deployment. Losses on either side are ultimately a victory for the aliens and their thralls.

I hear the defense of Cairo fared worse. The Romales was lost. The Core employed drones of Gammu design - maybe even converted Gammu units. Reports are still coming in and what we know is far from certain, but it seems these drones turned on the Core forces. It may even be that the Mars was lost to them. Cairo may be beyond saving, but if this is true, it wasn't a complete defeat.

I hear the Unto Nightfall is scheduled to return to Carthage to survey the battlefield and receive maintenance in the drydocks. She'll have to wait in line. There's plenty of ships in need of repairs after this onslaught.

Yet Carthage stands.

Attachments

---

Section 8 - Content & Feedback

Section 8 · 07-15-2025, 01:17 PM,

Section 8

Login ID: Warlock
Entry Date: 15 JUL 835
Location: Ames Research Station, Kepler

Priority Report: Entity, Earhart

Yesterday, 14 July 835, I received an emergency transmission from Dr. Thallia Thorn. She reported to have come into contact with "a creature" in one of the systems periodically connected to the EARHART hyperspace pocket. How her transmission was even able to reach me from there I don't know - something for Analysis to figure out, perhaps.

With no jump-capable ship at my disposal and the Alaska super gate not being a viable means of ingress into EARHART, I made the decision to attempt traversal of the Gotha anomaly. I am aware that this was immensely dangerous, that research into the anomaly is still in its early stages, and that it serving as an alternative ingress point into EARHART is - or rather was - a purely hypothetical assumption. However, I succeeded. More data for Analysis to pore over.

I used our latest astrographical data to navigate the EARHART pocket and was able to locate an active "gate" to one of the connecting systems. I proceeded through the jump hole.

I entered an as of yet uncharted system. My nav-system was unable to determine its location relative to Sirius, nor chart a map of my immediate surroundings. In the immediate vicinity of the jump egress I picked up the following signatures:

Dr. Thallia Thorn (independent researcher)
Lazurith (former member of the Technocracy)
THR-Overseer.Unit-42-F (Gammu AI drone)
EC]-Theta-A81-1 (Gammu AI drone)
Entity (Nomad Simurgh-type form)

As it turned out, the "creature" Dr. Thorn had come into contact with was none other than Entity. I will refer to the report submitted by Dr. Thorn herself as to what occurred in the uncharted system immediately prior to my arrival.

Unsurprisingly, my presence was not tolerated by the Nomad, forcing Dr. Thorn and myself to extricate ourselves immediately. We jumped back to the EARHART pocket and made best speed to an egress point to the Cologne system, where Dr. Thorn hoped to lie low at Heisenberg Research Station. The jump back to Sirian realspace was successful, but we were immediately pursued by alien warforms. Scans matched our records of Sentinel forms. Seeking safe harbor on Heisenberg was no longer a viable option, so we set course for the Hamburg system, where I hoped we would be able to shake our pursuers. This proved unsuccessful.

I was forced to make the decision to escape to Liberty space, hoping to either lose the Sentinels along the way or lure them into the Ontario system, where I hoped Xeno Alliance pilots would be ready to engage. Despite constant harassment by Sentinel warforms, Dr. Thorn and I were able to reach our destination. A wing of Xenos, reinforced by militant and Lane Hacker vessels, was ready for our arrival and engaged the aliens. We were able to neutralize all targets with no casualties of our own.

Uncertain whether we were out of reach of further Sentinel attacks and unwilling to put Fort Ramsey in harm's way, I escorted Dr. Thorn to the Kepler system, where I hoped the dark matter storm would serve to hide us from further pursuit. We arrived at Ames Research Station with no further incidents.

Realizing that Dr. Thorn had come into direct contact with both the Nomads and the Gammu AI, I was forced to reveal myself to her. She admitted to "translating" between the AI drones and Entity - bypassing their inability to otherwise directly communicate with each other. Whether Dr. Thorn was coerced or obliged willingly - through being compromised or otherwise swayed to the aliens' side - remains unclear; however, past incidents of this nature indicate the latter. The topic of "conversation" between the Nomad and the AI drones was apparently the pylon at the center of the EARHART pocket. For further details, I again refer to Dr. Thorn's report.

How exactly Lazurith is involved in all this is uncertain, though his history suggests that he remains under Entity's influence.

I will keep Dr. Thorn under close observation aboard Ames Research Station until further orders are received.

- Warlock

Attachments

Incident Report [Dr. Thallia Thorn]

Information & Content

Section 8 · (This post was last modified: 08-25-2025, 09:45 PM by Section 8.)

Section 8

Login ID: Captain Emrys Belmont
Entry Date: 25 AUG 835
Location: Coronado

Incident Report: Operative Warlock

Today, at 2031 hours SMT, we lost contact with Operative Warlock in the Omega-55 system. He was en route to Bornholm Depot, from which he was to observe the local Core and Wild activity. His ship's last transmissions to HQ indicate that he was ambushed and attacked by unknown hostiles, possibly infectees. In accordance with protocol, his ship's onboard systems and flight recorder were purged prior to its destruction. Operative Warlock elected not to eject, preventing potential capture by unknown hostiles.

I have listed Operative Warlock as KIA; SAR deployments from Battleship Atum and Dabadoru Station have been recalled.

In service to humanity.

Attachments

---

Information & Content

Section 8 · (This post was last modified: 09-27-2025, 07:13 PM by Section 8.)

Section 8

Login ID: Emissary
Entry Date: 27 SEP 835
Location: Battleship Atum, Vespucci

Priority Report: Suspected Compromisation, 34th Brigade

Command,

Today, at circa 1620 hours SMT, I made contact with the 34th Brigade's agent Melusine near the moon Jericho in Coronado. Agent Melusine displayed signs of severe exhaustion, reportedly experiencing hallucinations - seeing another vessel that wasn't there. I attempted to convince her of reporting to Battleship Atum for a psychological checkup and some rest and recuperation, however, her mental state rapidly deteriorated. She began conversing with her hallucination. Lacking experience in field psychology, I was unable to get through to the agent beyond this point.

Agent Melusine then powered up her weapons and opened fire. Orders to stand down were ignored and I was forced to return fire, suspecting her of having succumbed to Nomad infestation. Another case among many in Coronado as of late.

To my surprise, Agent Melusine did, however, stand down after a brief engagement. I proceeded as per protocol, detaining her under the suspicion of treason or compromisation until reinforcements from Barrier Gate Station in the form of the 34th Brigade's Tau-4 could join us. Tau-4 assured me that Agent Melusine had not been compromised. Nevertheless, we proceeded to Battleship Atum, where Melusine was delivered for a full medical and psychological evaluation.

Tau-4 proceeded to offer the following explanation for what had taken place:

During its expedition into extra-Sirian space some years ago, the 34th Brigade suffered significant losses, including one Andry Scott, who was presumed KIA. Upon returning to Sirian space, all records of Andry Scott were purged from the Order's databases, save for physical documents in the possession of Jimmy Manderson. The events of this expedition - details were not provided - allegedly caused a collective trauma among the returning survivors. This trauma has recently escalated, resulting in physical altercations between veteran members of the 34th Brigade and culminating in today's incident. The working theory is that Andry Scott - whether dead or alive - is through unknown means influencing the minds of veterans of the Brigade's expedition. These episodes are allegedly temporary, resulting in no permanent loss of control comparable to Nomad enthrallment. So far, only members of the 34th Brigade have been affected, and it is assumed that only these individuals can be affected.

As far as I know, Atum's chief surgeon has cleared Agent Melusine for duty. There were no signs of alien compromisation. I, however, remain unconvinced. The story I was presented with is beyond far-fetched, even by our standards. I therefore continue to suspect Agent Melusine to be under Nomad influence and, judging by the poor attempt at an explanation by her comrade, this influence to have spread further into the 34th Brigade.

I recommend placing the 34th Brigade under close observation and to alert our allies within shared areas of operations of their possible compromisation.

Emissary, out.

Attachments

Information & Content

Login
Username:
Password:	Lost Password?
	Remember me