Archive No.: 063-C

Project: TRIA PRIMA
Designation: SULFUR
Variant: C
Division: Crimson Mercenaries
Role: Mass-Production Assault Strike Platform
Status: Operational / Mass Production
Project designation: TRIA PRIMA
Production classification: Specialised Mass-Production Combat Unit
Derived from: TRIA PRIMA Common Combat Architecture
Influence:
Shock Assault Doctrine
Penetration Warfare
Concentrated Firepower
Rapid Strike Doctrine

Overview - Design Philosophy

SULFUR is the most aggressive configuration of the TRIA PRIMA platform.
The common architecture is reorganised around concentrated offensive capability. Weapon systems become visually and structurally dominant, while propulsion and combat infrastructure are arranged to support rapid engagement and withdrawal.
Unlike SAL, SULFUR is not intended to win through prolonged endurance.
Unlike MERCURIUS, it does not primarily seek to avoid engagement.
It exists to create a decisive one.

Operational Doctrine

SULFUR is a frontline assault unit designed for rapid strikes against high-value targets, hardened positions, and critical elements of enemy formations.
Its preferred engagement cycle is:
Approach. Penetrate. Destroy. Withdraw.

Architecture

The TRIA PRIMA modular structure is retained, but weapon assemblies are given priority within the configuration. The resulting platform is compact, heavily armed, and optimised for forward offensive action.

Production Philosophy

SULFUR remains a mass-production platform despite its specialised role.
Its purpose is to provide Crimson formations with dedicated assault capability without creating an entirely separate production ecosystem.

CBAA Historical Record

The third configuration of TRIA PRIMA emerged from a different question.
If SAL represented endurance and MERCURIUS represented controlled movement, what could the same architecture achieve when almost every design decision was directed toward offensive action?

The answer was SULFUR.
CBAA engineers retained the basic TRIA PRIMA structure but reorganised its priorities.
They brought weapon systems forward and integrated them more aggressively into the platform. Supporting structures were adapted around them, creating a vessel whose entire silhouette communicated forward intent.

SULFUR was not designed to remain in a prolonged exchange of fire.
Its purpose was to reach the decisive point of an engagement and apply overwhelming force before the enemy could reorganise.
The vessel therefore became the most direct expression of Crimson assault doctrine within the TRIA PRIMA family.
Its high-output weapons are supported by a propulsion architecture intended to deliver the vessel rapidly into effective range and remove it from danger after the primary strike.

The doctrine is simple.
Do not trade blows unnecessarily.
Do not remain where the enemy can concentrate against you.
Strike the critical point.
Then leave.

Despite its specialisation, SULFUR remained subject to the central requirement of Project TRIA PRIMA: it had to remain suitable for mass production.
CBAA deliberately avoided turning the vessel into an elite one-off weapon system.

The same modular production principles used for SAL and MERCURIUS were retained wherever possible. Specialised components changed the tactical function without destroying the common industrial foundation.
This allowed Crimson Mercenaries formations to deploy all three configurations within the same broader combat ecosystem.

SAL could establish and hold the frontline.
MERCURIUS could operate through gaps, approach from unexpected vectors, and provide a more elusive combat presence.
SULFUR could exploit the opening and deliver the decisive strike.
The three configurations were therefore not competing designs.
They were complementary weapons built from the same answer.

One architecture.
Three battlefield expressions.

Closing Statement

SULFUR does not enter the battle.
It starts the reaction.

Charon:
https://charon.gg/ships/63-tria-prima-sulfur/

Archive No.: 063-B

Project: TRIA PRIMA
Designation: MERCURIUS
Variant: B
Division: Crimson Mercenaries
Role: Mass-Production Low-Signature Frontline Combat Platform
Status: Operational / Mass Production
Project designation: TRIA PRIMA
Production classification: Specialised Mass-Production Combat Unit
Derived from: TRIA PRIMA Common Combat Architecture
Influence:
Low-Signature Warfare Doctrine
Adaptive Combat Architecture
Frontline Reconnaissance
Evasive Combat Doctrine

Overview - Design Philosophy

MERCURIUS represents the more fluid interpretation of the TRIA PRIMA architecture.
Where SAL emphasises mass and protection, MERCURIUS reduces the apparent rigidity of the platform. Its surfaces flow more continuously between major structures, producing a lighter and less conventional silhouette. The purpose is functional.
MERCURIUS is designed to reduce detection opportunities, improve tactical movement, and make the vessel more difficult to track and engage.
Despite its specialised configuration, it remains a frontline combat vessel and is intended for mass production.

Operational Doctrine

MERCURIUS operates through mobility, low signature and tactical uncertainty.
It can perform reconnaissance and forward observation, but its primary purpose remains combat. It is intended to enter hostile environments, engage when necessary, and reposition before an opponent can establish a reliable firing solution.

Architecture

The common TRIA PRIMA structure is retained while external assemblies are reshaped into a more integrated and streamlined configuration.

Production Philosophy

MERCURIUS demonstrates that specialised combat capability does not require abandoning the mass-production foundation of TRIA PRIMA.

CBAA Historical Record

Once SAL had established the basic viability of TRIA PRIMA, CBAA engineers began examining the limits of the common architecture. The question was not how to build a stronger SAL; it was how far the same platform could be transformed without losing the production advantages that made the program viable.

MERCURIUS became the answer.

