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 - 09-03-2025

[Image: 341.png]



34TH BRIGADE REPORT MESSAGE
CORONADO, BARRIER GATE, 03/09/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





CORONADO TACTICAL RECONNAISSANCE

The report is a complete overview of the tactical situation in the Coronado system as of August 31, 835. The report reflects general details after documented encounters.

As of August 31, 835 A.S, Coronado system had become another disputed area for a number of factions and states, as had been the case with the Ontario system. This was due to the activation of the planet Jericho, a satellite of the planet Salina, after being hit by a beam coming from the planet Sudbury. According to order 835-1-5, our task (341st wing) was to analysis the Coronado system to determine the extent of third party influence and their capabilities in relation to the planet Jericho.

GENERAL OVERVIEW

The main participants in the events of the last few days were several groups (including those hostile to The Order), neutral Freelancers and random individuals who either fell under the negative influence of the EMP impulse or were flying past and decided to find out the circumstances of what was happening. The list below shows a list of organizations that are directly interested in the situation around the planet Jericho and are not giving up their attempts to obtain information about Daam'Kvosh structures:
  • Crayter Republic: Several flights have been sent to check the area around the planet Jericho. Large forces have not been deployed, reinforcements are expected. A number of official statements have been made regarding the EMP-strike on the system, and measures have been taken to deal with the sudden increase in radiation levels on the planet Yuma.

  • Liberty Republic: LSF vessels have been dispatched, and based on recent encounters, may attempt to seize control of the planet from third parties (including the Crayter Republic) to conduct their own investigation. Similarities can be drawn to the planet Sudbury in Ontario. Republic has made official statements about Coronado and about helping Crayter in difficult times. However, due to the growing conflict with Kusari, serious reinforcements should not be expected. There is a possibility of cooperation with agents from the LSF.

  • Task Force Prometheus: Technocracy military formation, positioning themselves as ex-Legionnaires who survived the siege of the planet Veracruz about 6 years ago. They brought in large forces once, as part of a humanitarian mission. Among the ships of this group, an Osiris-class battleship was spotted[1]. The name of the vessel refers to the times of the old Hellfire Legion. Due to the information available about the suspected infection of the unit[2], the first battle between the 34th Brigade and Prometheus took place during a humanitarian mission, where LSF agents sided with the Order. After the victory, Prometheus forces did not appear in Coronado again. It is believed that the enemy is working on its mistakes and intends to send larger forces, eventually.

  • Technocracy of Auxo: Have made and continue to make multiple attempts to investigate the planet Jericho for their own purposes[3]. The forces of the 34th Brigade have had several previous encounters with the Technocracy both in Coronado and beyond[4]. It is believed that the Technocracy has prioritized investigating Jericho, as the 34th Brigade currently does.

  • Bundshuh (Platform): They were seen once in orbit of the planet Jericho. They do not have a high interest in this planet and can rather be considered "random passers-by", since they have not made any attempts to enter orbit since then.

  • Independent Miners Guild: Following the Jericho incident, several official statements have been made about increased difficulties in operations on Pecos. The withdrawal of claims to Jericho is expected, given recent events and possible mutual pressure from Crayter and Liberty. IMG have not yet visited the orbit of Jericho, and therefore their position relative to this planet remains unknown.

All the rest are already related to individual personalities, the mention of which is inappropriate, due to their zero influence on what is happening around the planet Jericho. Basically, these are random observers or independent researchers. The main participants in the theater of operations around Jericho can be considered:
  • Liberty Republic;
  • Crayter Republic;
  • The Order;
  • Technocracy.

CORONADO TACTICAL OVERVIEW

The situation in the Coronado system quickly descended into a state of panic, which was caused by an unexpected EMP strike on the system, during which the gate leading to Cortez was damaged[5]. There is a direct threat of losing contact between Coronado and other states. Since Coronado is also home to Lane Hackers and Outcasts, as well as independent pirates, there will be increased disruption to humanitarian missions to the orbit of the planet Yuma. Theoretically, the IMG and Technocracy could also resort to similar tactics to increase their influence in the orbit of the planet Jericho.

An attempt to create a stable transit between Coronado and Cortez with the mediation of Liberty and Bretonia cannot be ruled out, against the backdrop of the increased border threat of Wendigo and the events in Jericho. As stated earlier, Crayter has urgently sent a small force into orbit around the planet Jericho, but has not attempted a full-scale blockade of the planet's orbit from third parties. According to the latest news, the Yuma government intends to place all forces on high alert.

