Prey - Deep Storage and Cargo Bays A and B

This post is part of our series of tips for Prey by Arkane Studios. It's not meant to be a comprehensive walkthrough filled with boring common-sense or easily-discovered points of interest, but things that might be tricky or that are easily overlooked.

Technopath

  • There's a Technopath (and other enemies) in the room with the security booth. The Operators here start friendly but if the Technopath gets too close, they will become Corrupted.

Central Data Repository

  • The Cystoid Nests here are immune to fire from the gas pipes, even though the Research data you acquire indicates no Immunities.
Command Center
  • This is where you advance the quest "Disgruntled Employee" if you have it. However once the step is done here, you still have to use a Security Terminal if you actually want a quest marker on him. His name is under the Cargo Bay section.

Data Vaults

  • The Weaver inside can wander into the Electrical Junction (slide 1) but it's really chancy so it can take a while for it to eventually get itself killed.
    • You may have to spot it first to get it moving, either by going into the room and heading for the back, or going up to the piping above. Get it floating around then go handle the Thermal Phantom from the rafters while you wait then come back to snipe it from the padded pipes if it's still not dead.
    • Shooting Explosive Canisters for explosions and to ignite oil on the ground apparently does nothing to it.
  • To Repair the Electrical Junction safely you can first GLOO it from the piping above.
    Deep Storage Safes
    • There are two safes. An additional one is in Confidential Records if you can Hack in (or go through the ceiling -- slide 2). They use the same code.
    • The code is at Danielle Sho's terminal (slide 3).
    Talos I Exterior / Cargo Bay A and B
    • Once you step into a launch tube and the circular door closes, the door won't open for you to return to Deep Storage.
    • You can carry a Turret into the pod, but it will not be in the pod with you when you are transitioned to the Talos I Exterior map. The scripted scene is probably meant to transition you to the exterior and the pod you entered is on a different map now.
    • The other pod has supplies, presumably assembled by Danielle Sho when she launched it to escape Talos I.
    • Dayo Igwe
      • When you first get his quest you probably don't know where to go. Approach the breach and Sarah Elazar will give you separate quest instructions that coincide with what you need to do.
      • Once his container has docked you can use that one to continue the main quest task given by Sarah Elazar.
      • He has quite a bit to say once rescued and later when he relocates. Visit him at least a couple of times as he also gives you interesting things.
    • Moving containers around does not seem to attract Cystoids so the low-ammo way to take them out will still be to throw things at them.
    • The Cargo Bay Security Safe is part of a quest Sarah Elazar gives you later. She'll say something different if you've got the stuff from inside before seeing her for the first time.
      • If you don't want to Hack, you can still hear her different dialog. Go get the code from her, then reload a previous save where she hasn't spoken with you. The code will be valid even though she hasn't given it to you.
    • Sarah Elazar has a Transcribe with a few interesting audiologs on it but she must be dead in order for you to acquire the Transcribe off her person.
    • You CAN get "The Nightmare is Haunting You" here, after the area is supposedly secured. IT will probably start in Cargo Bay B but because you cannot shut the door to that area, it can come through and start attacking security guards patrolling Cargo Bay A.
    • There is an event that will result in Sarah Elazar relocating everyone to Life Support.
      • However if you come back here, it seems some characters are still here, even some that are also at Life Support.
      • There will also be a functional Military Operator Dispenser which should not actually be working by the time that event has occured.

    Comments