The engineers retained the fundamental structure, propulsion arrangement and modular philosophy of the baseline vessel while changing the relationship between its major components.
The result was a noticeably more fluid spacecraft.

Its geometry reduced the impression of concentrated mass and created a more continuous outer profile. Structures that appeared heavy and separate on SAL became more integrated within MERCURIUS.
The change was not purely visual. CBAA intended the new configuration to operate with a lower tactical signature and greater freedom of movement.

MERCURIUS could approach hostile formations without immediately presenting the same visual and sensor profile as the heavier SAL. It could perform forward reconnaissance, identify targets, and exploit openings in enemy formations. But CBAA rejected the idea of turning it into a dedicated reconnaissance craft.

MERCURIUS was still a Crimson combat vessel.
It was expected to fight.
Its advantage was that it could choose more carefully when and where that fight occurred.

This made MERCURIUS particularly suitable for forward-line operations where the ability to disappear into the tactical environment could be more valuable than simply absorbing another hit.
The configuration remained compatible with the TRIA PRIMA production system. This was essential.
CBAA did not want a unique stealth platform requiring an entirely separate industrial chain. MERCURIUS was designed to be manufactured using the same fundamental production philosophy as SAL, with specialised assemblies replacing selected standard components.
The result was a vessel that could be produced in significant numbers while providing a different tactical capability.
SAL represented endurance through mass.
MERCURIUS represented survival through movement and uncertainty.
Both remained Crimson Mercenaries' frontline assets.

Closing Statement

MERCURIUS does not disappear.
It simply refuses to remain where you expect it to be.

Charon:
https://charon.gg/ships/63-tria-prima-mercurius/

Archive No.: 063-A

Project: TRIA PRIMA
Designation: SAL
Variant: A
Division: Crimson Mercenaries
Role: Mass-Production Frontline Combat Platform
Status: Operational / Mass Production
Project designation: TRIA PRIMA
Production classification: Standard Mass-Production Combat Unit
Derived from:
TRIA PRIMA Common Combat Architecture
Influence:
Armored Advance Doctrine
Frontline Combat Doctrine
Mass Production Architecture
Distributed Protection

Overview - Design Philosophy

SAL is the baseline configuration of Project TRIA PRIMA.

The vessel was designed around simplicity, repeatability and battlefield endurance. Its construction uses a limited number of components and repeated structural assemblies, allowing the platform to be manufactured in large numbers without requiring excessive production complexity.
SAL deliberately favours mass and structural density over extreme agility. Its compact, heavily built configuration gives it the character of an armoured vehicle translated into a spacecraft.
The vessel is intended to enter the frontline, withstand sustained engagement and continue advancing.

Operational Doctrine

SAL is a direct-combat platform designed for prolonged frontline operations.
Its primary strength is not a specialised tactical trick, but the combination of armour, firepower, structural redundancy and production availability.

Architecture

The central hull is surrounded by dense modular structures housing propulsion, power systems and combat infrastructure. Repeated assemblies simplify construction, maintenance and replacement.

Production Philosophy

SAL establishes the standard production configuration from which the remaining TRIA PRIMA variants are derived.

CBAA Historical Record

Project TRIA PRIMA began as an attempt to create a simple and reproducible combat architecture for the Crimson Mercenaries.
Rather than developing three unrelated vessels for different missions, CBAA engineers established a common structural foundation that could be adapted without abandoning the production system.
SAL became the first configuration.

Its architecture was deliberately conservative. The Bureau wanted a vessel that could be produced in large numbers, deployed to the frontline, and maintained without the logistical burden associated with increasingly specialised platforms.
The result became the physical foundation of the entire TRIA PRIMA family.
From SAL, CBAA would develop two further interpretations of the same architecture.
One would reduce its battlefield signature.
The other would increase its offensive concentration.
SAL remained the reference.

Closing Statement

SAL does not need to be exceptional.
It needs to keep advancing.

Charon:
https://charon.gg/ships/63-tria-prima-sal/

Archive No. 062

Designation: CUSPIS
Division: Crimson Mercenaries
Role: Armored Assault & Breakthrough Corvette
Status: Operational
Project designation: CUSPIS
Derived from: Crimson Corvette Architecture
Influence:
Armored Cavalry Doctrine
Breakthrough Warfare
High-Speed Assault Doctrine
Distributed Squadron Operations
Kinetic Penetration Architecture

Overview

Project CUSPIS represents the Bureau's development of a specialized breakthrough platform designed not to hold the battlefield, but to tear through it.
CUSPIS is not primarily an independent combatant. Its intended operational form is the CUSPIS Squadron — multiple heavily armored vessels operating as a single penetrating formation.

Its doctrine is based on a simple principle:
Do not attack the front. Break through it.

CUSPIS squadrons accelerate into enemy formations, penetrating the defensive line at a designated point. Once behind the enemy front, they attack command, artillery, logistics, and other high-value targets before redirecting toward another section of the battlefield.

There, the squadron attacks the enemy formation from behind while allied forces advance from the opposite direction, exploiting the resulting chaos and destroying what remains of the disrupted line. The CUSPIS squadron emerges into the rear of allied forces, regroups, rebuilds formation, and accelerates once more before beginning another circuit.

The doctrine depends on momentum.

A CUSPIS that stops becomes vulnerable. A CUSPIS that maintains speed remains difficult to engage.
Like heavily armored cavalry, the formation survives not by remaining stationary under fire, but by maintaining its momentum through the battlefield.

