Discovery Gaming Community
34th Brigade - Reporting channel - Printable Version

+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Role-Playing (https://discoverygc.com/forums/forumdisplay.php?fid=9)
+--- Forum: Unofficial Factions and Groups (https://discoverygc.com/forums/forumdisplay.php?fid=67)
+--- Thread: 34th Brigade - Reporting channel (/showthread.php?tid=207498)

Pages: 1 2 3 4 5

RE: Hades Brigade - Reporting channel - Perfect Gentleman - 07-26-2025

[Image: Bez-nazvania81-20250108183317.png]



34TH BRIGADE REPORT MESSAGE
VESPUCCI SYSTEM, BATTLESHIP ATUM, 26/07/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - Medium | Recipient - Operations Tracking Department





VESPUCCI EXPLORATION OPERATIONS

The following report reflects the general state of the Vespucci system as of July 26, 835 A.S.

The exploration of the system began on July 23, a small research team was assembled, whose task was:

  1. Collect data on all large Insurgency/Fleet ships destroyed in Vespucci.
  2. Conduct an analysis of the system for the activity of third-party groups and the security forces of the Liberty Republic.
  3. Create a map of the system as of today, with an assessment of the tactical capabilities of the Order forces stationed in the system.

Assembled the team, we set off. The following regions became our areas of interest:
  • Planet Veracruz orbit.
  • Guerrero Cloud.*

* - Due to the interference of the cloud, it was decided to only examine the outer part of the cloud, and therefore all operations were carried out in the open space of the system.

System status at 26/07/835

As of July 26, 835 A.S, the Vespucci system is a vast battlefield of a long-ago battle, with numerous ship wrecks scattered both in orbit around the planet and along the Vespucci-Kansas route. This is consistent with previous data and news that Liberty launched her attack from the Kansas system, neglecting Magellan due to the minefield there preventing the transfer of large forces. The highest priority region of the system should be considered the orbit of the planet Veracruz, around which we have discovered multiple ship wrecks. All the most dramatic events of the recent assault took place right here. It is worth noting that the Insurgents were not the only ones who suffered losses: Liberty Fleet also failed to easily end the conflict, and the destroyed battleship Delaware is proof of this.

However, the ships on the Insurgency side are obsolete and beyond repair. Scans show that after the siege was over, the Liberty fleet made a fair amount of effort to "empty" the ships, leaving behind only the hulls of whatever they couldn't salvage. Alloy plating the ships would be suitable for both the Atum and Wyoming. None of these ships are beyond repair to "factory new" condition or nearly to that. If the large ships of the Insurgency or the Fleet that managed to survive the assault of Vespucci fell into the hands of the Nomads, they will turn to this field to bring them to a state of full combat readiness or nearly to that.

Third-parties operating in the system

The main visitors to the system are the ex-Insurgency forces (Hellfire Legion), Liberty Navy, LSF, Gaians. Occasionally, you can meet random explorers who, apparently, intend to find something valuable for themselves. The outcome of the meeting usually depends on how the representatives of one group or another behave. At the moment, everything looks like this:
  • Liberty Navy - Hostile. Do not make contact and intend to use weapons against the Order forces, labeling them as terrorists.
  • LSF - Neutral, inclined to negotiations and cooperation.
  • Hellfire Legion (TFP) - neutral, inclined to negotiations, were insisting of avoiding to enter the Guerrero cloud (see attached report - [2]).
  • Gaians - neutral, inclined to negotiations. The final status of relations will be established after negotiations between the Battleship Atum command and the Atacama station command.
  • Independent pilots - Mostly only interested in the work of the Order in the system. Do not show aggression and are rather led by their own curiosity.

Further work with any of these groups is more situational in nature and sometimes cannot correspond to the main agenda of current orders and operations.



The system map is already being actively created and should reflect the current state of affairs. Based on current data, I hereby believe that agents working in Vespucci should prioritize the following:

  1. Continue to investigate the system and establish contacts with local groups.
  2. Conduct a study of the Kansas system for appropriate analysis of the ship wrecks in that system.
  3. Begin preparations for the study of the Guerrero Cloud.

Also, I note that the ship wrecks are not suitable for their restoration and return to service. Key elements are missing, the ships are suitable only as a source of hull panels. These panels can be used to repair Atum, but these wrecks cannot have any other purpose. Even if we completely destroy all these ships, we will not achieve a tangible result: there are too many small fragments in the orbit of Veracruz, and therefore both we and anyone else will be able to use them. I hereby consider the part of the operation on the destruction of the wreckage to be irrelevant and unprofitable due to the possible financial costs and risk to the agents.

COMMANDER ALFRED SCHWARTZ
34TH HADES BRIGADE
26/07/835





ATTACHMENT FILES
  • [1] - 24/07/835 - Guerrero Cloud Analysis (For read only)
  • [2] - 24/07/835 - Vespucci patrol (For read only)
  • [3], [4] - 23/07/835 - Battleship Ravager wreck
  • [5], [6] - 23/07/835 - Insurgency cruiser wreck
  • [7] - 23/07/835 - VMS-Philadelphia wreck
  • [8] - 23/07/835 - Marshall Station wreck
  • [9] - 23/07/835 - INS-Chicago wreck
  • [10], [11], [12], [13], [14] - 23/07/835 - E/F4 Debris field

[+]Black box


RE: Hades Brigade - Reporting channel - SSV - 07-26-2025

[Image: Bez-nazvania81-20250108183317.png]



34TH BRIGADE REPORT MESSAGE
VESPUCCI SYSTEM, BATTLESHIP ATUM, 26/07/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - High | Recipient - Operations Tracking Department





VESPUCCI SYSTEM RECONAISSANCE MISSION


Mission Overview

On 26 Jul 835 A.S., I participated in a reconnaissance patrol of the Vespucci system under the command of Commander Alfred Schwartz. My primary assignment focused on locating, surveying and salvaging Liberty-origin weapon systems modified by the Insurgency and their Commonwealth allies for potential integration into Order assets. Secondary objectives included wreckage documentation, faction contact protocols, and tactical assessment of salvageable military technology.During the patrol, our team systematically examined five major wreckage sites containing remnants of the recent civil conflict:

VMS Philadelphia - Located in sector F-4, this transport craft was originally a separatist vessel repurposed to support Veracruz military industry. During its final operation, the Philadelphia desperately attempted to evacuate remaining ground-based personnel from the system. Both the ship and its escorts were destroyed when Navy reinforcements finally broke through the Insurgency defenses. The hull remains largely intact, though cargo bays have been gutted by previous salvage operations.

Gunboat Maine - Found in sector E-4, this vessel was once a crucial component of the Separatist defense forces in Bering. Having defended Marshall Station on numerous occasions, the Maine continued its protective role until the end. The gunboat was destroyed just before Marshall Station's fall Despite the catastrophic damage, many weapon components survived the explosive detachment and remained accessible for salvage.

Cruiser Chicago - Discovered in sector D-4, this vessel was one of the original participants in the separatist rebellion in New York. Having survived numerous battles with the Navy and other hostile forces, the Chicago represented one of the most loyal crews from its original battlegroup. The ship's destruction came when its engine room was hit during the initial skirmishes that would eventually doom Marshall Station. Evidence of attempted spot repairs was visible but proved futile against the sustained bombardment.

Avarice Wreck - Located at the Guerrero Cloud perimeter, this is the remains of a pirate freighter that strayed into the asteroid field and was subsequently destroyed, reportedly by Hellfire Legion patrols. The wreck was deliberately left in place as a warning to future trespassers. External plating shows heavy pitting from weapons fire, but interior power couplings remain largely undisturbed.

Battlecruiser Triton - Positioned in sector C-6, this vessel became the last surviving heavy warship in the Insurgency's devastated armada. The Triton was forced to engage Delaware's formation, which possessed superior numbers but lacked the cohesion and determination of their opposition. This engagement ultimately spelled Delaware's doom and shattered any notion of this campaign being an ideal victory for Liberty. The Insurgency's surviving forces achieved exactly what they had hoped for, exposing the image of an immortal Liberty as a fabrication. Despite this achievement, the Triton suffered catastrophic damage during the battle. The Commanding Officer died from blood loss after shrapnel wounds sustained during the engagement with Delaware. By the time the Ohio arrived to finish what Delaware should have waited for, the ship was little more than a drifting hulk.


Salvaged Insurgency Technology
My focused extractions concentrated on weapon, engine, and thruster subsystems unique to Insurgency retrofits. From the Triton's dorsal battery cluster, I successfully recovered an HFGx-04pl "Judgement" Plasma Cannon Mk II. This weapon system showed significant modifications from standard Liberty specifications, with enhanced power coupling and improved thermal management.From the Chicago's maneuvering section, I extracted an Insurgency Thruster assembly featuring enlarged thermal vents and modified exhaust routing. The design showed clear improvements over standard Liberty thruster technology, particularly in heat dissipation during extended maneuvers.The Maine's split stern section yielded an intact Insurgency Heavy Fighter Engine Mk I core housing complete with fuel injectors. Despite the vessel's destruction, the engine compartment had remained sealed, preserving the advanced propulsion system in salvageable condition.Additional components recovered included reinforced capacitor rings, modified coolant manifolds, and specialized heat-sink arrays that proved compatible with Order power-bus architecture.


Integration Into 042D "Bastet" Heavy Fighter
Upon return to Battleship Atum, I worked with the reverse-engineering team to integrate the recovered technology into my personal combat platform. The primary weapon upgrade involved installing the HFGx-04pl "Judgement" Plasma Cannon Mk II as a centerline mount, replacing one of my standard Order Class lasers. This modification provides eighteen percent increased hull damage per second and demonstrates superior shield-stripping capabilities compared to standard energy weapons.The Insurgency Thruster with reinforced vents was installed to replace my standard Bastet thruster system. This upgrade delivers six percent improved cruise acceleration and reduces heat build-up by four percent during sustained maneuvers, providing crucial tactical advantages during combat operations.The Insurgency Heavy Fighter Engine Mk I core was integrated with Order firmware to replace my existing engine. This modification provides five percent additional power-output headroom and significantly smoother afterburner cycling, enhancing overall flight performance.


Strategic Assessment
The mission revealed that Insurgency wrecks continue to house serviceable advanced hardware despite Liberty's post-battle salvage efforts. The modified Liberty plasma systems emphasize raw damage output over energy economy, but integration with Order cooling technology proves highly feasible and effective.The Guerrero Cloud perimeter continues to conceal valuable salvage opportunities, as evidenced by the relatively intact Avarice wreck. This suggests that patrol routes in the region remain porous and accessible to authorized salvage operations.The Vespucci system remains a contested graveyard containing substantial technological assets. A permanent Order presence is essential to deny these resources to Nomad forces or other hostile factions who might exploit the advanced military hardware for their own purposes.


Recommendations
Based on my findings, I recommend authorizing expanded salvage teams to secure remaining Insurgency weapon caches before hostile factions return to claim these assets.Deployment of sensor buoys around the C-6 and D-4 wreck grid would enable monitoring of scavenger traffic and possible Nomad interference. Additionally, a feasibility study should be initiated for towing intact gunboat and reactor sections to Atum's dry-docks for comprehensive parts harvesting operations.The successful integration of Insurgency technology into my Bastet heavy fighter demonstrates the viability of battlefield salvage operations for maintaining our technological edge against increasingly sophisticated opponents.




LIEUTENANT BEN HISLOP
34TH HADES BRIGADE
26/07/835






ATTACHMENT FILES
  • NONE

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 07-29-2025

[Image: Bez-nazvania81-20250108183317.png]



34TH BRIGADE REPORT MESSAGE
VESPUCCI, ATACAMA BASE, 29/07/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - High | Recipient - Operations Tracking Department





TECHNOCRACY AND ELDER NOMAD ENCOUNTER


28th of July, 835 AS. I moved out from Atacama base on standart patrol ruitine, including confirmation of the Liberty's and Insurgency's vessels wrecks. Patrol was proceeding as planned, until contact with the "Aletheia" Dunlin Retrofit Explorer was made. After a short conversation, it was confirmed that Thallia Thorn, an independant researcher who we met previously was commanding that vessel.

Shortly after, a contact appeared, flagged as Technocracy-affiliated "Revenant" - "Hawfinch" very heavy fighter. A conversation was conducted, as it was assumed them not being alone, given an encounter that occured a day before with a Technocracy-affiliated AI. During such conversation, the following was made clear:
  • Dr. Thorn is acquainted with Auxesia, at the very least - with the "Revenant".
  • "Revenant" is not hostile, at the very least - not aiming for the armed conflict.
  • "Revenant" is aware of the Order presence at Gallileo during the latest border escalations.
  • "Revenant" had multiple contacts with Nomads and the Elder Nomad entities. From their words - in agressive manner, mentioning being threatened to be melted into one of the human-Nomad hybrid technologies.
  • "Revenant" was giving away hint of them stealing a Nomad Powercell. As well as visiting the deep Omicrons.
  • "Revenant" is denying their infected status.
  • "Revenant" is planning to visit the Nomad "Homeland".

After said discoveries were made, my sensors registered an unknown contact. Neither "Revenant" or "Aletheia" noticed it. As I stayed vigilant, this occurance been mostly written off to local interferences. Yet shortly after this contact reappeared. Both "Revenant" and "Aletheia" reacted to it negatively, then - it was obvious why. An unidentified "cloud", there are no more fitting words for that, scanners did not come up any viable data about it.

Circumstances escalated quickly. That yet unidentified "Entity" made physical contact with "Aletheia" as more precisely - started to deforming and destroying the vessel's hull. This followed by multiple unknown contacts, a wing of the "Avenger"-class very heavy fighters. It was collectively decided to run off to Magellan . I followed in sake of not compromising our base of operations, continuing intelligence gathering and watching over the researcher, as loosing her to the Technocracy would be a wasteful decision.

Soon after our group moved to Leeds, aiming to conceal ourselves in it's West Smog Cloud and regroup. As the words of the "Revenant" went, "They're light, right? This cloud should dampen the effect. But let's get to safety away from the authorities, Halifax's smog cloud should be dense enough". Mentioning of that there is "No way to combat it at the moment", further enforced this plan.

Near the Halifax Freeport we encountered Bretonian warships, two "Churchill"-class Gunboats and a wing of "Crusader"-class very heavy fighters. Presumably - Bretonian Armed Forces, yet the timing of their appearance is too much of a coincidence. They engaged us immediately, situation was handled. Shortly after, some more data was discovered from conversations between us three:
  • The unidentified "Entity" is "one" of the Nomads' "Elders", named "Harbinger".
  • "Revenant" implied, that agents from the Overwatch and Section 8 are aware of the fact before. It was mentioned, that Section 8 became aware of it as a result of a "deal" with a Nomad.
  • "Harbinger" might have been attracted and "angered" at Dr. Thorn because of her denial to act as a "translator" between the said Nomad and A.I.s. As well as for her getting in posession of an unknown Nomad / K'Vosh "artifact", picked up from one of the "Uncharted" systems. From one of the K'Vosh sites, or sub-relays, as the "Revenant" called them. The "artifact" itself is located somewhere yet unknown.
  • "Revenant" mentioned, that there is "No point" for the "Harbinger" in the hunt for Dr. Thorn, as there is no time for it. An answer to a logical question aimed to get an explanation was answered with that "Everything's is a ticking bomb".
  • Dr. Thorn mentioned, that A.I.s involved need monitoring, assuming that not all of their kind is afflicted with contact to "Harbinger", with "Revenant" confirming this statement.

Then "Revenant" suggested visiting Dublin, as it was uncovered later - for Dr. Thorn to scan the anomaly in the debris of a destroyed Jump Gate. For this trip we were accompanied by ACV-"Halcyon", a "Judicator"-class cruiser commanded by someone named "Leviathan", also Technocracy-affiliated.

As we decided to move out from the Halifax Freeport's proximity, another Armed Force's patrol showed up, closing in to our position. As before, thay attacked instantly, yet we managed to escape into New London system via a jump hole nearby. The rest of the way to Dublin jump hole was univentful, yet right at it - we encountered an another patrol, escape was just as successful.

In the Dublin system itself, no hostile encounters were met, Dr. Thorn conducted her scans successfully, yet she needs time to put those into any valuable and clear data. Except of her supposing that "the rift" is opening. After such, it was decided to go back.

On our return to the New London system and our way to Magellan through Manchester we were encountered by "Mako"-class Battleship it's affiliation, nor it's status in terms of being controlled by AI is not clear. The warship was destroyed.

As we made our way to Magellan, Technocrats went into Vespucci first. On my and Dr. Thorn's short stop near the jump hole, we again were encountered by a wing of "Avengers" that were mentioned earlier. The situation was handled. In Vespucci system itself, a similar fight with another pack of "Avengers" broke out, resolved with the same success. The conversations there were not containing any practical meaning, yet they will be included.

After breaking contact with Technocrats, I have returned back to Atacama base.



LIEUTENANT ANDREA D'ARCE
34TH HADES BRIGADE
29/07/835





ATTACHMENT FILES
  • [1] - 28/07/835 - "Harbinger" sighting;
  • [2]. [3] - 28/07/835 - "Revenant" and [b]ACV-"Halcyon";
  • [4], [5], [6] - 28/07/835, 29/07/835 - Hostiles: Bretonian group, "Mako", Libertonian group;
  • [7] - 29/07/835 - Dublin Jump Gate anomaly.

[+]Black box


RE: Hades Brigade - Reporting channel - Firb - 08-04-2025

[Image: Bez-nazvania81-20250108183317.png]



34TH BRIGADE REPORT MESSAGE
VESPUCCI SYSTEM, BATTLESHIP ATUM, 04/08/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - Medium| Recipient - Operations Tracking Department





KANSAS SYSTEM EXPLORATION


This report covers the patrol of the Kansas system, conducted alongside Agents "Anubis" and "Melusine". Prior to the operation, I was stationed at Barrier Gate in the Coronado system. After receiving mission details, I left the station and moved to our meeting point in Vespucci via the following route: Coronado → Inverness → Ontario → California → Magellan → Vespucci. During my flight, I encountered two independent traders near Planet Los Angeles. No contact was initiated, but a brief scan revealed nothing suspicious in their cargo holds.

Upon arrival in Vespucci, I moved to Atacama Station, where Agents "Anubis" and "Melusine" were already waiting. After a quick resupply, our team initiated the operation and moved toward the Kansas system jump hole.

After entering Kansas, the first notable object we encountered was an abandoned Liberty Navy battlecruiser. The cause of its derelict state remains unclear. Scans confirmed the absence of life signs, and the vessel's systems were either destroyed or missing entirely. Like other wrecks observed later, it was deemed unrecoverable or not worth the cost of salvage. We continued our investigation through the debris fields. Among the destroyed ships were several Liberty Navy and Insurgency vessels. Eventually, we arrived at the remains of Fort Riley.

Historical records indicate that the Insurgency had anticipated a full-scale joint offensive by Liberty and Bretonia against Vespucci. In preparation, they consolidated forces from multiple stations to establish a unified defense. However, the offensive did not proceed as expected: only a small Bretonian detachment, consisting mostly of destroyers, arrived — Liberty’s fleet never joined. The Bretonian unit was defeated with surprising ease, leaving major installations like Fort Riley and Mulvane Station vulnerable. Both were later overrun by Liberty forces during a high-intensity siege spearheaded by the Delaware battlegroup.

After scanning Fort Riley, we moved to Planet Wichita. The planet is nearly entirely covered in ocean, with only scattered islands breaching the surface. These landmasses host the ruins of several failed colonization attempts. In orbit, we found several wrecks — a mix of Liberty Navy vessels and fighters. Agent Melusine conducted a perimeter sweep, but no unusual signals or anomalies were detected.

Our final stop was the wreck of Mulvane Station, orbiting the gas giant Planet Topeka. Among the debris, we discovered a destroyed Insurgency cruiser and — notably — a still-operational communication satellite. According to our analysis, this satellite predates Liberty's offensive in the region and was not constructed by Libertonian forces.

After completing our scans and recording the site, we returned to Vespucci without incident. All collected visual records and location coordinates are attached to this report.

LIEUTENANT JESSE HUGHES
34TH HADES BRIGADE
04/08/835





ATTACHMENT FILES
  • [1] - Liberty Battlecruiser near Vespucci Jump Hole.
    [2] - Wrecks of Insurgency Cruiser destroyed by collision with Liberty Cruiser.
    [3] - Abandoned Liberty Cruiser near Fort Riley Wreck.
    [4] - Abandoned Liberty Battlecruiser near Planet Witchita.
    [5], [6] - Station Mulvane wrecks and Satellite near it.

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 08-08-2025

[Image: 411.png]



34TH BRIGADE REPORT MESSAGE
VESPUCCI, BATTLESHIP ATUM, 08/08/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - High | Recipient - Operations Tracking Department





PATROL DUTY, 06/08-07/08

This report concludes two days of patrols, both 6th and 7th of August.

6th of August, 835 A.S.:
  • My route was concluded from flying through the Vespucci system, which proved to be stable and univentful, as well as the way through Kansas and Pennsylvania with the following route into Texas. All the way was performed using Jump Holes and moving through clouds/debris fields, combined with using a Cloaking Module.

    However, on the contrary to rather quiet situation in other systems, Texas proved to be troubling. By unknown reasons, if not specutaliting, a Nomad fleet was spotted in the proximity of Planet Houston, composed of snubcraft units, as well as those comparable to gunships, cruisers, battlecruisers and battleships. Direct involvement in combat was not necessary, since Liberty Navy warships and LSF agents have assembled a fitting defence organization, proving an effective repelling and destruction of the attacking fleet.

    In the proximity of California Jump Hole, I was attacked by the group of Kusarian "Wyvern"-class fighters, without any intelligeble IFF signatures, nor any communications to catch. Presumably, this wing was the survivors of the past battle. Or connected to another occasion which will be described next.

    Thereafter, upon returning into Pennsylvania system, an encounter with the so-called "Entity" took place. The Nomad appeared to be observing, not putting on any agressive actions towards me. After a brief visual contact, it disappeared, wether entering hidden state or shifting in space, that is up to speculation. On my way back, no sign of it's presence was registered neither visually or by scanners.

    Upon my arrival on Atum, I willingly reported this encounter. Thereafter, I was investigated by the standart protocols, including scanning and psychological tests, all of those proving clear state of mind and body.
7th of August, 835 A.S.:
  • This patrol concluded similar route to the day before. And, as similary Vespucci and Kansas were empty and uneventful, Pennsylvania was a hot point this day.

    Using the Cloaking Module, I broke distance with Planet Erie, with my attention caught by the battle raging on in it's proximity. The fight was compositioned of two sides: for one it were Liberty Navy with the assistance of LSF agents, and for the opposing side - Tas Force Prometheus warships, along with the assistance of the Technocracy and, surprisingly, two vessels of The Platform.

    The outcome of this battle was decided in Liberty's favor.

    This concludes the report, since all the possible reasons and explanations of the both events, regardless of the parties taking part in those, are nothing more than speculations.


LIEUTENANT ANDREA D'ARCE
34TH HADES BRIGADE | 411TH WING
08/08/835





ATTACHMENT FILES
  • [1] - 06/08/835 - Houston battle;
  • [2] - 06/08/835 - Kusarians;
  • [3] - 06/08/835 - Entity encounter.
  • [3], [4] - 07/08/835 - Erie battle, The Platform's presence.

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 08-15-2025

[Image: 411.png]



34TH BRIGADE REPORT MESSAGE
VESPUCCI, BATTLESHIP ATUM, 15/08/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - Medium | Recipient - Operations Tracking Department





11/08/835 INTELLIGENCE COLLECTION

As the subject suggests, this report is a conclusion of the latest events, cherry-picked from various encounters and conversations. All of which were conducted on "Melusine" - signed ship. Transparency of my alligeance, be it with neutral or hostile entities, proved to be a useful tool, paired with staying away from dangerous and inconvinient encounters with the use of cloaking module.

To start off, at planet Veracruz's orbit, members of a group named "New Dawn" were met, two of them, tagged as "Lilith" (pilot's name - Siara Solantra) and "Crimson Queen". From their own description and from the words of others - they are a zoner-militant group, that opposes Liberty's interests in Pennsylvania. Their ideology is based on anarchistic principles, comparable to one's of "The Platform".

Soon after I have met the militants, "Falkenhorst", a Hel-class cruiser of the said "Platform" arrived, with "Crimson Veil" Bastet-class heavy fighter of the same affiliation soon undocking from the internal hangar. From the conversations of those two groups it was made clear - "The Platform" will openly assist militants in their fight for planet Erie and Pennsylvania as a whole.

After a short conversation, an LSF pilot callsigned "Sigma-7" appeared, turning immedeately hostile towards the militants, yet was quick to deal with.

Later that day, I went out on a patrol, once again meeting said militants and the "Falkenhorst". An vessel then appeared, which was tagged as an Outcast by the IFF systems of my ship, yet no communication was made, as said ship continued to gather scrap from planet Veracruz' orbit - presumably a junker with a broken or/and stolen transponder device.

Also, a freelancer callsigned as "Vengeance" was present on the scene, notably - piloting a Nightjar-class very heavy fighter. Questioning was not conducted, since "Halcyon", a Vindicator-class cruiser affiliated with the Technocracy and commanded by Navarch Leviathan appeared. From since I was monitoring the situation from bigger distance. What was certain, is that the "New Dawn" militants and Auxesia are holding a mutual-defence pact between each other.

Since that - no other details to report on, as I continue to monitor the situation.



LIEUTENANT ANDREA D'ARCE
34TH HADES BRIGADE | 411TH WING
15/08/835





ATTACHMENT FILES
  • [1] - 11/08/835 - "Vengeance" Nightjar.

[+]Black box


RE: Hades Brigade - Reporting channel - Perfect Gentleman - 08-17-2025

[Image: Rework2-Clear.png]



34TH BRIGADE REPORT MESSAGE
OMICRON DELTA, DABADORU STATION, 17/08/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - Medium | Recipient - Operations Tracking Department





ENTITY RESEARCH

The attached report reflects all the characteristics of the alien Nomad object "Entity". The report lists all files and known encounters, behavior, and potential long-term threats. The scientific data is based on witness statements and recordings obtained from "Blackjack" ship (piloted by Lieutenant Alex Russel) blackbox on August 12, 835 A.S.

DESCRIPTION

Entity (referred to by some individuals or groups as “The Harbinger”) - A creature of Nomad origin, representing an energy signature of impressive width, capable of transporting unidentified Nomad ships and other vessels (or their copies) into the known space of the Sirius sector. The Entity also possesses the standard Nomad means of communication - telepathy - which limits its communication with Gammu AI and forces it to use human intermediaries[1]. The Entity has two states, each of which can be determined visually. First state allows one to recognize in the Entity the outlines and known signs characteristic of Nomad vessels[2], [3], [4]. The second state usually (and most often) opens when the Entity begins active movement and resembles the movement of a huge cloud of unknown origin[5].

Unlike other Nomad ships, the Entity does not use any weapons, but prefers to transport unidentified ships into its space of presence either for communication or to engage in direct combat with those it deems dangerous. The ships can be either of Sirian origin[6], [7] or typical Nomad vessels[8]. It is still unclear why the Entity creates copies of ships known to us, but the most likely is an attempt to establish communication (see [Report about Entity, by Aspirant Victor Bruno]).

CHARACTERISTICS AND ABILITIES

  1. Signature: Entity ship is not a physical object, and therefore the use of standard types of weapons is ineffective. However, with sufficient density of fire, the cloud dissipates, which negatively affects the Entity. This allows us to judge the physical origin of the cloud, which is the basis of the Entity.
  2. Speed: The ship has high speed indicators, which can be compared to the parameters of well-known racing engines. Due to the technological development of the Nomads, the speed of the Entity can be much higher. Note: all small Nomad ships (Light Fighters, Heavy Fighters, Very Heavy Fighters and Bombers) that appear in space by Entity have such speed[9]. The use of standard cruise disrupters also has no effect[10].
  3. Weapons: The Entity does not carry standard Nomad weapons or anything resembling it. Instead of this Entity sending human and Nomad ships of unknown origin straight to the Sirius sector.
  4. Communication: Standard Nomad telepathic abilities and related ones.
  5. Known abilities of the Entity:
    • Using the Nomad cloaking device.
    • Transfer of ships to the Sirius sector. The transferred ships can be either of Sirian origin or Nomad vessels. In theory, the transfer is carried out using hyper-technology (see [Report about Entity, by Senior Scientist Koji Yasu]). Nomad ships created by the Entity use beam weapons[11], which are effective mainly at short range. This type of weapon is used on ships smaller than a gunboat[12], all others use standard weapons[13]. The Entity is also capable of returning ships back[14].
    • The ability to create copies of ships of known models, including those of non-human origin (Gammu AI).

The Entity's energy signature suggests that the size and number of ships being transferred is affecting the Entity and preventing it from being constantly active. It is likely that the transfer of ships is draining energy, and this is directly related to the Entity's distance from the supposed "source" from which it draws ships.

ZONES OF ACTIVITY AND REGISTERED MEETINGS

Reports of the Entity have been circulating in the Order since before the events of today, which suggests that this creature has been in the Sirius sector for a long time. The potential damage this creature could cause to humanity is unclear and most likely non-existent: not a single major clash between the Order and the Nomads or known factions with the Nomads has been accompanied by the presence of the Entity.

The Entity generally visits random locations in the Sirius sector, which does not lead to any global consequences. The encounters are random and rarely go beyond a couple of sectors of one system. In rare cases, the Entity purposefully moves between systems, pursuing someone it considers either dangerous or an object for its study. The frequency of the Entity's appearance has increased since the events of the Blackout[15], which may be directly related to the Erhart system and its nature[16].

Cases of encounters with the Entity that the 34th Brigade has information about to date:
  1. Omicron Beta encounter with Gammu AI.[1]
  2. Earhart and Sigma-19 encounter with Gammu AI and Phoenix Zoners.[17]
  3. Omicron Delta and Omicron Pi encounter with Gammu AI and Phoenix Zoners.[16]
  4. Vespucci encounter with Lieutenant Andrea D'Arce and Technocracy.[18]
  5. Omicron Delta encounter with Lieutenant Alex Russel, Commander Kunrad Amhrad, Phoenix Zoners and Eclipse Vanguard.[19]

FURTHER INVESTIGATION

Using all the information above and the data that was obtained during the last meeting with the Entity in Omicron Delta, I have every reason to believe that this will not be the last meeting. Despite the reports of the destruction of such an object - it would be reckless to assume that it would be destroyed by such simple methods as a standard weapon. However, this is only my assumption as a scientist, and hasty conclusions should not be made.

The entity also mentioned the features of the Earhart system and ways to bypass the protective platforms located in the center of the system. It is believed that the platforms have a system for identifying emerging threats and react to them with a certain pattern, the so-called "feature", which all humans and Gammu AI have. What specific feature is being discussed - we have yet to find out. However, if we can deceive the platforms' defense mechanism, we will be able to get to the center of the system and study the unknown structure in more detail.

As stated earlier, the Entity is not invincible. The use of standard weapons shows that the cloud can dissipate, allowing us to better study its physical properties and draw our own conclusions.[20], [21]

SCIENTIST JINNA LEONS
34TH HADES BRIGADE
17/08/835





ATTACHMENT FILES
  • [1]     - 27/06/835 - To: Order| E\V/ 34th || From: Phoenix (Attachment document "Theta-A81", for read only)
  • [2], [3], [4] - 12/08/835 - Encounters with Entity (by Lieutenant Alex Russel, for read only)
  • [5] - 28/07/835 - "Harbinger" sighting ("Technocracy and Elder Nomad encounter" report by Lieutenant Andrea D'Arce, for read only)
  • [6], [7] - 28/07/835, 29/07/835 - Hostiles: Bretonian group, "Mako", Libertonian group ("Technocracy and Elder Nomad encounter" report by Lieutenant Andrea D'Arce, for read only)
  • [8] - 12/08/835 - "Silver Yellow" Nomad signature (by Lieutenant Alex Russel, for read only)
  • [9], [10] - 12/08/835 - Entity Nomad vessels speed and cruise disruptor launch (by Lieutenant Alex Russel, for read only)
  • [11], [12], [13] - 12/08/835 - Difference in weapons, Nomad encounters in Omicron Delta (by Lieutenant Alex Russel, for read only)
  • [14] - 12/08/835 - "Sigma Alpha" Nomad Battleship encounter (by Lieutenant Alex Russel, for read only)
  • [15] - 06/10/831 - "Sirius shaken by mass Jump Gate blackout" (by Colony News Service, for read only)
  • [16] - 08/07/835 - To: Order| E\V/ 34th || From: Phoenix (Attachment document "Dr. Shinji Kano", for read only)
  • [17] - 27/06/835 - To: Order| E\V/ 34th || From: Phoenix (Attachment document "Dr. Elias Voss", for read only)
  • [18] - 29/07/835 - "Technocracy and Elder Nomad encounter" report (by Lieutenant Andrea D'Arce, for read only)
  • [19] - In this case, the report itself is direct evidence of a meeting with the Entity in Omicron Delta. It also sets out all the details of the past meetings and the characteristics of the Entity as a phenomenon.
  • [20], [21] - 12/08/835 - Using standart weapons against Entity (by Lieutenant Alex Russel, for read only)

[+]Report about Entity, by Aspirant Victor Bruno
[+]Report about Entity, by Senior Scientist Koji Yasu


RE: Hades Brigade - Reporting channel - Lamor - 08-18-2025

[Image: 341.png]



34TH BRIGADE REPORT MESSAGE
CORONADO, BARRIER GATE, 18/08/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - High | Recipient - Operations Tracking Department





OPERATION #835-8 COMPLETION

Yesterday our group received orders to meet and escort a pilot with the call sign «Anubis». We needed to meet him in the Cortez system and provide them with cover until the jump hole in Coronado. These sectors were especially dangerous due to the rather large activity of the Technocracy, so we had to be ready to react as quickly as possible. Our assumptions were not in vain: several enemy fighters appeared in the system and attacked our ships near the jump hole in Coronado. We quickly headed to the necessary point and engaged the enemy.

The results of this incident are as follows:
  • our group responded quickly enough to provide the most effective resistance to the enemy;
  • the enemy was a group of several very heavy fighters;
  • during this battle, all Technocracy vessels were eliminated;
  • the Order ships provided the most effective resistance and not a single fighter on our side was shot down;
  • all pilots successfully reached their destination.

Although we have successfully completed the task, the danger of Technocracy's influence in the Independent Worlds remains very high.

ENSIGN WILLIAM ECKERT
34TH HADES BRIGADE | 341ST WING
18/08/835





ATTACHMENT FILES
  • NONE

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 08-21-2025

[Image: 411.png]



34TH BRIGADE REPORT MESSAGE
VESPUCCI, BATTLESHIP ATUM, 21/08/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - Medium | Recipient - Operations Tracking Department





KEPLER-ALBERTA INVESTIGATION

As was planned before and due to low activity in sectors that are designated by the order of commander Amhrad, yesterday's flight was aimed for Kepler. The path there was uneventful, no hostile nor friendly encounters occured along the way.

I have entered the system from Colorado, as the way from here was the most convinient and safe. Kepler itself greeted me no different from anyone else - dark matter storm was as dangerous as before, apart from thin corridors inside which I followed. Using partial nav-data and buoys installed by zoners from Ames.

First stop was the "Prophet". A curious anomaly by itself, yet my path was headed to the northern reaches. I found my way around the anomaly, but after - it was a series of mistakes and successes in proceeding forward.

The further I went - the less navigation systems were relevant. With luck, I've found the second stop, the buoys "in the middle", vaguely hinting the road. Up to this point the hull of my ship held up nicely, proving the toughness of Bastet in harsh conditions of space around.

The next stop was the anomaly itself. Visual will ba attached, yet to describe it with words: the sight was reminiscent of standart collapsed Jump Holes, yet differences are notable with less deteriorations of the collapsed one, The gravitational pull of the anomaly felt weaker than usual, as well as sensors were not reading the usual collapse signs. Though, it is up to debate and closer inspection to determine wether it is true or not.

The way back was more difficult than to the anomaly's position. Navigational systems gave out, so I had to blindly find the relativaly safe corridor. Upon reaching the "middle buoys", the hull started to deteriorate, failing to oppose the dark matter around. Reactor let out a leak, stting the ship on fire, though, I managed to make it as controlled as possible. Systems were failing, therefore I had no choice but stop by Ames once I made it out from the North of Kepler.

The ship's condition was far from optimal, yet the repairs were possible. And once those were made to the point of no risk for the vessel to fall apart along the way, I have made the run for return. The way back to Atum was as uneventful as before.

Conclusions of the science team will be attached:


From the little, but still relevant data that was extracted by lieutenant d'Arce, the following can be drawn as more or less certain facts:
  • The anomaly to the North of Kepler is, indeed, a phenomenon known by the public as a Jump Hole, the electromagnetic readings are similar to which are recorded near the more stable and usual ones;
  • Though this particular anomaly differs from the reading we can get near Collapsed Jump Holes, for example - a closer one in Sonora Ice field;
  • All the differences may or not occured from the envolvement of dark matter in the space around the observed phenomenon, at least said matter is known to be connected to other examples of big enough catastrophies involving Jump Gates and Jump Holes alike.
If we are to theorise, keeping in mind the data about wrecks of infected vessels that were found in that area of the system, our conclusion might be as facinating as concerning in the same time. The noted difference of Alberta's Jump Hole can lead us to assuming the low but not zero possibility of re-opening this passage. The information from those Wilds' wrecks themselves could be useful to point out a more accurate theory based on their goals.
The other though that comes to mind, is speculating about the Blackout, Pulse and Dallas incident as a whole, yet that would be too much speculation before any reliable assumptions.
We do not assume, that flooding Kepler with the dark matter is caused by this particular anomaly, yet theoretically it can be connected with this two occasions, as well as with the Blackout and similar catastrophie regarding the Dallas incident.




LIEUTENANT ANDREA D'ARCE
34TH HADES BRIGADE | 411TH WING
21/08/835





ATTACHMENT FILES
  • [1], [2] - 20/08/835 - Visual contact with the remnants of Alberta Jump Hole, recording of the sensors' readings.

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 08-28-2025

[Image: 411.png]



34TH BRIGADE REPORT MESSAGE
VESPUCCI, BATTLESHIP ATUM, 28/08/835
This message is compiled from templates compiled by the 34th Brigade security division and approved by Order High Command effective April 2, 835 A.S. Transmission of the message into the hands of third parties is authorized with the written permission of the Brigade Commander or the Brigade Commandants. Any other cases will be considered a crime against the Order and will be punished in accordance with the law on violation of the secrecy provisions of internal communication. Attempting to change the internal code of the message will be treated the same way.
Priority - High | Recipient - Operations Tracking Department





UNCHARTED-4 EXPLORATION

On the 27th of August, 835 A.S., I moved out, as it was planned, into Earhart. Using a cloaking module and gaps between patrols, I made my way into the system, meeting with Dr.Thorn on the other side. There, she guided me to a jumphole leading to Uncharted 4 system.

The system itself is covered in a nebula of some sort, dramatically slowing down the movements, also containing large crystallic formations. Our way through it was risky, as the space around had highly radiated pockets, posing danger similar to Kepler's storms. The path was found, the navigational data is recorded and saved. We found another jumphole, leading to the unknown system beyond the 4th Uncharted one.

Following place was different. Instead of red nebula there was clouds of leftover dark matter, with an unidentified object at the center. As we proceeded further, dark matter clouds were becoming more dense, yet not unstable or charged enough to pose any danger. The final destination was a broken alien structure, similar to Earhart's pillars.

Upon inspection, it was concluded, that it contains damaged cores of some sort, probably - filled with the dark matter. That would explain the clouds around and, probably, the cloud present in Earhart. The main difference between this column and ones from before - the absence
of it's core. I assume, that the object in this system's center is a missing part in question.

Soon after, Revenant of the Auxesia appeared. Now it was evident that Technocracy, more or less, is aware of things that happen all around. She was mentioning "connecting" this pillar to the others, that there is not much time to decide, since "it's a mistake that we could get here in the first place and all this machinations are faultering".
Also it was mentioned, that Nomads, assumingly, the Harbinger, are after the solution to this puzzle as well. Since this column's purpose is unknown, the next move to figuring out what this machines are - is to figure out this one "subrelay's" purpose.

Then Dr. Thorn showed that her physical condition worsened. As Atum's medical crew concluded - severe exhaustion. I couldn't risk it with eliminating Revenant, as her ship better survived the trip there, Thorn's condition wasn't getting better and the last thing that we needed - is to leave her alone with a technocrat.

Our trip back was safe enough. One of the Earhart's paths into Sirius led to Vespucci. After making sure that we are not followed, we set our course to Atum.

LIEUTENANT ANDREA D'ARCE
34TH HADES BRIGADE | 411TH WING
28/08/835





ATTACHMENT FILES
  • [1], [2], [3] - 27/08/835 - Crystallic formations in Uncharted-4; Jumphole into the system "beyond"; Flight data, referencing the route;
  • [4] - 27/08/835 - The object at the system's centre;
  • [5], [6] - 27/08/835 - The pillar and it's containment core.

[+]Black box