Otherwise, the situation in Coronado is unsettled and will not be for the next few months or even years. The map below shows all patrols and routes inside Coronado:

[Image: Coronado.png]

  • Crayter Republic has increased its patrols between the Cortez Jump Gates and the planet Yuma, and has moved additional forces to the planet Jericho.
  • Technocracy uses the Barrier Rim and the Sierra Vesta Nebula to fly beyond the visibility of patrols from hostile organizations and groups, and to refuel and repair their ships at the Barrier Gate. After a meeting in the motorcade system, one can rightly assume that technocracy has sufficient opportunities for free movement inside the coronado and beyond.
  • Liberty Republic is beefing up the defenses around the gate to Cortez, and is also sending ships to the planet Jericho on a regular basis. These are mostly small scout units.
  • IMG are not deviating from the work plan set for September, and therefore their routes have not changed, except that they have now completely excluded the trajectory through Jericho.

FURTHER WORK

Tactical analysis indicates increased instability in the Coronado system. Given our limited resources, I hereby recommend that the 34th Brigade HQ direct all efforts to the planet Jericho and establish close liaison with Liberty, Crayter, and IMG representatives regarding the continued blockade of the planet's orbit from outsiders. At the moment we are collecting all the data on the planet Jericho and awaiting further orders and plans for the planet.

COMMANDER WALDEMAR OTTO
34TH HADES BRIGADE | 341ST WING
03/09/835





ATTACHMENT FILES
  • [1] - 26/08/835 - HFB-Incursus scan data, by Commander Waldemar Otto (for read only);
  • [2] - 22/07/835 - To: 34th Hades Brigade, Subj: Task Force Prometheus (for read only);
  • [3] - 24/08/835 - "Technocracy vessel contact" recording, by Commander Alfred Schwartz (for read only);
  • [4] - 18/08/835 - "Operation #835-8 completion", by Ensign William Eckert (for read only);
  • [5] - 23/08/835 - "Coronado lightings" recording, by Commander Alfred Schwartz (for read only);
  • [6] - 27/08/835 - "Tau-31 Jump Hole" recording, by Commander Waldemar Otto (for read only);
  • [7] - 27/08/835 - "Coronado Jump Hole" recording, by Commander Waldemar Otto (for read only);
  • [8] - 27/08/835 - "Travel to Yuma planet" recording, by Commander Waldemar Otto (for read only);
  • [9] - 03/09/835 - Coronado tactical map, by Commander Alfred Schwartz (for read only).

[+]Black box


RE: Hades Brigade - Reporting channel - mijuu09 - 09-07-2025

[Image: Rework2-Clear.png]



34TH BRIGADE REPORT MESSAGE
THURINGIA,TENNSTELD BASE, 07/09/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





OPERATION #835-9 COMPLETION - 07/09/835

This report covers the patrol beginning in Omicron Delta and concluding at Tennsteld Base in the Thuringia system. The operation was carried out by agents 34th|O’Reilly, 34th|SD-Wanderer, 34th|Rogue, and 34th|Nephthy.

Our departure point was Dabadoru Station in Omicron Delta. Following final checks , the team set course for the Thuringia system. The route carried us through Omicron Kappa, Omicron Theta, Omegas and Dresden, where we were met by (=)"Falkenhorst" an Bundschuh agent. This agent offered both guidance and safe passage through contested sectors, ensuring that our movement remained uninterrupted.

Upon arrival in Thuringia, the (=)"Falkenhorst" extended further assistance, granting our wing docking privileges at Tennsteld Base. The base personnel provided full hospitality, including berth assignments and access to local logistical support. No hostile encounters were recorded during the approach or docking procedures. He also answered some questions about the Earhart system, which seems a little dangerous.


The mission concluded without incident, and all agents returned to readiness status at Tennsteld Base.

ENSIGN SEAN O'REILLY
34TH HADES BRIGADE
07/09/835





ATTACHMENT FILES
  • [1] - 29/08/835 - Flying to Thuringia
  • [2] - 29/08/835 - Omega-41
  • [3] - 29/08/835 - Meeting (=)"Falkenhorst"
  • [4] - 29/08/835 - Arrival to Tennsteld Base



[+]Black box


RE: Hades Brigade - Reporting channel - Lamor - 09-09-2025

[Image: 341.png]



34TH BRIGADE REPORT MESSAGE
CORONADO, BARRIER GATE, 09/09/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 - Low | Recipient - Operations Tracking Department





CORONADO SEARCH OPERATION - 06/09/835