CUSPIS does not hold the line.
It moves through it.

CBAA Historical Record

The origins of CUSPIS can be traced to a recurring problem identified by Crimson Mercenaries tactical analysts.
Conventional assault vessels were effective against individual targets but became increasingly vulnerable when attacking dense, organized defensive lines. A formation could absorb attacks, redistribute firepower and isolate individual attackers.

CBAA's response was not to create a vessel capable of remaining under fire longer.
It was to create one that would not remain there at all.

The CUSPIS concept required three characteristics above all others:
Protection.
Acceleration.
Penetration.
Everything else became secondary.

The resulting vessel was built around a heavily reinforced wedge-shaped hull, concentrating structural mass toward the forward section while maintaining a low, highly directional profile.

CUSPIS approaches an enemy formation like a projectile. Its weapons engage targets during the penetration phase while its armor protects the vessel through the point of maximum exposure.
The result is not a ship designed to fight its way toward the enemy.
It is designed to go through the enemy.
The Bureau quickly rejected individual deployment. A single CUSPIS could create a breach, but only the squadron could exploit it.

Multiple vessels therefore enter the same section of the enemy line, combining speed, concentrated fire, and multiple penetration vectors. Once behind the formation, they attack designated targets in the enemy rear before selecting another section of the front.
The second penetration is performed from behind.
CUSPIS attacks the enemy line at another point while allied forces simultaneously advance from the opposite direction. The resulting crossfire and disruption can collapse the local defensive formation, allowing the CUSPIS Squadron to penetrate the enemy line and emerge behind its own forces.

There, the squadron regroups.
Then it accelerates.
Then it attacks again.

This creates a continuous battlefield circuit:
Friendly Rear → Enemy Front → Enemy Rear → Enemy Front → Friendly Rear.
The purpose is not withdrawal.
It is repeated penetration.

CBAA designated this doctrine Armored Cavalry Penetration.
The analogy is deliberate. Ancient heavy cavalry could survive a charge only while maintaining momentum. Once stopped and surrounded, its greatest advantages disappeared.
CUSPIS follows the same principle at extreme scale.

Its armor allows it to survive the initial penetration.
Its engines preserve the momentum needed to complete the attack.
Its weapons turn that momentum into destruction.
Its maneuverability allows the squadron to change its point of attack before the enemy can reorganize.

A stationary CUSPIS is a vulnerable CUSPIS.
A moving CUSPIS is a weapon in motion.

The Bureau therefore considers momentum not merely a tactical advantage, but a survival system.
CUSPIS squadrons are not designed to hold territory, defend static positions, or conduct prolonged engagements.
Their purpose is to keep moving.
Find the line.
Break the line.
Strike the rear.
Break through again.
Regroup.
Accelerate.
Repeat.

Closing Doctrinal Statement
CUSPIS does not retreat from the battlefield.
It completes the circuit.

CBAA ARCHIVES

Archive No. 055

Designation: Balista

Division: Black Projects Division

Role: Strategic Railgun Strike Corvette

Status: Experimental

Project designation: BALISTA

Derived from: Crimson Heavy Corvette Research

Influence:
Vector Strike Doctrine
Future Ballista-Class Platforms
Joint Operations with Archive #056 "Eye"

Overview

Project BALISTA was never intended to participate in conventional fleet engagements.

It exists for a single purpose.

To eliminate targets that cannot be allowed to survive.

Operating alongside the reconnaissance platform Archive #056 – Eye, Balista remains beyond visual engagement range, maintaining complete emission discipline while awaiting firing authorization.

Eye observes.

Eye identifies.

Eye predicts.

Eye confirms.

Only then does Balista awaken.

The vessel diverts nearly its entire reactor output into a spinal electromagnetic accelerator extending through almost the entire length of the hull.

For several seconds, the ship ceases to behave like a conventional spacecraft.

Every auxiliary system is sacrificed.

Every unnecessary circuit is shut down.

Every available joule is redirected into a single weapon.

As reactor output exceeds normal containment limits, the exposed energy spine erupts with violent blue electrical discharges. Magnetic containment fields overload, plasma vents open automatically, and cooling channels struggle to dissipate the impossible thermal load generated by the firing sequence.

Then—

One shot.

No warning.

No ranging fire.

No correction.

Only silence.

Lore

CBAA Historical Record

Conventional artillery supports fleets.
Balista supports history.
Entire campaigns have ended before the first battle because a single command vessel, orbital defense platform or planetary installation simply ceased to exist.
The Bureau concluded that overwhelming firepower was no longer enough.
Absolute precision was required.
But precision demands vision.
Project 056 Eye solved that problem.
Designed as an autonomous reconnaissance and targeting platform, Eye could remain hidden for days, continuously observing strategic assets far beyond the operational range of conventional fleets.
When firing authorization was granted, encrypted firing solutions were transmitted directly to Balista.
The two vessels were never considered separate weapons.
Within Bureau doctrine, they were classified as two components of a single strategic system.
One machine observes.
The other delivers judgment.

Operational Analysis

