Skip to corpus content
HIMR Public Corpustimestamped source index

Recording summary · April 2022

[2022-04-18] How to Unlock the Executor Capital Ship in Lego Star Wars the Skywalker Saga [Gzp7pqCyhJg]

AI-generated reading aids, not verified accounts.

These summaries describe what appears in the transcripts. A speaker’s claims are not established facts, and transcription or speaker-label errors can carry through. Check the linked transcripts and original recordings for context.

Months and years group recording metadata—not necessarily when an event happened. Undated recordings remain separate.

Read this recording’s transcript →

Overview

Unlocking the Executor capital ship in LEGO Star Wars: The Skywalker Saga requires completing Episodes 4, 5, and 6, finding the ship in Bespin or Tatooine space, defeating exterior defenses, and clearing the hangar and a boss to obtain a keycard that forces the general's surrender.

The Executor costs 5 million studs to purchase, cannot be flown directly in space, permits internal exploration containing Kyber brick puzzles, and follows the player across star systems.

Themes

Prerequisites and location for finding the Executor capital ship.

Combat phases involved in taking control of the Executor.

Purchase cost and stud display discrepancies.

Ship exploration, Kyber brick puzzles, and operational limitations.

Encountering and destroying a second Executor dreadnought in space.

Developments

Daniel searched Bespin space for the Executor before traveling to Tatooine space, where the ship appeared while flying toward a comet.

Daniel cleared the defensive turrets and TIE fighters, entered the ship's hangar, defeated the boss TT-2005, used the keycard on the machine to drop the force field, and accepted the general's surrender.

Daniel encountered a second Executor after returning to space, destroying its turrets and engines with proton missiles to blow it up.

Uncertainties & gaps

Whether the stud counter showing minus 700 million while the top display showed 3.5 billion was caused by a software glitch or bug.

Whether the immediate spawning of a second Executor in the same location was an intended mechanic or a bug.

Whether the Executor capital ship possesses additional unobserved functions.

Release summaries_41e8738ae15a49a906b67f18 · · Methodology