Overview

The Pirate Grenadier was a Space Pirate field trial built around an experimental energy grenade launcher. The Logbook calls the weapon a mixed blessing. Its projectile output was powerful, but the bearer had to leave the normal rifle behind, and a fast opponent could close distance until the launcher became comparatively ineffective. The role was specialized through subtraction as much as addition.

That trade changed the Grenadier's place in a formation. Ordinary Pirate Troopers could move between rifle fire and close pressure; the Grenadier converted the same sentient body into a long-range explosive-support platform. It required distance, a usable firing lane, and enough time to charge and release a shot. When those conditions disappeared, the apparent improvement became a burden.

Only four normal Grenadiers are documented in the released encounter record: a pair in the Agon Wastes Command Center and a later pair at the Path of Eyes in Temple Grounds. The small sample does not prove total production, but it supports the Logbook's description of experimental field use rather than a mature weapon issued across the Pirate expedition.

Experimental Program and Operator Selection

No source identifies Grenadiers as a hereditary caste, altered species, fixed age group, or population native to Aether. The role began with an existing Pirate combatant assigned a launcher and trained around its demands. Selection likely favored patience, spatial judgment, and the willingness to hold position while other troops created the distance the weapon required.

The experiment tested more than projectile output. Pirate command needed to know whether one soldier could carry the system through operational corridors, acquire a moving target, manage the charge interval, and survive after surrendering the standard rifle. A successful detonation did not answer whether the resulting unit was worth the tactical inflexibility it introduced.

The operator also became inseparable from the trial. Every missed shot could be blamed upon aim, every close-range failure upon positioning, and every successful blast upon the launcher. The institution could call the weapon promising while treating the individual wearing its disadvantages as expendable evidence. Experimental status protected the project more reliably than it protected the tester.

Training therefore centered on prediction rather than simple marksmanship. A rifleman corrects aim continuously while firing; the Grenadier committed to a future impact point and trusted terrain, allied pressure, or the target's own momentum to keep that prediction useful. Crews drilled the reading of doors, ramps, machinery, and retreat paths because the weapon was strongest when the battlefield had already been reduced to a small number of choices.

Launcher Architecture and Charge Cycle

The launcher was large enough to displace the rifle from the Grenadier's loadout. Released encounter models also omit the standard close-combat scythe, but the Logbook explicitly confirms only that the rifle was left behind. The archive should preserve that difference between visible configuration and stated program requirement.

Encounter observation shows a charging interval before projectile release. That interval telegraphs the attack and gives a mobile opponent time to leave the expected blast zone. The weapon's power therefore depended less on surprise than on restricting available movement. A shot aimed into a constrained lane could be dangerous even when its timing was obvious.

No released scan provides the launcher's power source, exact range, blast radius, recharge period, ammunition count, damage chemistry, or guidance system. “Energy grenade” identifies the Pirate weapon class without converting it into tabletop force damage or a conventional chemical explosive. The correct technical conclusion is functional: charged area pressure at distance, with poor response after that distance collapses.

Body and Loadout Tradeoff

The Grenadier remained a sapient Pirate soldier in issued combat armor. The launcher changed balance, stance, field of view, and available arm use, but no source documents a unique physiology, genetic modification, or dedicated armored subspecies. The operational body was a standard combatant narrowed around an oversized tool.

Leaving the rifle behind removed the ordinary ranged fallback. If the grenade line became unsafe or ineffective, the bearer could not simply change weapons and continue as a conventional trooper. Encounter observation shows close-range ramming instead: the armored body became an emergency weapon when the designed firing relationship failed.

Ramming should not be mistaken for the unit's primary doctrine or proof of great melee skill. It was the blunt answer remaining after specialization removed flexible options. The action exposed the launcher, forced the bearer into the range the Logbook identified as a weakness, and demonstrated that the role's heaviest equipment could not solve the problem it created.

Firing Geometry and Combined-Arms Use

The Grenadier controlled space most effectively when another feature controlled movement first. Walls, raised platforms, machinery, doorframes, and allied troops could narrow the target's escape choices while the grenade charged. The launcher did not independently dominate a room; it converted constrained geometry into explosive consequence.

This made ordinary Pirate personnel part of the weapon's practical support. Rifle troops could occupy the fast target, discourage a direct rush, or force movement across the Grenadier's chosen line. The Grenadier could in turn punish a stationary opponent or break a position that small-arms fire had failed to clear. This combined-arms reading is DSI reconstruction, but it follows directly from the scan's contrast between power at range and vulnerability to fast closure.