The firing sequence revealed an unexpected phenomenon.
During discharge, immense electromagnetic fields escaped containment and surrounded the vessel in expanding arcs of ionized plasma.
The effect resembled the experimental electromagnetic disruption system first documented during Project Amethyst Arc.
Unlike Amethyst Arc, however, the interference generated by Balista was never intentionally engineered.
It was a consequence of pushing the reactor beyond every conventional safety margin.
Ironically, this instability became a tactical advantage.
Immediately after firing, the residual electromagnetic storm severely degraded hostile targeting systems.
Radar solutions drifted.
Optical tracking became unreliable.
Guidance computers reported inconsistent range calculations.
Missile lock quality deteriorated dramatically.
For several critical moments following the shot, Balista became extraordinarily difficult to engage.
The Bureau classified the phenomenon as an unintended—but operationally valuable—secondary defensive capability.

Silent Relocation Protocol

The electromagnetic storm was temporary.
Once residual energy levels fell below operational thresholds, Balista entered its final firing phase.
Massive cooling tunnels along the exposed reactor spine gradually sealed.
Radiator arrays retracted beneath armored hull sections.
External thermal emissions rapidly declined as surplus heat was absorbed into dedicated thermal reservoirs.
With the reactor returned to low-output operation, the vessel transitioned into Silent Mode.
Engine signatures were minimized.
Power consumption dropped to essential systems only.
Sensor emissions approached background radiation levels.
Rather than fleeing at maximum speed, Balista simply disappeared.
By the time hostile forces recovered from the electromagnetic interference, the firing platform had already relocated to another concealed position, awaiting the next transmission from Eye.

Bureau Doctrine

Project BALISTA established the Vector Strike Doctrine.
Victory does not belong to the fleet with the most guns.
It belongs to the fleet that removes the only target that mattered.
A sniper does not announce his presence.
A railgun does not require a second shot.
And a weapon that cannot be found...
May fire again.

Thank you u/SuperZetaman1, my brother for taking pictures of this ship, you are tha real maestro!!!

CBAA ARCHIVES

Archive No. 054

Designation: Predator Evo

Division: Crimson Division

Role: Hunter Corvette Reconstruction

Status: Operational

Project designation: PREDATOR

Derived from: Archive #017 – Crimson Predator

Influence:

Modern Crimson Doctrine

Hunter-Class Development

Overview

Project PREDATOR EVO represents the Bureau's return to its own origins.

Rather than pursuing entirely new concepts, Bureau engineers reopened the oldest surviving Predator archives and reconstructed the vessel using every engineering principle developed throughout decades of CBAA research.

Although visually recognizable as the successor to Archive #017, nearly every structural component has been redesigned.

The result is not a modernization.

It is the realization of what the original Predator was always intended to become.

Every angle, every intake, every engine placement, and every exposed system serves a single purpose:

Create a vessel capable of overwhelming its target through relentless pursuit.

Predator Evo abandons unnecessary complexity in favor of mechanical honesty.

Nothing exists for decoration.

Everything exists because it improves performance.

Archive #054 proves that evolution does not always require a new doctrine.

Sometimes the greatest progress comes from perfecting the very first idea.

CBAA Historical Record

Archive #017 was created during a time when the Bureau possessed more ambition than experience.

Built entirely with the limitations of early construction methods, Crimson Predator established the foundations of what would later become the Crimson Doctrine.

The original vessel demonstrated that speed, aggression, and continuous pressure could compensate for technological limitations.

Its architecture became iconic. Its engineering did not.

Years later, after the introduction of advanced fabrication methods, Bureau engineers revisited the original blueprints.

Rather than replacing the Predator... They rebuilt it.

Weak structural transitions disappeared.

Internal systems became integrated into the hull.

Power distribution was redesigned around modern reactor architecture.

Every exposed component was evaluated.

Only those that contributed directly to performance remained.

The resulting vessel retained the unmistakable silhouette of its predecessor while achieving an entirely different level of refinement.

Predator Evo became more than an upgrade.

It became a historical correction.

Within Bureau archives, Archive #054 demonstrates a fundamental engineering principle.

Innovation creates history, while Reconstruction perfects it.

The first Predator taught the Bureau how to hunt. Predator Evo reminds the Bureau why it began hunting in the first place.

P.S. - u/SuperZetaman1 - Thank you, Brother! For your patience, being there, and most importantly, for giving your finishing touch with decals and for creating such photos- truly masterpieces!

Welcome to the Crimson Bureau of Applied Atrocity (CBAA)

Every ship posted here belongs to the Crimson Bureau of Applied Atrocity (CBAA) — a fictional black-project military design bureau existing entirely within No Man's Sky.

Unlike traditional ship builds, CBAA projects are not designed around aesthetics first.

Every vessel begins with a question.

• What mission must it accomplish?
• What engineering challenge must it solve?
• What tactical doctrine defines its purpose?
• What technological problem does it attempt to answer?

Only after these foundations are established does the ship itself begin to take shape.

Every line, every compartment, every structural element exists because it serves a purpose.

Four Divisions. Four Philosophies.

🔴 Crimson Mercenaries

Frontline combat vessels built for battlefield dominance, overwhelming firepower and psychological intimidation.

🟣 Amethyst Division

Precision interceptors and experimental energy platforms where speed, elegance and efficiency become weapons.

🟢 Alien Division

Research into unconventional engineering inspired by unknown civilizations, asymmetric architectures and non-human technological concepts.

⚫ Black Projects Division

CBAA's experimental laboratory, where Innovation Vector (IV) prototypes test technologies and operational doctrines before they become part of future fleets.

The CBAA Archives

Every completed vessel becomes an official archive entry.