On September 6, the 341st Wing too part in an operation to search for the lost IMG cruiser “Cuba” in the Coronado system. The meeting was held in orbit around the planet Pecos, where further actions were discussed. In addition to our agents, there were also many other people seeking to find the missing ship and, if possible, rescue the surviving crew members.

Our first target was the Barrier Rim area. The only thing that was found were fragments of a ship, probably belonging to our target. It was likely that the ship could have remained in this area, so I, together with "Tau-4", headed towards the jump hole in Tau-31, located at the other end of the nebula.

Finding no ship or other clues, we left Barrier Rim and began searching for the ship in the open part of the system, and then moved on to the Sierra Vista cloud. Ultimately, it was there, on the outskirts of the nebula, that the Cuba was found. Rescue ships quickly arrived at the scene.

The results of the operation are as follows:
  • The cruiser "Cuba" was found in the Sierra Vista cloud area;
  • The ship was seriously damaged, most of the crew were died, and some of the survivors were seriously injured;
  • A large number of people took part in the operation. They made a huge contribution to finding the ship, evacuating and rescuing the survivors;
  • The 341st Wing successfully escorted the rescue ship to Barrier Gate;
  • The ship probably sustained serious damage as a result of colliding with asteroids due to the aftermath of the EMP explosion from the Jericho.

After escorting the ship with the wounded, we landed at Barrier Gate. The 341st Wing continues to monitor the situation in the system.



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





ATTACHMENT FILES
  • [1] - 06/09/835 - Flight to Pecos
  • [2], [3], [4], [5] - 06/09/835 - Ship scanning
  • [6] - 06/09/835 - IMG Cruiser "Cuba".

[+]Black box


RE: Hades Brigade - Reporting channel - HussarCorsair - 09-10-2025

[Image: Rework2-Clear.png]



34TH BRIGADE REPORT MESSAGE
"CAYMAN", LINER "INTREPID MAIDEN", 09/09/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





DEEP OMEGAS PRELIMINARY ACTION REPORT

Previously stationed in Thuringia, I received a priority transmission to rendevousz with 34th's Rogue, Xander, and Nephthys for new assignment. We regrouped and rearmed at Tennstedt Base, and then made course for co-ordinates in Omega-47. Rogue briefed us on the way, stating that the Order had received information about new systems with intermittent access in the far reaches of the Walker Nebula. An access point to these systems was to be found at our destination. Our orders were to perform reconnaissance in force and report our findings. Unfortunately, my own guncam was nonoperational due to the hazards of Thuriniga. Footage of the Deep Omegas should follow with Commander Amhrad's report.


Our wing proceeded to the coordinates in O-47 where we encountered the first of the anomalies that would come to be a staple of the Deep Omegas. All such anomalies lead into these new systems, and seemed to have intermittent phase-alignment. Generally speaking, all of the systems were desolate except for other newcomers' and their outposts. Our wing encountered a Corsair depot, a Coalition "Tempest"-class carrier, Zoners with their liner in the first system, Unaffiliated pilots, and- most concerning- confirmed infectees wielding hybrid technology and fielding "Donau"-class cruisers.


The most noteworthy encounter was our encounter with a freelance explorer piloting a civilian ferry. Order Primary fleet agent Matthew McKinley got to him first, and was escorting the ship out of the Deep Omegas when we arrived on scene The ferry had somehow gotten an anomalous structure stuck inside its cargo hold, something that warranted the pilot's pursuit by infected elements. Our wing and Agent McKinley made short work of the infectees and successfully escaped to the Zoner liner Intrepid Maiden. Here we are hoping to debrief the ferry pilot and either extract the object in his hold or take his ship into custody if that proves impossible with our current facilities. All relevant correspondence has been attached below.




ENSIGN ASTRID WEBER
34TH HADES BRIGADE
09/09/835





ATTACHMENT FILES
  • None

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 09-22-2025

[Image: 411.png]



34TH BRIGADE REPORT MESSAGE
OMICRON DELTA, DABADORU STATION, 22/09/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





DEFECTED AGENT ENCOUNTER

This day, me and Raven went out on a routine patrol mission around Omicron Delta.

Immediately when we left the vicinity of Dabadoru Station an Order Agent, piloting a Bastet Mk.II class heavy fighter. Transponder flagged as "Andry Scott". During communication with the said agent, he showed symptoms of psychosis and seemed like he was aware of the past assignments of the Brigade. Something called The Abyss was mentioned, as well as the names of 34th's veterans, including captain Helson, commander Schwartz and senior scientist Yasu. After a brief conversation the agent engaged and was put down.

