Mass Effect 3 Guide Walkthrough Act 2
Geth Comm Hub
In order to complete this mission, you must virtually interact with the geth by interfacing with the geth server. The Geth VI has intercepted research conducted by Cerberus on human/geth interfacing, so it’s confident that it can facilitate the necessary interface required for the mission. More importantly, however, it requires your trust.
Regardless of how you respond, you’ll have to do what it says to complete the mission, so respond in accordance with your Paragon/Renegade leaning to get the points you desire.
Once you’re ready, you land on the Rannoch surface and enter the facility shortly after the Geth VI has cleared it out. The interface pod scans you and creates a virtual version of you to interact inside the server, but you have full control.
The server interior looks like nothing you’ve ever seen, yet somehow looks as you might expect a virtual world to appear. Angular and constructed of cubelike data bits, the server is wide, expansive, and lacks much detail. It’s a machine’s world.
DESTROY FOREIGN CODE
The geth server has been infected with foreign Reaper code. This takes the shape of long, orange strings of data cubes that pulsate with information. The infected code creates weblike connections across the server and frequently blocks your path.
Walk down the glowing path to its end, where an orange strand of Reaper code blocks your way. Open fire on the Reaper code to obliterate it, and the path will autoconstruct itself ahead of you, allowing you to proceed deeper into the server.
Follow the path down and around to another section of infected code and blast it with your weapon. The dead-end path will turn from bright, blinking red, to a solid light blue as it autocompletes and extends deeper into the server.
Continue obliterating malicious code as you go, and follow the path the server lays out for you. If you reach a dead end, search for a section of the path that is either blinking red, which indicates that you must destroy code to proceed, or blinking blue, which simply requires you to step on it to extend the path farther along.
In some cases, you may have to destroy intersecting (crisscrossing) sections of malicious code in order to proceed. If you do, follow the code strings to the bright orange sections and fire on them, then follow the code to its source to completely obliterate it. Do so with the second part of the intersecting string, and the path will autoconstruct.
The first section completes at a server terminal. Walk into it to be transported into the next section of the server.
As you enter the next area, the Geth VI begins to have trouble communicating with you. It asks you to investigate. There is only one way forward, so get moving. Just as before, begin removing infected code until you reach a large, spherical data cluster covered in malicious Reaper code.
To free the data cluster from the Reaper code, fire on the nodes extending out of the data cluster, out to the rest of the server. Target the node connections and open fire until the code is completely removed from that cluster section.
There are three nodes extending out of the first data cluster. Clear a path around the cluster and remove all of the nodes to free the data transmission.
When you remove the shell of Reaper code surrounding the first data cluster, you can view a streaming bit of archived geth history. The video feed reveals the creation of the first geth nearly 300 years ago. Clear a path to the next data cluster and walk around the massive information archive, clearing infected code as you go.
.jpg)
The next data cluster also has three nodes of infected code attached to it. Circle around the cluster and clear out all three to view the next bit of streaming archived information. This data cluster streams information regarding the emergence of the first geth AI.
Walk up to the next server access node and meet up with the Geth VI. It reveals another archived data cluster; this one is of the first geth that ever took up arms against its creator. As the quarians massacred sentient geth, one machine took a first step toward self-preservation.
Step into the next server node and access the next area. This area contains the final data cluster. As you continue in your mission, the quarians and other members aboard the Normandy begin to worry about your progress. Things are getting rough outside the server. Still, you can’t abort, so continue on your current mission and see it all the way through.
By now, the Reaper infection has learned to self-replicate and is counteracting your progress. In this section, simply attacking one section of the corrupted data strings won’t be enough. You’ll need to destroy a weakened section of the Reaper code earlier in the string before attacking the section of infected code in your way.
Starting at the section of code blocking your path, follow the string back to its origin. When you find another bright orange section of the code in that same string, destroy it, then turn your attention back on the code blocking your path. With the other section of the string severed, the code in your way won’t be able to self-replicate and you’ll be able to proceed.
When you reach the next data cluster, follow the path around it to the left and turn toward the far left wall. You’ll see two missing sections of the wall; each one has a strand of weak Reaper code extending into the distance. Blow away the left weak Reaper code segment, then turn around and destroy the first node of infected code on the data cluster.
The second node on the data cluster requires you to destroy two infected sections of malicious code. Follow the node back to a Y-split in the string and destroy both sections of weakened code along the branching paths. One extends into the wall behind you; the other crosses overhead. Once both are destroyed, turn back to the node on the data cluster and remove it.
Repeat this on the third node on the data cluster; it also has a Y-split along the code string. Remove the malicious code from the data cluster completely.
The final data cluster reveals a critical piece of geth/quarian history. Some of the quarian population didn’t agree with the removal of the geth and attempted to intervene on their behalf.
Leave this data cluster and follow the path around to one more corrupted section of code. Just as before, remove infected sections of the string before attacking the nodes on the cluster, and free the data cluster completely. This data cluster shows a piece of geth/quarian history during which the quarians declared martial law.
Finally, follow the path out of this section and back to the Geth VI, near a large sealed data cluster. Walk up to it.
The final data cluster is from 290 years ago. It reveals how the geth spared the quarians as they fled after the Morning War. Meanwhile, in space, all geth begin to malfunction and shut down. Massive geth fighters suddenly go quiet midflight and begin to drift in space.
Your mission was a success. Sprint to the exit point and leave the server. Back on the planet’s surface, you reunite with the Geth VI and several huge geth Prime units.
While you were in the server, the Geth VI transferred the geth from the server into the Prime hardware units. The Geth VI convinced the Prime units to help oppose the Reapers in the war. Your responses to this new revelation will yield Paragon/Renegade points, so respond accordingly. If you trust the Geth VI’s intentions and accept its help happily, you’ll get Paragon points. Do otherwise, and your skepticism will be rewarded with Renegade points.
Back on the Normandy, the quarians, including Admiral Xen, are relieved that the geth are no longer attacking their fleet but remain skeptical of geth Prime’s true intentions.