Projects inherit technologies, doctrines and architectural principles from earlier ships while introducing new concepts that influence those that follow.

Rather than isolated creations, every corvette contributes to a continuous technological lineage spanning the entire Bureau's history.

More Than Shipbuilding

For me, No Man's Sky has become a platform for combining:

• industrial design
• systems engineering
• military architecture
• hard sci-fi worldbuilding

Every new release expands the history of the Bureau.

Every ship is another chapter.

Welcome to the CBAA Archives.

Doctrine Before Design.

CBAA ARCHIVES

Archive No. 030

Designation: Crimson Executioner

Division: Crimson Mercenaries

Role: Commissioned Extermination Corvette

Status: Commissioned Service

Project designation:
EXECUTIONER

Derived from:
Crimson Harbinger

Influence:
Crimson Vanguard

Overview:

Crimson Executioner represents the absolute endpoint of first-generation Crimson combat doctrine.

Where Harbinger denied strategic options, Executioner removed the need for strategy altogether. Every aspect of the vessel was engineered around terminal engagement geometry. Its elongated execution arms, concentrated central combat core and uninterrupted forward alignment were designed to converge overwhelming force upon a single operational objective without deviation or hesitation.

Unlike previous Crimson platforms that shaped or controlled the battlefield, Executioner exists to conclude it. The vessel abandons concepts such as interception, containment or prolonged pressure in favor of irreversible decisive action. Once committed, its operational profile allows neither retreat nor negotiation.

Archive #030 stands as the Bureau's final exploration of pure aggression before Crimson doctrine reached technological and philosophical saturation.

Build:

BBA-assisted placement

An in-game version is possible using advanced glitch-building techniques, but requires extensive manual construction.

Lore

CBAA Historical Record

Archive #030 marks the final evolution of the Crimson Doctrine.

For years the Bureau had pursued increasingly sophisticated methods of controlling conflict.

- Predator hunted.

- The Claw captured.

- Protector endured.

- Devil overwhelmed.

- Dead Calm deceived.

- Reaper broke.

- Dread dominated.

- Harbinger surrounded.

Executioner questioned none of those principles. It simply removed everything that was no longer necessary.

The vessel was designed around a single assumption.

Every strategic decision had already been made before its arrival.

Its immense execution arms no longer projected operational influence.

They became the physical continuation of a sentence that had already been passed.

Combat telemetry repeatedly demonstrated the same outcome.

By the time hostile commanders identified the vessel, every escape corridor had already collapsed under preceding Crimson operations.

Executioner did not create victory.

It arrived to formalize it.

Within Bureau archives, Project EXECUTIONER was never considered the ultimate warship.

It was considered the point beyond which further escalation no longer produced a better doctrine.

Aggression had reached its logical conclusion.

There was nowhere left to evolve.

CBAA ARCHIVES

Archive No. 029

Designation: Crimson Harbinger

Division: Crimson Mercenaries

Role: Commissioned Strategic Assault Corvette

Status: Commissioned Service

Project designation: HARBINGER

Derived from:
Crimson Dread

Influence:
Crimson Vanguard
Operational Encirclement Doctrine
Strategic Strike Groups

Overview:

Crimson Harbinger represents the Bureau's transition from battlefield dominance to operational dominance.

While Crimson Dread established control over contested space through sustained pressure, Harbinger was engineered to shape the battle before decisive engagement even began. Its elongated forward structures extend the vessel's engagement geometry far beyond the central combat core, allowing hostile movements to be constrained long before direct contact.

Rather than acting as the primary siege platform, Harbinger coordinates the collapse of enemy operational freedom. Its architecture emphasizes reach, positional superiority and persistent forward projection, enabling accompanying Crimson formations to exploit increasingly limited maneuver corridors.

Archive #029 marks the emergence of Operational Encirclement Doctrine, where victory is achieved by denying an opponent meaningful strategic choices rather than overwhelming them through firepower alone.

Build:

BBA-assisted placement

An in-game version is possible using advanced glitch-building techniques, but requires extensive manual construction.

Lore

CBAA Historical Record

Archive #029 documents the Bureau's realization that battlefield superiority alone was no longer sufficient.

Crimson Dread had proven capable of controlling engagements once battle had begun.

Harbinger was conceived to determine where the battle would occur in the first place.

Instead of concentrating on increasing firepower or structural resilience, Bureau engineers extended the vessel's operational geometry. The elongated forward arms projected sensor arrays, targeting relays and distributed weapon systems far ahead of the primary combat core, creating an expanding zone of tactical influence that advanced faster than the fleet itself.

Enemy commanders repeatedly reported an identical phenomenon.

Routes that appeared open moments earlier were suddenly no longer viable.

Escape vectors disappeared.

Reinforcement corridors became engagement corridors.

Withdrawal became pursuit.

Unlike previous Crimson vessels, Harbinger did not force opponents into disadvantageous engagements.

It quietly removed every advantageous alternative.

Within Bureau strategic doctrine, Archive #029 became the foundation of Operational Encirclement Doctrine.

Control does not begin when weapons fire.

It begins when every other decision has already been taken away.

CBAA ARCHIVES

Archive No. 053

Designation:
Amethyst Arc

Division:
Amethyst Division

Role:
Experimental Electromagnetic Interceptor

Status:
Experimental

Project designation:
ARC

Derived from:
Nyx Talon
Advanced Amethyst Energy Research

