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

34th Brigade - Reporting channel - 34th Brigade - 04-01-2025

34TH BRIGADE REPORTING CHANNEL
All reports within the Brigade are left here, according to a compiled template. Please do not disregard it, in order to avoid damage to the coding and further declassification of the document for third parties. Distribution of the contents of the documents is only permitted with the written agreement of the Brigade Commander or the Brigade Commendants. Any attempt to pass information into the hands of third parties will be considered an attempt at sabotage or a violation of the secrecy provisions within the Order. This will be punished in accordance with the relevant laws.

Jimmy Manderson Wrote:"- The more incorrect reports there are, the more the person making them will be reprimanded."


[+]Template - 351st Wing
[+]Template - 341st Wing
[+]Template - 411th Wing


RE: Hades Brigade - Reporting channel - 34th Brigade - 04-01-2025

[Image: Bez-nazvania81-20250108183317.png]



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





REPORT EXAMPLE

This is where you write information about what happened. You should include the time, who was with you and the circumstances of what happened. As you fill out the report, you write dryly, briefly, clearly and concisely. Without any emotionality, but using official terminology.

For example, “The enemy runned away” is an example of an incorrect fill-in. Whereas “The enemy was forced to retreat” is correct. You approach the rest of your reports with similar logic.

At the end of the report you state how it ended. If you have any additional details that require a narrative at the end of the report, you write it at the end of the report, not in the middle, so that the context is not lost.

ASPIRANT JIMMY MANDERSON
34TH HADES BRIGADE
01/04/835





ATTACHMENT FILES
  • [1], [2], [3]... - 01/04/835 - You adding files here and naming it. Because we need to know what we're looking at.

[+]Black box


RE: Hades Brigade - Reporting channel - Perfect Gentleman - 04-12-2025

[Image: Bez-nazvania81-20250108183317.png]



34TH BRIGADE REPORT MESSAGE
VESPUCCI SYSTEM, BATTLESHIP ATUM, 12/04/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





WYOMING CHASE OPERATION REPORT

This report reflects events that occurred during the search and destroy operation of the Battlecruiser Wyoming in the Ontario system by the Battleship Atum at the time of March 30, 835 A.S. Preliminary orders associated with this report refer to when the escalation between the Liberty Free Republic (LFR) and the LSF was at its peak, which in turn increased Nomad and Infectees activity. Intelligence readings and increased frequency of engagement made it clear that the number of alien opponent signatures was only increasing. It also signaled that Wyoming would soon abandon its position and try to get out of Atum strike again.

The orders were as follows:
  • All forces operating in neighboring systems to return to Battleship Atum immediately.
  • Freighter "Odyssey" should maintain his previous position.
  • Agent "Monolith" maintains his position in the Coronado system and continues to monitor sensor readings.
  • Senior Scientist Koji Yasu remains on Battleship Atum, not leaving under any circumstances.
  • Ships operating in the Ontario system, temporarily assigned to Battleship Atum, should start the necessary preparations for a future engagement.

The occasion for the chase to continue was the culmination of LSF and LFR forces conflict in the Ontario system, which leaded to a clash between both sides at the recently reactivated gateway to the California system. Taking advantage of the clogged radio airwaves and the full involvement of both sides in the mutual conflict, Wyoming withdrew from positions near the South Ontario Debris Field. As soon as the data from the advance parties was received, Atum and all the escort vessels, according to the above orders and the order of battle formation, began the pursuit of the warship, expecting to destroy it.

CHASING OPERATION DETAILS