COMMANDER KUNRAD AMHRAD
34TH HADES BRIGADE | 411TH WING
22/09/835





ATTACHMENT FILES
  • [1] - 22/09/835 - Fight with vessel flagged as "Andry Scott".

[+]Black box


RE: Hades Brigade - Reporting channel - Lamor - 09-24-2025

[Image: Rework2-Clear.png]



34TH BRIGADE REPORT MESSAGE
OMICRON DELTA, DABADORU STATION, 24/09/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





EARHART EXPLORATION

This report reflects the situation regarding Earhart as of September 17, 835. The report contains information obtained as a result of an expedition conducted by agents 34th|Rogue, 34th|SD-Wanderer, and 34th|Nephthys.

On September 17, 835, our group was ready to depart for Earhart. After meeting at Tennstedt Base, we headed for the jump hole we needed, which led directly to our destination. The rift was located inside the planet Gotha, practically at the core, so we took advantage of it immediately, as the radiation level in this area was incredibly high.

EARHART. GENERAL PROVISIONS

We arrived there in a few seconds, and the first thing we saw were two structures in the center, forming a glow between them. Approaching these objects is currently extremely dangerous, as they are protected by surrounding objects that resemble defensive turrets in their functionality and are capable of striking targets from a considerable distance. Thanks to the small size of our ships, we managed to dodge their beams, but it would have been too dangerous to get any closer. Moreover, the scanners did not return any results regarding these objects and displayed a garbled set of symbols. In addition to these structures, there was an incredible amount of ship debris and even fragments from the station in the system. All the ships were of different classes, ranging from fighters to capital ships. In addition to this, we discovered some ships that can be attributed to the Nomads, which may serve as confirmation that the defense system also perceives them as a threat. It is worth noting that during the entire period of our research, we did not encounter a single functioning ship.

In addition to these objects, we noticed other structures resembling jump gates in shape, and we were right. After analyzing these objects, we found that the following systems can be accessed from Earhart:
  • Omicron Delta;
  • Tau-37;
  • Uncharted 3;
  • Uncharted 5.

It is also worth noting that it is not possible to return to Thuringia from Earhart via the same route we took to reach the designated system. Also, when leaving Earhart for other Sirius systems, it is not possible to return the same way, which is not typical for the Uncharted systems, from where we were able to successfully return to Erhart through a jump hole.

UNCHARTED 5

As part of our expedition, we decided to use these gates and jumped to Uncharted 5. Interestingly, we discovered an object there, similar in its characteristics to a jump hole, surrounded by debris from an unknown structure. Our scanners were unable to predict where this rift led, so we decided not to use it. In the same system, we also discovered another fragment at the other end of the asteroid field, probably related to the debris around the rift, but we have not yet been able to determine what kind of structure it was. After returning to the Earhart, we continued our exploration of the system and stumbled upon the gate. After analyzing it, we determined that it led to Uncharted 3, so we decided to use it.

UNCHARTED 3

Upon arrival at the site, we discovered an object that initially resembled a polygonal shape, but it was not static and constantly changed its form. We also noticed two structures, probably supplying the object in the center. Unlike Earhart, these structures do not have any protective systems, but they generate a great deal of radiation over a large area. As in the case of the object in Earhart, our scanners were unable to provide any data. We also noticed smaller spherical structures around these buildings, arranged in a circle around the object. They probably serve as generators for the structure in the center. It is worth noting that among these small spherical structures, there was one that stood out from the rest - it was rotated in a different position and appeared to be damaged. In addition, we noticed a cluster of organic substances around it; analysis showed that these were organic capacitors.

EXPEDITION RESULTS. FURTHER PLANS

We have outlined the main points concerning the situation in Earhart and the Uncharted systems. To study the processes taking place in Earhart, we will need time to observe and analyze the situation. However, we suspect that the functionality of the jump holes may be artificial and controlled, as Earhart is directly linked to incidents of ships disappearing during hyperjumps, which is why we observed a large number of them in this system. Thanks to this expedition, we analyzed the routes into and out of Earhart, which will allow us to return there unhindered for further analysis and research.


ENSIGN ROBERT HENDERSON
34TH HADES BRIGADE
24/09/835