Influence:
Future Amethyst Energy Platforms

Overview

Project AMETHYST ARC represents the next technological evolution of the Amethyst Division, expanding upon the operational experience gained through the Nyx interceptor program.

Rather than pursuing greater firepower or heavier protection, Bureau engineers explored the offensive potential of experimental electromagnetic field manipulation. The vessel's energy core functions as both its propulsion source and an integrated battlefield system, capable of disrupting hostile sensors, distorting targeting solutions and generating controlled electrical discharge arcs against nearby enemy vessels.

Designed for pilots operating alone against numerically superior forces, Arc combines exceptional maneuverability, a compact silhouette and an advanced energy architecture to execute aggressive hit-and-run strikes, rapid target elimination and deep penetration missions.

Archive #053 demonstrates that battlefield superiority can be achieved not only through weapons, but through absolute control over the electromagnetic environment.

CBAA Historical Record

Following the operational success of the Nyx Doctrine, the Bureau initiated a new research program within the Amethyst Division.

The objective was no longer to improve the interceptor itself.

It was to redefine the battlefield surrounding it.

Traditional energy cores powered propulsion systems.

Project ARC transformed the energy core into an active combat system.

Engineers developed an experimental electromagnetic architecture capable of manipulating localized energy fields around the vessel. These distortions reduced sensor reliability, interfered with targeting systems and generated high-energy electrical discharge arcs against hostile ships operating within close proximity.

The interceptor required neither overwhelming armor nor superior numbers.

Its survivability depended upon remaining impossible to track and striking before the enemy understood what had entered the battlespace.

Combat reports described a recurring sequence.

A sudden electromagnetic storm.

Violent blue electrical discharges.

A dark silhouette visible only for seconds.

Then silence.

Within the Bureau, pilots gave the vessel a simpler name.

The Storm That Hunts.

Project AMETHYST ARC confirmed that the future of the Amethyst Division extended beyond aerodynamic architecture alone.

Mastery of energy itself had become a weapon.

Within Bureau archives, Project AMETHYST ARC established the Electromagnetic Dominance Concept.

The most dangerous interceptor is not the one carrying the largest weapons.

It is the one that turns the battlefield itself against the enemy.

Survivors rarely agree on the ship's appearance.

They all remember the storm.

They all remember the silence afterward.

"If you can clearly see the Arc... it has already decided to let you live."

Special thanks to: u/SuperZetaman1 - support and advice u/Special_Cow4974 - for making photo session of my ships.

CBAA // Amethyst Division

CBAA Archives

#52 — NYX Talon

Amethyst Division

Long-range Interceptor / Precision Strike Platform

Not every interceptor has to look fragile.

The NYX Talon was conceived within the Crimson Bureau of Applied Atrocity (CBAA) as a flagship project of the Amethyst Division—where elegance, precision and velocity are valued above intimidation. Every surface exists for a reason, and every line serves the pursuit of aerodynamic perfection.

Unlike the brutal warships fielded by the Crimson Division, the Talon achieves superiority through speed, stability and calculated precision. Its razor-thin delta wing, four-engine propulsion system and seamlessly blended fuselage create the illusion of a single continuous airframe cutting effortlessly through atmosphere and vacuum alike.

The latest canopy represents the final evolution of the design. By prioritizing a smooth transition between the cockpit and fuselage, the aircraft gains a more unified silhouette, reinforcing the philosophy that the most advanced engineering should appear almost effortless.

*"Speed is invisible. Precision is inevitable."*

CBAA Archive // Declassified

Innovation Vector IV-51 "Bulwark"

Most experimental projects chase speed.

Bulwark was designed to answer a different question:

What if survival itself became the primary weapon?

Developed within the CBAA Black Projects Division, IV-51 explored distributed armor geometry and defensive projection concepts instead of conventional offensive optimization.

The oversized lateral shield structures were never intended as decorative wings. They form a protective envelope around the command module, allowing the vessel to absorb, redirect and survive impacts that would cripple more agile platforms.

Unlike the sleek hunters that followed, Bulwark embraces mass. Every line of its silhouette communicates the same philosophy: advance slowly, hold the line, refuse to yield.

The project proved that survivability could be engineered into the airframe itself rather than relying solely on shields or maneuverability. While the prototype was never selected for mass production, many structural concepts later influenced subsequent CBAA programs.

Not every Innovation Vector exists to become the future.

Some exist to make the future possible.

CBAA ARCHIVE // CRIMSON DIVISION

Asset ID: #49

Designation: Crimson Warden

Classification: Light Security Corvette

Division: Crimson Division

Status: Operational

"A fortress can be bypassed. A Warden cannot."

Following a series of successful Crimson offensives, Bureau analysts identified an unexpected vulnerability.

Capturing territory was never the problem.

Keeping it was.

Rather than assigning expensive capital assets to routine patrol duty, the Crimson Bureau of Applied Atrocity commissioned a compact corvette dedicated to one purpose:

Permanent territorial control.

Thus Project #49 was born.

The Crimson Warden is among the smallest corvettes ever produced by the Crimson Division, yet its silhouette conceals an unusually dense concentration of firepower. Four synchronized forward batteries, reinforced armor, redundant power routing and extended sensor coverage allow the vessel to dominate strategic corridors, orbital checkpoints and station approaches far beyond what its size would suggest.

Unlike assault corvettes, the Warden does not spearhead invasions.