Further information is provided by specifying the timing of events prior to the onset of the battle.
  • 16:20 - The first reports of hostilities at the Jump Gates to California have been received. LFR and LSF are the main participants in the battle. The presence of third parties (except Hackers) is not detected.
  • 17:00 - Multiple reports from Battleship Atum patrols of a number of encounters with Nomad forces in the south. Given the enemy's tactics, it was concluded that the Wyoming was about to leave the system and the attacking forces were intended as a diversion.
  • 17:43 - The first report from one of the scouting parties, indicating a Wyoming location. The ship has left its position and is about to emerge from the wreckage. All Order forces are on full alert and begin moving towards the enemy ship. Atum acts as the flagship of the fleet.
  • 18:09 - Atum discovers Wyoming, the enemy manages to impose on the battle.
  • 18:30 - The accompanying Wyoming force is outnumbered, the enemy ship is under heavy fire. The Atum takes moderate damage.
  • 18:35 - Two large Nomad signatures appear on sensors, the enemy ships engage with additional reinforcements and win the opportunity to activate the hyper rift taking the Wyoming into the Vespucci system (this was discovered after the battleship Atum and other Order ships jumped in).
  • 18:40 - After making the jump and proceeding into the system, the battleship Atum encounters reinforcements of Nomad forces in the system. A fierce battle ensues in orbit around the planet Veracruz.
  • 19:10 - The alien forces manage to push back the battleship Atum and the attack group, which allows the cruiser Wyoming a window to escape the pursuit. Battleship Atum uses a cloaking device to also escape the attack (at this point the battleship also received serious damage).
  • 19:20 - Sensors on Atum and other escort ships no longer register hostile signatures, and both sides have finally broken off combat.
  • 22:35 - Atum is forced to come out of disguise near the Atacama Station, which belongs to the Gaians. Conflict is avoided, and both sides begin negotiations. The presence of Nomad forces was still not detected.

OPERATION RESULTS

Brief summary of the chase results:
  • Battleship Atum suffers serious damage.
  • Battlecruiser Wyoming suffers serious damage.
  • Both sides disengage from the battle in orbit of planet Veracruz.
  • Additional information is received about the presence of infected forces in the Vespucci system. These same forces provided support to Wyoming during the battle at Veracruz.

According to the latest data, the Nomads and Infectees presence in the Ontario system has been reduced, but the Nomads themselves are still continuing to explore the system, which is directly related to the anomaly on the planet Sudbury. In addition, the battle cruiser Tuscaloosa was transferred to the orbit of the planet Sudbury for more radical methods of its exploration. It was the transfer of this cruiser that served as a pretext for the LFR to launch an attack on the gate to California when it would be most vulnerable.

At this point, Wyoming's fate remains uncertain, other than the fact that the enemy has once again managed to slip away. Atum also requires repairs, the success of which is directly dependent on the outcome of negotiations with the Gaians in Vespucci. 34th Brigade forces sent to the Atum battleship earlier remain on board and, at the time of writing, have completed the repair and maintenance process on their ships, allowing them to resume active combat operations if necessary.

The key figure in the Sudbury exploration operation, Koji Yasu, did not sustain any serious injuries during the battle. However, his distance from the planet puts further exploration in question, which is why he needs to travel to Ontario as quickly as possible and with a ship equipped to receive data from beacons in orbit and on the planet's surface.

Further orders will be announced later.

COMMANDER ALFRED SCHWARTZ
34TH HADES BRIGADE
12/04/835





ATTACHMENT FILES
  • NONE

[+]Black box


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

[Image: Bez-nazvania81-20250108183317.png]



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





PATROL

The patrol began in the Omicron Delta system, launching from Dabadoru Station, where I arrived to meet with one of the Brigade pilots — Agent Blackjack. After receiving brief instructions, we proceeded through Omicron Kappa en route to the Omicron Theta system.

While transiting through Kappa, we encountered a Coalition transport vessel. We established contact with the captain and inquired about the purpose of their presence. During the exchange, the captain mentioned ships allegedly infected. As a precaution, we escorted the vessel to Freeport 11 to verify access codes and request additional data. I provided my Neural-ID to receive any encrypted information from the crew. I am currently awaiting the transfer of those logs, which will be forwarded to Command upon receipt.

After the operation, the vessel continued on its route, and we returned to Theta. The remainder of the patrol was uneventful. We returned to Dabadoru Station and concluded the patrol.

Contact with a potentially valuable source of information has been established. Confirmation of possible infected activity in the region is pending.

ENSIGN LEX HALE
34TH HADES BRIGADE
19/04/835





ATTACHMENT FILES
  • NONE

[+]Black box


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

[Image: Bez-nazvania81-20250108183317.png]



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





PATROL, OMICRON DELTA BORDER CONTROL

Patrol mission was conducted under Blackjack's command. After the order from Dabadoru station, I joined up with the crew at Omicron Theta, including callsign Raven. The route has passed uneventful, excluding small skirmishes against small Wilds, Nomads and the Core patrols and ended in Omicron Delta.
On the other hand, upon arrival in Delta, our squad encountered several ships and conducted routine scanning operations. As Raven and, upon his arrival, Cronos-2, were working on Zoners and GMS vessels, myself and Blackjack questioned the corsair pilot. Scanning showed three signatures in his cargohold, two of them identified as saved Bounty Hunters lifepods, but the third was called Wild by the corsair himself. Apparently, he picked up the pod after hostile encounter, he presumed his prisoner's affiliation. The escape pod was transferred to Blackjack's cargohold without resistance and then moved to Dabadoru station.


