The Battle of Wayland represents an early engagement within the broader Galactic Civil War. This conflict formed a component of a larger Alliance initiative aimed at securing four Incom-manufactured T-65 X-wing starfighter prototypes. These prototypes were under the protection of Imperial forces stationed on the planet of Fresia.
Following a preceding raid executed to draw the Imperial I-class Star Destroyer Tyranny away from Fresia, the Rebel Alliance uncovered a network of automated sentry drones. These drones were strategically positioned throughout the Fre'ji system to provide early warning to the Imperial Navy regarding any potential disruptions to the Incom Corporation nationalization proceedings.
Leveraging the capabilities of the protocol droid C-3PO, the Alliance formulated a strategy to circumvent the Imperial sentry network. The astromech droid R2-D2 was tasked with infiltrating an uplink station situated on Wayland. The purpose of this infiltration was to register Alliance vessels within the attendance logs of the nationalization ceremony. This measure would enable the Rebels to approach Fresia's surface unimpeded.
The Alliance's strike team established a position in a forest clearing located near the uplink station. R2-D2, C-3PO, and a contingent comprising T2-B tanks and infantry made preparations to advance towards the uplink station. Their objective was to complete their mission swiftly. The preparation phase held immense significance for the battle's outcome, as the Rebels had a clear view of the uplink station from their landing zone. They initiated the development of a plan, coinciding with the Empire's awareness of their presence.
As the Rebel force advanced toward the facility, combat ensued. R2-D2 connected to the uplink station's controls and commenced the extraction of codes that would grant the Alliance Fleet passage through the blockade surrounding Fresia. This process required time, allowing the Empire to dispatch reinforcements. A surge of three Stormtrooper squads and four AT-ST walkers arrived to suppress the Rebel presence.
Subsequently, another wave consisting of three Stormtrooper squads and four AT-ST walkers landed, followed by a final Imperial surge composed of three TIE Maulers and three Stormtrooper squads. Encircled by Imperial forces, the Rebels initiated a desperate defensive maneuver to delay the enemy, providing R2-D2 with the opportunity to retrieve the codes from the uplink station. The Rebels then broke contact and withdrew from Wayland amidst enemy fire.
The landing codes acquired from Wayland were authenticated by the Imperial forces orbiting Fresia, enabling the Alliance to deploy a ground force onto Fresia and initiate an operation aimed at liberating the X-wing prototypes. These starfighters would prove to be invaluable assets to the Rebels, serving them effectively throughout the remainder of the Galactic Civil War.
This battle represents the second mission within the Rebel campaign of the 2006 video game Star Wars: Empire at War. While players have the option to deploy Y-wing bombing runs to support the Rebel soldiers, it is not essential for mission success, and therefore, this article omits them to maintain factual precision.
Attempting to complete the mission's final objective using the game's fast-forward feature can occasionally cause glitches that render the mission unfinishable.
The occurrence of a battle on Wayland contradicts established canon in The Last Command, as the New Republic did not discover Wayland's existence until the Thrawn campaign. Holocron continuity database custodian Leland Chee has yet to address this discrepancy.