It arrives after the battle. It remains long after everyone else has departed.

Crimson doctrine assigns Wardens to orbital infrastructure, supply routes, research facilities and newly secured systems, where they serve as the Bureau's permanent presence. They escort convoys, intercept unauthorized traffic and respond immediately to any hostile incursion.

Within the Bureau, commanders often summarize the vessel's tactical philosophy with a single sentence:

"Territory is not considered secure until a Warden is watching it."

Despite its compact dimensions, the Warden carries the command-and-control systems expected of a much larger vessel, enabling it to coordinate local defense forces while maintaining independent combat capability.

Enemy reconnaissance reports frequently underestimate the ship.

Few make the same mistake twice.

CBAA Archive // Crimson Division

"We do not guard borders.

We define them."

This project began with a build request from u/Lobuliyt27 inspired by a Destiny 2 ship.

The objective sounded simple: create a small corvette while preserving the spirit of the original design.

But copying has never been the purpose of the Innovation Vector program.

Instead, I wanted to reinterpret the concept through my own design language, following the Nyx philosophy of long, flowing lines, aggressive proportions, and a silhouette that feels more like a predator than a machine.

At only around 1.2× the size of a standard No Man's Sky starship, Umbra bridges the gap between a heavy interceptor and a true corvette.

Every curve and every surface was shaped by hand to create one continuous flowing silhouette rather than simply assembling predefined modules. The goal wasn't to recreate the original ship, but to capture its essence while making it unmistakably part of my own universe.

It isn't a replica.

It isn't a copy.

It is my interpretation.

CBAA Black Projects Division

Innovation Vector IV-51 "Umbra"

Inspired by a Destiny 2 build request.

Defined by its own identity.

CBAA BLACK PROJECTS DIVISION

Innovation Vector Program

Prototype IV-48 "Null"

STATUS: ARCHIVED

The Innovation Vector program was established to validate experimental technologies considered unsuitable for immediate fleet deployment.

Prototype IV-48 "Null" was developed as a compact experimental corvette intended to evaluate a continuous armored dorsal architecture, distributed energy systems and high-density forward weapon integration.

During its final redesign, conventional dorsal access was eliminated in favor of short-range teleportation nodes integrated into the wing structures, allowing the entire upper hull to function as uninterrupted armor.

More than 750 auxiliary light emitters were removed during the final optimization phase. The remaining emitters were enlarged and strategically repositioned, improving visual coherence while remaining within operational limitations.

Final Evaluation

✓ Flight trials completed.

✓ Architecture validated.

✓ Innovation Vector objectives achieved.

Project archived as:

IV-48 "Null"

"Some technologies become products.

Others become classified."

— Crimson Bureau of Applied Atrocity

After several redesigns, rebuilds and countless small adjustments, I've finally decided to call this project finished.

Spectre2 is a complete remake and reinterpretation of the legendary Spectre from Galaxy on Fire 2 HD, recreated within No Man's Sky.

Rather than building a direct copy, my goal was to preserve the identity of the original vessel while adapting it to the visual language and construction limitations of NMS. The result is larger, heavier, and far more militarized than my previous attempt.

This ship is also part of my larger No Man's Sky lore project, the Crimson Bureau of Applied Atrocity (CBAA).

Within that setting, Spectre2 belongs to the Alien Mercenaries Division, a branch dedicated to reconstructing and reinterpreting iconic spacecraft from other science-fiction universes. The objective is not perfect replication, but creating versions that look like they could genuinely exist within No Man's Sky while remaining immediately recognizable to fans of the original source material.

Compared to my earlier Spectre build, this remake focuses on:

• a much cleaner silhouette
• stronger military aesthetics
• more believable structural proportions
• significantly increased visual mass
• heavier weapon placement
• improved symmetry and detailing
• a stronger sense of intimidation and battlefield presence

The design draws inspiration from destroyers, stealth bombers, and heavily armed strike vessels rather than traditional starfighters.

Every element was built entirely using in-game assets.

At this point, the project is complete.

No more modifications.
No more redesigns.
No Spectre2.1.

Just Spectre2.

The vessel now takes its place within the CBAA Archive as an official Alien Mercenaries Reconstruction Project, joining a growing collection of ships inspired by classic science-fiction universes.

I'd love to hear what GOF veterans and fellow NMS builders think about the final result.

Lore Classification

CBAA Archive #46
Project Name: Spectre2
Division: Alien Mercenaries
Origin Inspiration: Galaxy on Fire 2 HD
Status: Complete / Archived
Construction Method: Built in Blender.

After a lot of iterations, I can finally call #45 VoidX2 finished.

​

This ship is a complete remake of my old #21 VoidX, one of my earliest custom starship projects.