ENSIGN KUNRAD AMHRAD
34TH HADES BRIGADE
07/05/835





ATTACHMENT FILES
  • [1] - 07/05/835 - scanning_results_0705835_corsair_spike

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 05-17-2025

[Image: Bez-nazvania81-20250108183317.png]



34TH BRIGADE REPORT MESSAGE
OMICRON DELTA, DABADORU STATION, 17/05/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-1 - PYGAR ARTIFACTS EXTRACT

On the day of 14.05.835, me and agent Hale recieved operation details. It was already some time since the job was actual, so we decided not to waste a minute more. As the mission stated, me, as callsign Rogue, accompanied by callsign Raven, teamed up at Dabadoru and flew out for our task. The way to Pygar was uneventful, and I wouldn't call it bad. We've met up with the scientist, who was in control of their side of operation and recieved 4 packages, containing 25 units of artifacts each. Then, packages were shared between Raven's and mine cargoholds as 2 by 2. We took off of Pygar and then headed back to Dabadoru. Our way back was also pretty much safe, excluding small Core patrols which were successfully avoided. After docking at Dabadoru, the artifact batches were handed over to the scientist group. Mission accomplished.

ENSIGN KUNRAD AMHRAD
34TH HADES BRIGADE
17/05/835





ATTACHMENT FILES
  • [1] - 14/05/835 - Raven batch transferred.
  • [2] - 14/05/835 - Rogue batch transferred.

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 05-23-2025

[Image: Bez-nazvania81-20250108183317.png]



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





OMICRON DELTA PATROL DUTY

Today, as scheduled, I took off from Dabadoru station for a patrol mission.

Overall, it was a breeze, before a distress call was cought on my communication module. As was stated, signature "Scorpion.Beta-Lambda" has sent this call throughout Delta and, presumably, beyond. No location was provided whatsoever, only messages about their crippled ship.

As I contionued my patrol, a Freelancer who went by a callsign "Wostok", piloting "Obsidian" fighter came by. Scanning ruitine has detected Nomad artifacts. After questioning, freelancer stated them as cargo to our branch in Omicron Mu. I've taken this cargo under my watch.

This encounter was joined by a Deterrance corsair vessel, also in question about that distress call from earlier. And that call was getting worse. Communication module started to go with static noises, also delivering obscure vision-like messages, as it always do when Nomads are communicating between each other and want for us to catch someting. Then it showed itself from it's cloaking device and scanners made a "Scorpion" gunboat out of this vessel, seems like a mix of Nomadic and human tech. Of course, it was terminated on sight. Though, personally, I think that we can expect more of such traps in future due to attention that was brought to this distress call.

Corsairs departed, mentioning that they are gathering their forces in Delta. Then I've escorted damaged "Wostok" to Freeport 11 and returned to Dabadoru. The artifacts from earlier were handed over to our scientists.

ENSIGN KUNRAD AMHRAD
34TH HADES BRIGADE
23/05/835





ATTACHMENT FILES
  • [1] - 23/05/835 - Hostile Gunboat.

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 05-24-2025

[Image: Bez-nazvania81-20250108183317.png]



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

The operation started as scheduled, Raven and I, prepared and ready, docked out from Dabadoru station and moved our way on a designated route.

Nothing particular happened on our way to Kaiserslautern Depot, every possible encounter was successfully avoided.

Upon our arrival, we've met with The Platform officer, going by the callsign "Civil Servant" and his, seems like, subordinate, who went by a callsign "Arverni". Both of them responded to a code-phrase according to our agreement with Bundschuh. Also, other escort arrived shortly, consisting of Emilia Hoffmann, and, met later, near Hudson JH, Bundschuh capital vessel "Volksboote".

On our way to Hudson we made a small-talk about situation overall and in Rheinland in particular. Here are the news about Corsairs stepping in New Berlin system and Rheinland officials growing their military force.

Then, the meeting was attended, all aquientances are made. But transition was enterrupted by an MND agent showing up on the radars, mere 10-12 klicks away. This encounter was resolved by parting ways with that agent by "Civil Servant's" initiative.

