| ||For the radiant quest, see Defend.|
|Minutemen main quest: Defend the Castle|
|Go to the Castle|
|Defeat the attackers.|
|Talk to Preston Garvey|
|Reward: 300+ XP|
|Leads to: The Nuclear Option (Minutemen)|
This quest consists of several waves of attackers that spawn and attempt to take over the Castle. Before the first wave, the Sole Survivor is instructed to create defenses to protect the Castle. Afterwards, a broadcast from Radio Freedom will ask all minutemen in the area to assist the Sole Survivor at the Castle. Once this is done, the waves will spawn.
Brotherhood of SteelEdit
Waves consists of one Vertibird and its occupants which put together, consists of a total of ten vertibirds and about thirty Brotherhood of Steel soldiers. Most of the men inside the ship will not be lootable with the exception of ragdolls falling out.
Waves of raiders and attack dogs will attack from either the front side or the back.
- Completing this quest will automatically fail Semper Invicta, Ad Victoriam, Liberty Reprimed, Blind Betrayal, Tactical Thinking and Mass Fusion. However, completing Ad Victoriam while Defend the Castle is active will successfully complete Defend the Castle.
- This quest can be gained by becoming an enemy of the Institute after giving Institute network information to Sturges. For example, getting caught while trying to complete Underground Undercover or by completing Spoils of War. Other ways are to kill any named personnel in the Institute, such as Father.
- Sometimes there is a bug where enemy waves will not move upon spawning or will move in the wrong direction in an attempt to fight other enemies in the area. If the quest appears to be stuck, try looking for the enemy wave nearby, and then drawing them back to the Castle. Synths can also teleport into the player character-made structures, so make sure they are not hidden in or among any place that may appear inaccessible. If the synths cannot be found, continuing the Brotherhood quests through Ad Victoriam where one must "defend Liberty Prime," synths teleport into the fight, including the synths that would have been attacking the Castle, providing the opportunity to kill them. This will also complete the "defending the Castle" mission if it was started, and not completed prior to the Brotherhood Ad Victoriam quest.
- Any companions told to stay at the Castle will participate in the battle, save for those who turn hostile due to siding against their factions.
- Ronnie Shaw will mention the Institute's crows nearby, as a reason for her concern.
- The extra unnamed minutemen that Ronnie calls in may be added to the Castle's settlement population if they survive the battle, potentially causing shortages in resources.
- PC Many quests involving the Railroad, such as the weathervane, and Randolph quests will automatically fail if not completed beforehand.[verified]
- PC It is a possibility that Ronnie Shaw's proper dialogue will not appear to end the quest; the only options that will appear are trading and merchant dialogue, leaving the quest unbeatable. There is no known fix for this bug. (It is possible to instantly end the quest by typing the setstage console command: SetStage 000bdb04 450) [verified]
- PC Xbox One Sometimes, enemy waves will not move upon spawning or will move in the wrong direction in an attempt to fight other enemies in the area. If the quest appears to be stuck, try looking for the enemy wave nearby, and then drawing them back to the castle. Synths can also teleport into the player character-made structures. [verified]
- PC It is possible to glitch the quest during the synth attack in such a way that all guns, energy weapons, and explosives including Minutemen artillery will cease dealing damage. From that point on, other characters and the player character may fire or throw grenades at each other to no effect, and only bashing or other melee attacks will deal damage.[verified]
- PC This quest was meant to also be a repeatable/radiant quest. However, much like with Defend the Artillery quest, looping errors prevented this from occurring. [verified]
- This seems to have been fixed with official patch 1.3.