ATTACHMENT FILES
  • [1] - 17/09/835 - Earhart structures;
  • [2], [3], [4], [5] - 17/09/835 - Jump holes in Earhart;
  • [6] - 17/09/835 - The rift in the Uncharted 5;
  • [7] - 17/09/835 - Found fragment;
  • [8] - 17/09/835 - Structures in the Uncharted 3;
  • [9] - 17/09/835 - Damaged part of structure;
  • [10] - 17/09/835 - Samples extracted from the structure.

[+]Black box


RE: Hades Brigade - Reporting channel - Perfect Gentleman - 09-27-2025

[Image: Rework2-Clear.png]



34TH BRIGADE REPORT MESSAGE
OMICRON DELTA, DABADORU STATION, 27/09/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





ADDITIONAL INFORMATION TO "EARHART EXPLORATION" REPORT

For the sake of information security, I am attaching additional files to Ensign Robert Henderson's report. I hereby advise that I have no further comment regarding the flight to the Earhart system, as I deem it necessary to include this information in Mission #1-835.

SCIENTIST JINNA LEONS
34TH HADES BRIGADE
27/09/835





ATTACHMENT FILES
  • [1] - 18/09/835 - Uncharted 5 damaged gates;
  • [2] - 18/09/835 - Uncharted 3 damaged structure;
  • [3] - 18/09/835 - Uncharted 3 mining operation;
  • [4] - 18/09/835 - LCC Bell video recordings;
  • [5], [6] - 18/09/835 - Uncharted 5 photage;
  • [7], [8], [9], [10], [11], [12] - 18/09/835 - Earhart photage;
  • [13] - 18/09/835 - Uncharted 3 photage.

[+]Black box


RE: 34th Brigade - Reporting channel - Perfect Gentleman - 10-18-2025

[Image: 341.png]



34TH BRIGADE REPORT MESSAGE
CORONADO SYSTEM, BARRIER GATE, 18/10/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





ATUM TRANSFER TO THE CORONADO SYSTEM

OPERATION OVERVIEW


This report details the transfer of the battleship Atum to the Coronado system.

The escort group included forces from the Order, as well as the Gaians, who responded to the call for assistance in exchange for certain guarantees of continued assistance from Atum's commander, Admiral Nilsen. The 341st Wing had arrived three days earlier, on October 2, 835 A.S.

The primary objective was to transfer Atum to the Coronado system, where the Gaian forces would leave the escort group in the Magellan system. In Cortez, Atum would reunite with Crayter forces and continue directly to the Sabah shipyard in orbit around the planet Yuma. The 341st Wing was planned to act as a reconnaissance group, intercepting hostile ships before they made direct contact with the battleship.

The ship's transfer was successful, though not without losses among the escort group's personnel and critical damage to the battleship. Attached is a timeline of the events as of October 5, 835 A.S.

CHRONOLOGY, 05/10/835

  • 17:35 - Ships from the 341st Wing and Commander Oliver Moss ("Seth") rendezvous at the battleship Atum in the Vespucci system. Escort group formation is underway.
  • 17:50 - Preparing for takeoff, receiving final orders and setting the final route point. Transfer of the route sheet to the support group.
  • 18:02 - Battleship Atum and its escort group begin moving towards the orbit of the planet Veracruz.
  • 18:10 - 341st Wing and "Seth" are deployed to the planet's orbit to conduct reconnaissance. Other Order agents not affiliated with the 34th Brigade are also participating in the mission.
  • 18:12 - First fire contact with large enemy forces in orbit around Veracruz. Atum performs a gravity assist maneuver, giving it speed and allowing it to successfully head toward the Magellan system. The battleship takes no damage.
  • 18:20 - Atum makes a successful jump to the Magellan system. In square E6, the battleship suffers its first minor damage. The 341st Wing delays the attacking forces and then returns to the battleship to provide additional support.
  • 18:27 - First encounter with Crayter and Liberty Fleet forces in the The Barrier Cloud. Both sides provide battleship support. Another wave of attackers is repelled. The enemy is rotating its forces for another strike.
  • 18:50 - Atum arrives in the Cortez system. Gaians abandon the escort group at Magellan as planned, handing over the battleship's protection mission to Crayter and Liberty. The enemy is using all its forces to inflict maximum damage on battleship. The 341st Wing is forced to provide constant fire support to Atum. The ship sustains moderate damage, raising the risk of the operation being disrupted.
  • 19:10 - The battleship Atum arrives in the Coronado system. Damage is nearing critical, and the mission continues.
  • 19:20 - Atum reaches the planet Baja under heavy enemy fire. The infected continue their attempts to inflict as much damage as possible on the battleship. The final firefight leads to the emergency activation of the cloaking device and Atum's withdrawal from the battle, heading for the Sabah shipyard.
  • 19:30 - The last of the infected forces were destroyed in orbit around the planet Baja. The 341st Wing returns to the Barrier Gate for rest and new orders. The mission is now considered a success.