Transition was made later, on Kaiserslautern Depot, from where our route back has started.

It passed univentful, except some more communication with the Bundschuh, learning of a conflict between MND and them, located in Thuringia. "Civil Servant" was sure of incubi infestation amongst MND ranks.

We parted our ways with Bundschuh in Omicron Theta, then - got to Dabadoru Station safe and sound. Jinna Leons transferred in good state of health and mind.

Job is done.



LIEUTENANT KUNRAD AMHRAD
34TH HADES BRIGADE
24/05/835





ATTACHMENT FILES
  • NONE.

[+]Black box


RE: Hades Brigade - Reporting channel - kotyafffsky - 05-26-2025

[Image: Bez-nazvania81-20250108183317.png]



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





OMICRON DELTA PATROL DUTY / NOTH-11 ENCOUNTER

Another patrol duty started, as always, from Dabadoru station. Most of it didn't have any notable event nor encounters, untill.

Upon visiting Freeport-11 and having a small talk with agent Anya Seer and earlier aquianted freelancer Wostok about the recent views in case there's something worth mentioning in this very report, another pilot, Noth-11 joined up. This conversation can be summarized in following topics:

First of all, his ship. RH-GM17 "Loki MK. II" of the Red Hessians ship building lines.

Second, his cargo. Approximatly, according to my scanner array, 45 units of Azurite Gas. Cargo was destroyed by Noth-11 himself, earlier claimed to be his trophy from a shot-down Corsair.
Note: pilot arrived from direction of Tokelau Ice Cloud.

Third, his attitude. Throughout the conversation, Noth pilot was overall negative, to 34th Brigade, it seems, in particular. He claimed, that if it was not for Freeport's no firing zone, he would have engaged me or any other.
Note: Agent Seer did a good job, being as well as the mediator and as well as the one questioning, with just a little bit of correctioning through one-to-one communication channel between her and me.

Fourth, Noth plans. Of course, this is the subject to be questioned, but Noth-11 implications were that he and his so-called "family" are in a conflict with corsairs right now. And yet, even if their views of Order - this one offered to strike at Corsairs as well.
Note: that might be just a sarcasm, or, as I feel, an attempt to give an idea of joining in this unnecessary war. Even as the Freeport-9'er I see it that way. As well as this may be a sign that they are trying to pull the attention from elsewhere.

Fifth, last but not least. Even if Noth-11 just arrived to Freeport, he didn't decide to dock at it. His way "for a rest" was destined somewhere in a direction to mentioned Tokelau Ice Cloud. Althogh, I didn't risk following him for it to jeopardize the investigation, probably yet unknown to the Noth thmeselves, this is a fact to consider.

Report end. Scanning data as well as communications from the black box are related.

LIEUTENANT KUNRAD AMHRAD
34TH HADES BRIGADE
26/05/835





ATTACHMENT FILES
  • [1] - 25/05/835 - Noth-11 scan summary.

[+]Black box


RE: Hades Brigade - Reporting channel - Perfect Gentleman - 05-31-2025

[Image: Bez-nazvania81-20250108183317.png]



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





SHIP & CREW INSPECTION - DARKHORSE

In accordance with the objectives of Operation 835-3, a scheduled rendezvous was made with the ship's captain, Dante Flintlocke, and his crew off Dabadoru Station on May 28, 835. The purpose was to inspect the ship in order to establish its status for further cooperation with the Order.

The inspection included the steps outlined in the operation's objectives. The ship's captain cooperated in accomplishing each of them, and shared additional details: crew and ship's activities over the past month. During the inspection, he mentioned the anomalous location in Omegas, as well as the coordinates to it. The location of the anomalous location is Omega-5, coordinates: 1494 20363 -42506. The ship's status, identification codes, and crew details suggest that they are not among the infected, nor have they been seen cooperating with groups hostile to the Order.

After completing the inspection, the protocol was to escort the ship to Freeport-11, after which I returned to Dabadoru Station, awaiting further instructions.



LIEUTENANT ALEX RUSSEL
34TH HADES BRIGADE
31/05/835





ATTACHMENT FILES
  • [1] - Darkhrose arrival at Dabadoru
  • [2], [3], [4], [5] - Scanning data
  • [7] - Darkhorse arrival at Freeport-11

[+]Black box