Old build (#21 VoidX):

https://www.reddit.com/r/NMS_Corvette_Design/s/LnOugi3kt8

​

Looking back at it now, the original VoidX was built entirely in-game, before I started using save editing and advanced build techniques.

​

Back then the whole project relied mostly on:

1/2 offset placement

180° rotations

45° rotations

vanilla in-game construction methods

​

At the time it was the best I could do, but I always felt that my vision of Voidx from GOF2HD deserved a proper rebuild.

​

8 months later I decided to revisit it from scratch.

​

The goal wasn't to create a completely new ship, but to preserve the original silhouette and idea while pushing the design much further in terms of:

proportions

symmetry

flow of the lines

structural detail

overall visual cohesion

​

The result is VoidX2.

​

Comparing it to the original version is probably the best illustration of how much my building techniques and design philosophy have evolved since then.

​

I'd love to hear what you think, especially if you've seen the original #21 version.

​

"Sometimes the best new project is rebuilding an old idea with the skills you didn't have back then."

​

#NoMansSky #NoMansSkyBuilds #StarshipBuilding #CustomStarship #VoidX #SciFiDesign

NYX SERAPH // Corvette-Class Assassin

Beauty is the first warning.

After countless iterations, compromises, rebuilds, and lighting passes… #44 is finally reaching its final form.

Built around the idea of a “femme fatale” starship — elegant, smooth, seductive at first glance… but unmistakably lethal.

The silhouette was inspired by:

- venomous snakes,

- predatory sea creatures,

- stealth interceptors,

- and curved alien architecture.

The goal was to make something that looks alive.

A ship that feels fast even while standing still.

NYX SERAPH — Corvette Configuration

Installed Systems:

- 2x Max Refiner

- Mission Radar

- Appearance Modifier

- Teleporter

- Trade Terminal

- Exocraft Summoning Room (From Freighter)

- Nutrient Processor / Food Station

- Probe

- Signal Booster

- Weapon Rack

- 10x Cargo Storage

- Save Point

- Health Station

- Hazard Protection Station

Additional Notes

- Designed for 3rd-person flight view, 1st-person flight view optional

- Fully functional mobile corvette/base hybrid

- Medium-small class vessel

- Heavy emphasis on silhouette and atmospheric lighting

- Black hull with layered purple/pink/blue reactive lighting

The hardest part was balancing:

- elegance,

- aggression,

- and NMS building limitations.

A lot of compromises had to be made structurally, but honestly… I think those constraints helped shape the ship’s identity.

She’s not a battleship.

She’s a predator.

“Nyx Seraph doesn’t chase targets.

It appears behind them.”

#NoMansSky #NMS #NoMansSkyBuilds #Starship #SciFi #Spaceship #NMSBuilders #BaseBuilding #Gaming #SciFiArt

Hello Hello Games Team,

I would like to report a major issue introduced with update 6.4 regarding custom Corvette-class starship construction.

After updating, many existing Corvette builds are now being forcibly clipped/cropped to fit within a single Corvette landing pad footprint. This appears to be a newly introduced hard size restriction.

The problem is that this change was not clearly communicated anywhere in the patch notes.

The only related line states:

“Fixed an issue that prevented corvettes from landing in the Space Station and the Anomaly.”

However, there is no mention of:

- a newly enforced maximum Corvette size,

- automatic clipping/cropping of existing builds,

- limitations on dimensions,

- or compatibility-breaking changes affecting already-created ships.

As a result, many large custom Corvette builds that worked correctly before 6.4 are now severely damaged visually and structurally.

Examples of what now happens:

- front sections are cut off,

- rear engine assemblies disappear,

- silhouettes are destroyed,

- carefully designed geometry is forcibly cropped,

- ships lose their intended proportions and identity.

This is especially frustrating because many players invested dozens or even hundreds of hours into advanced Corvette designs under the previous system constraints.

From a technical standpoint, the current solution also feels extremely destructive: instead of scaling or validating geometry gracefully, the game appears to apply a hard clipping boundary.

This effectively invalidates a large category of creative builds overnight.

I fully understand the need for performance optimisations and landing compatibility fixes, especially after the “rendering thumbnails for multiple complex corvette-class starships” crash issue mentioned in the patch notes.

However, introducing such a major build restriction without explicitly documenting it is very disappointing.

Please consider:

- restoring previous size behaviour,

- increasing the allowed Corvette dimensions,

- implementing dynamic scaling instead of clipping,

or at minimum clearly documenting these restrictions in the patch notes.

Additionally, if the goal was to solve performance issues caused by certain extremely complex Corvette builds negatively impacting other players, then the real issue is not physical ship size, but part count.

A much better solution would have been introducing a reasonable hard part-count limit, for example around 2000-2500 parts.

Even standard-sized vanilla Corvette builders can easily exceed 1000 parts simply through decorative detailing, and many already reach 2000+ parts without using oversized ship dimensions at all.

This suggests the actual performance bottleneck is build complexity and object count, not Corvette dimensions themselves.

This change has had a massive impact on the creative Corvette-building community.

Thank you for your time.

​

A compact combat corvette derived from my earlier build, #17 Crimson Predator.

The goal was simple: create a much smaller and more agile fighter while preserving the full functionality of a larger capital-style ship. #41 is only slightly longer than #17 due to the extended tail section, but internally it remains a highly efficient micro-corvette.

Despite its compact size, it includes:

Teleporter

Galactic Trade Terminal

Refiner

Nutrient Processor

Mission Radar

Health Station

Hazard Protection Station

Save Point

1st and 3rd person flight viewing options

8 cargo containers

The interior is built around a single small hub, which made space management extremely challenging. Every module had to justify its place, with no room for unnecessary decorations. The result is a dense but fully functional command center.

I originally described the interior as “basic,” but the feedback from the community suggests otherwise. It turns out that even in a very small footprint, it is possible to create something practical, immersive, and visually striking.

#41 Aureus Predator is a compact hunter — small enough to feel nimble, yet equipped to serve as a complete mobile base.

What do you think of this micro-corvette design?