FURTHER MISSIONS OF 341ST WING


Orders received from Admiral Nilsen indicate support for the battleship while it was undergoing repairs. The 341st Wing took a three-day rest period and then returned to duty on October 8, 835 A.S. Currently, the battleship is supported by Crayter forces, the 46th Fleet, and Order patrols (including the 341st Wing).

It is assumed that the infested will visit again to finally destroy Atum. Liberty's presence is no less suspicious. However, no incidents between them and the Order have yet been observed. The arrival of the Order battleship has also generated considerable media attention, which will not go unnoticed by other Houses in the Sirius sector. It is planned that the battleship will complete its repairs as soon as possible and then move on to other areas of interest. Until then, the 341st Wing provides support to local patrol groups and the 351st Wing, which is working to explore the planet Jericho.

COMMANDER WALDEMAR OTTO
34TH BRIGADE | 341ST WING
18/10/835





ATTACHMENT FILES
  • N/A

[+]Black box


RE: 34th Brigade - Reporting channel - Perfect Gentleman - 11-05-2025

[Image: 341.png]



34TH BRIGADE REPORT MESSAGE
CORONADO SYSTEM, BARRIER GATE, 05/11/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





ADDITIONAL INFORMATION TO REPORT OF 18/10/835

I hereby attach additional information to the report of 18/10/835 - "ATUM TRANSFER TO THE CORONADO SYSTEM".

The attached files contain a list of suspected infested individuals involved in the attack on the battleship during its transfer to the Coronado system. I urge Brigade Headquarters to review this list and forward it to other Order agents, as well as to designate the targets as hostile by default.

COMMANDER WALDEMAR OTTO
34TH BRIGADE | 341ST WING
05/11/835





ATTACHMENT FILES
  • [1] - 28/10/835 - Flora's external communication to 34th Brigade, Subject: The List (For read only)
  • [2] - 28/10/835 - Flora's attached video-material of Atum escort operation (For read only)
  • [3] - 05/11/835 - To: Flora, Subject: Full list (by Commander Waldemar Otto, for read only)


RE: 34th Brigade - Reporting channel - Perfect Gentleman - 12-03-2025

[Image: Rework2-Clear.png]



34TH BRIGADE REPORT MESSAGE
OMICRON DELTA, DABADORU STATION, 03/12/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 REPORT - OMICRON DELTA - 03/12/835

On December 2, 835 A.S., I conducted a 24-hour overflight of the Omicron Delta system to search for suspicious ships, objects, and individuals. I followed the route sheet transmitted to me from 34th Brigade Headquarters two hours earlier, and after I had replaced the previous Order patrol.

Patrols proceeded calmly until I visited the Palau Ice Cloud, where several suspicious individuals were detected, directly identifying themselves as members of the Core (as indicated by their transponders). These individuals were exploiting Omicron Delta's direct link to Omicron Pi (and the planet Knossos, respectively) to smuggle Xeno Relics into[1] known Sirian space, sending them to known organizations and installations[2] for further sorting. The Core pilots were not friendly, and they reacted negatively to my demand to leave Palau space.

The enemy force at the time of the engagement was as follows:
  • R-01 - R1 "Draugr" Edge Worlds Miner
  • Alcore005 - R1 "Draugr" Edge Worlds Miner
  • MarsMiner - Enterprise 20 "Rhino" Liberty Civilian Freighter

A battle ensued between us, during which one of the enemy ships (MarsMiner) docked with a station also affiliated with the Core[3]. This same individual had previously mined ice in Palau, ostensibly for subsequent transport to Nauru. His emergency docking with this installation confirmed my suspicions that the Core had a station in this region. During the battle, all hostile vessels were destroyed and I've returned to the Dabadoru station for emergency repairs. After 2 hours my patrol continued with no incident.

All data is attached below.

LIEUTENANT ALEX RUSSEL
34TH BRIGADE | 351ST WING
03/12/835





ATTACHMENT FILES
  • [1] - 02/12/835 - R-01 scan data;
  • [2] - 02/12/835 - R-01 docking at Core installation - "Grootegeluk Depot";
  • [3] - 02/12/835 - Core installation - "Corporate Shipping Airways-D" - in Palau Ice Cloud.

[+]Black box