The arrangement also created danger for the Pirates themselves. A blast weapon in an industrial room required firing discipline, and a rushed shot could threaten equipment or allies occupying the same lane. The experimental program therefore measured restraint as much as aggression: when not to fire was part of operating a weapon whose impact extended beyond a single target.

Command Center Field Trial

The first scan opportunity occurred in the Agon Wastes Command Center after Samus's first battle with Dark Samus. When she returned through the Pirate installation with the Dark Beam, two Grenadiers occupied the central command space. Their appearance placed the experimental system inside a facility already disrupted by invasion, dimensional research, and the loss of control over its own routes.

The Command Center offered long interior lines but also multiple approaches and structures capable of breaking sight. It was therefore a meaningful trial rather than an idealized range. A Grenadier could exploit distance across the room, yet Samus could use motion and cover to invalidate the charge cycle. The encounter demonstrated both sides of the “mixed blessing” in the same architecture.

These units could be encountered again in the Command Center on later visits, preserving the first scan opportunity. Their presence should not be expanded into a claim that Grenadiers occupied the entire Agon mining complex. The documented location is specific even if the weapon's role can be analyzed in broader industrial terms.

Path of Eyes Deployment

A second documented pair appeared at the Path of Eyes in Temple Grounds during the route toward Torvus Bog. These Grenadiers did not respawn after their encounter, making the placement a discrete field commitment rather than evidence of a permanent local garrison. The range entry must therefore include Temple Grounds as well as Agon Wastes.

The Path of Eyes changed the geometry without changing the weapon's problem. A transit route offered distance and channelized movement, but an intruder continuing forward could close that distance quickly. The Grenadier's success depended upon using the approach before the approach delivered Samus into the launcher's weak range.

Together, Command Center and Path of Eyes show an experiment tested in two functions: interior facility defense and route interdiction. Four bodies cannot establish an empire-wide doctrine. They do show Pirate command attempting to learn whether a powerful but inflexible launcher could earn a stable place between standard infantry and more expensive elite specialists.

Institutional Cost of Specialization

Pirate weapons culture often treated additional power as self-justifying. The Grenadier challenged that assumption because the new system visibly required surrendering a proven rifle. Command could not pretend the unit had become universally superior; every field report had to account for what the bearer could no longer do.

That cost extended beyond combat. A separate launcher meant dedicated maintenance, handling, training, and replacement components within an expedition already supporting portal research, Metroid containment, mining, and defense against the Ing. Experimental firepower competed with other programs for limited technical attention even before Samus entered the firing lane.

The launcher also imposed a supply problem unlike a rifle's ordinary service cycle. Its exact power source and ammunition architecture remain unreleased, but a field experiment still required technicians to inspect the charge system, verify safe handling, and decide whether damaged equipment should be repaired or quarantined. That support burden explains why a weapon capable of conspicuous destruction could remain scarce: destructive output alone did not make it easy to issue, sustain, or trust.

For the operator, specialization narrowed identity. The soldier was no longer evaluated as a complete trooper but as the carrier of one device: charged correctly, protected adequately, and placed at suitable range. When the launcher failed tactically, the body absorbed the consequence. The project retained the privilege of being unfinished.

Field Assessment and Legacy

Field response should begin with geometry. Identify the charged launcher, expected impact area, available lateral routes, and supporting troops. A direct rush can exploit the documented weakness but becomes dangerous if it follows the most obvious lane. Breaking sight, changing elevation, or forcing the Grenadier to rotate and reacquire may collapse the charge cycle without entering the blast's center.

Any tabletop profile should use three states: charging or aiming at range, releasing an area projectile, and falling back to an armored ram after closure. It should not invent lawful-evil alignment, low-light vision ranges, force typing, opportunity-attack restrictions, or exact charge bonuses as verified record. The weapon's real identity already provides sufficient encounter structure.

The Pirate Grenadier's legacy is a warning about measuring weapons without measuring roles. The launcher was powerful; the soldier carrying it was less flexible. Pirate command gained a blast and lost a rifle, then sent four bodies into the field to determine whether the exchange was worthwhile. The mixed blessing belonged to the program. Its cost belonged to the Grenadiers.