“ | ” | ||
Lawrence Foster is a minor character in Perfect Dark. He is a brown haired man. His is a technician and assistant of Osgood Potts in the Carrington Institute. During free time from the missions, Foster can be found in the firing range along with Osgood Potts.
Role[]
Foster's only major role during the missions is in Carrington Institute: Defense, where he is taken hostage by the Skedar, along with the rest of the Institute employers. During his capture however, he (along with Potts) arm themselves with a Falcon 2 and fight against dataDyne's shielded brutes carrying deadly K7 Avengers despite them being at a huge disadvantage. Joanna must quickly come to his aid before the enemies gun him down. At the time, Foster was also working on a new weapon that can help penetrate the Shield tech items carried by the dataDyne troops, which Joanna retrieves later in the mission.
Trivia[]
- Foster's name is revealed by the female Institute employer in the last room down the hall of the top floor after the room Stanley Grimshaw is found in, When Joanna visits, she will sometimes notify Joanna that Foster is looking for her, and he'll be in the firing range. He is also mentioned by Daniel Carrington when he provides Joanna information on the prototype RC-P120 he was working on during the Institute's invasion.
- Foster, along with Potts, are the only two Institute staff employees (not counting the CI soldiers) to use a weapon (Falcon 2) and assist Joanna in fending off the Skedar/dataDyne intruders. However, this is temporary as he escapes after being rescued.
- Foster's face is randomly generated as a generic enemy encountered during the missions. His face is also permanently applied on the unlockable Co-Op Perfect Buddy, Hotshot, a CI soldier dual-wielding separate model DY357s (N64 version only).
- Foster's head is actually one of the game's main developers, as seen with the Team Heads Only cheat.
- For unknown reasons, during the Institute Defense mission, the auto-aim is applied on Foster (and Potts) despite not being an enemy. This is likely a developer oversight.