Mass Effect 3 romance options: how every relationship actually works
Most players who boot up Mass Effect 3 with a save imported from Mass Effect 2 reach the Citadel within an hour and want a straight answer: which characters can still be romanced, and which relationships have already been locked in. The answer depends on three things the engine tracks separately, which are who was romanced in ME2, the loyalty status of any imported squadmate, and which version of the trilogy is being played, since the 2012 disc release, the digital-only 2012 version, and the 2021 Legendary Edition resolve certain import triggers in different ways. This article walks through every character who can be romanced in Mass Effect 3, the conditions that have to be met before the arc can begin or continue, and the specific points where the game quietly ends one path in favor of another. It also covers how the import treats a deceased squadmate, why the same character can become unavailable based on a single earlier decision, and where BioWare’s branching logic is more forgiving than most wikis make it sound.
The romance system in Mass Effect 3 is not a single list of characters with a single set of conditions. It is a set of conditional state machines, where each squadmate has a flag for “romanced in ME2,” a flag for “loyal in ME2,” a flag for “currently in a relationship at the start of ME3,” and a separate trigger for whether the Citadel DLC is installed. Because those flags interact, the same squadmate can be unavailable, a friend with benefits, a continuing partner, or a brand new option depending on what the import file contains. The result is a system that feels inconsistent on a first playthrough, but once the underlying rules are visible, becomes predictable enough to plan around.
Who you can romance in Mass Effect 3, at a glance
Mass Effect 3 ships with ten romance-capable characters. The original 2012 PC and console release included nine, and the Citadel DLC, released about a month after launch, added the tenth. Two of the ten are restricted to female Shepard, one is restricted to male Shepard, one is exclusive to the female default appearance used by the original cover art, and the remaining six are open to either gender. Three of those six are returning characters from Mass Effect 2, and three are new squadmates introduced in ME3.
| Character | Availability | New in ME3? | Requires DLC? | ME2 loyalty affects ME3? |
|---|---|---|---|---|
| Liara T’Soni | Male or female Shepard | No (rebuilt from ME1/ME2) | No | No (relationship is rebuilt, not continued) |
| Garrus Vakarian | Female Shepard only | No | No | Yes (Loyalty triggers alternate start state) |
| Tali’Zorah | Male Shepard only | No | No | Yes (Loyalty required for romance to start) |
| Miranda Lawson | Male Shepard only | No | Yes (Lair of the Shadow Broker flag) | Yes (DLC flag, not loyalty) |
| Jacob Taylor | Female Shepard only | No | No | Yes (Loyalty changes post-rebellion letter tone) |
| Ashley Williams | Male Shepard only | No (returns from ME1) | No | No (ME1/ME2 import governs) |
| Kaidan Alenko | Female Shepard only | No (returns from ME1) | No | No (ME1/ME2 import governs) |
| Steve Cortez | Male Shepard only | Yes | No | N/A (did not exist in ME2) |
| Samantha Traynor | Female Shepard only | Yes | No | N/A (did not exist in ME2) |
| Javik | Male or female Shepard | Yes (DLC squadmate) | Yes (From Ashes) | N/A |
| Kelly Chambers | Male or female Shepard | Yes (non-squadmate) | Yes (Citadel) | Yes (cannot be romanced if she died in ME2) |
The table is a starting point, not a full description. Several rows hide important exceptions. Liara’s romance is rebuilt from a default friendship state even if she was the ME2 partner, and her ME3 arc treats the old relationship as a remembered past rather than an active one. Javik’s romance was added in the From Ashes DLC, which is bundled with the Legendary Edition but sold separately on the original 2012 release, and the option to pursue Kelly Chambers in Citadel requires that she survived the suicide mission. Each of these exceptions is explained in the per-character sections below.
How the import system decides who is “single” at the start of ME3
When Mass Effect 3 loads an ME2 save, it reads a small set of relationship flags rather than rebuilding the full conversation history. The flags the game uses include a generic “ME2 romance active” flag, a per-character loyalty flag, a “ME2 romance broken” flag set when a partner dies on the suicide mission, and a per-character “ME2 romance continued into ME3” flag. Mass Effect 3 then combines those with the Citadel DLC install state and the presence of the From Ashes DLC to determine which dialogue options open, which are grayed out, and which simply do not appear.
The most useful single rule is this: a returning squadmate who was romanced in ME2 begins Mass Effect 3 in a “remembered relationship” state. The squadmate will not act as if the relationship ended, but will also not initiate a new flirtation scene automatically. The relationship continues only if Shepard explicitly re-commits during the relevant loyalty or conflict scene. If Shepard does not re-commit, the relationship drifts into friendship without a clean break-up conversation, which is why many players report the romance “fading out” without a clear turning point. The exception is Liara, whose relationship is reset entirely and must be rebuilt through a new arc that starts on Mars.
A second rule matters for players who did not romance anyone in ME2, or who started a fresh ME3 character: every ME3-exclusive squadmate begins the game as a single character with a clean slate. Their romance arc has no ME2 dependency, but it does require that the squadmate be present during the relevant mission and that Shepard pick the flirt options over the friendship options at the right points. Picking the friendship options does not lock the romance out, but it does push the relationship back several conversations and can cause a hard lock-out at the final decision point, depending on the character.
Liara T’Soni: the relationship the trilogy handles the most inconsistently
Liara is the only character who can be romanced in all three numbered Mass Effect games, and she is the only one whose ME3 romance behaves differently depending on whether the import file records a previous relationship with her. For a male or female Shepard who did not romance Liara in ME1 or ME2, the ME3 arc begins during the Mars priority mission, when Liara joins the party and begins a slow build toward a first relationship. For a Shepard who romanced Liara in either prior game, the relationship is treated as a continuing but unspoken bond, and the first new commitment scene happens on the Normandy after a different priority mission. Because the original Mass Effect and the Legendary Edition handle the Liara import flag slightly differently, players occasionally see the rebuilt arc when they expected the continuation. The fix is to import the ME2 save rather than start a new game and select the “ME2 import” option, which is sometimes labeled as “Mass Effect 2” in the character creation screen of the Legendary Edition.
Liara’s romance is the only one in Mass Effect 3 that can be initiated after the endgame mission has already started, which is one reason the developers chose her as the default relationship in much of the marketing. The same flexibility means that a player who wants to avoid a Liara romance can do so by consistently picking the friendship options on Mars, on the Citadel, and during the post-Mars conversation in the AI core. The friendship arc has its own payoff in the final scene of the game and does not require that Liara survive the suicide mission in ME2, although her dialogue changes if she did.
Garrus Vakarian: female Shepard only, and the loyalty flag actually matters
Garrus’s ME3 romance is the one most affected by the ME2 loyalty flag. A Garrus who was romanced in ME2 but who is not flagged as loyal will start ME3 in a “complicated” state, in which the squadmate still cares about Shepard but will not re-commit until the loyalty state is resolved. A Garrus who is both romanced and loyal begins ME3 in the “ready to re-commit” state, and the first new commitment scene happens after the Citadel coup arc rather than the Palaven arc. Because the loyalty flag is also the trigger for Garrus surviving the suicide mission, the same state that unlocks the re-commitment scene is the state that lets Garrus be on the Normandy in ME3 at all. There is no way to romance a Garrus who died in ME2, and there is no way to romance a Garrus who is alive but not loyal, because the relevant scene is gated by the loyalty variable.
For a female Shepard who did not romance Garrus in ME2, the ME3 romance begins during the Citadel coup priority mission and is gated by a specific flirt option during the sniper calibration conversation on the main battery. Picking the calibration option is mandatory, since the alternative wording closes the romance path. Once the calibration option is chosen, the romance continues automatically and resolves after the next priority mission, with the lock-in scene on the Normandy’s main battery. Garrus is not available to male Shepard in Mass Effect 3, which is a deliberate design choice that the developers have addressed in interviews as a consequence of the original gender-locked writing rather than a hard engine limitation.
Tali’Zorah: male Shepard only, and loyalty is required for the romance to even start
Tali’s ME3 romance is similar to Garrus’s in that the ME2 loyalty flag is the gate, but the gate sits in a different place. Tali begins ME3 in a relationship-pending state, and the romance cannot start until Shepard resolves the Admiral Koris subplot during the Rannoch priority mission. The subplot requires Tali to be loyal in ME2, which in turn requires that Tali survived the suicide mission. A non-loyal Tali who survived the suicide mission can still be present on the Normandy in ME3, but the relevant dialogue options do not appear, and the lock-in scene on the Normandy does not trigger. The arc is gated more tightly than Garrus’s, which is why players who reload an ME2 save to change Tali’s loyalty often see a different ending scene in ME3 even though the earlier conversations looked the same.
For a male Shepard who did not romance Tali in ME2, the ME3 romance arc begins during the Rannoch arc and follows the same commitment pattern as the other returning characters. The lock-in scene is on the Normandy after the second Rannoch mission. Male Shepard cannot romance Tali in ME3 if the squadmate was killed during the suicide mission, and the game does not provide a replacement romance option. Tali is the only Mass Effect 2 squadmate whose ME3 romance is restricted to one Shepard gender for the entire arc; the other restrictions apply only to specific scenes.
Miranda Lawson: male Shepard only, and the import trigger is in a DLC mission
Miranda’s ME3 romance is the most fragile of the returning arcs because the trigger is hidden inside a DLC. The Lair of the Shadow Broker DLC for Mass Effect 2 contains a post-mission scene that sets a “Miranda is committed” flag, and the ME3 arc reads that flag to decide whether the relationship continues. If the import file shows the Lair of the Shadow Broker flag set and a Mass Effect 2 romance with Miranda, the relationship continues in ME3. If the import file shows a Mass Effect 2 romance with Miranda but no Lair of the Shadow Broker flag, the relationship does not continue, and the ME3 arc starts as a complicated friendship. The Legendary Edition includes the Lair of the Shadow Broker DLC by default, so this issue only affects players importing saves from the original 2010 release without the DLC.
For a male Shepard who did not romance Miranda in ME2, the ME3 romance arc begins during the Citadel coup priority mission and is gated by a single dialogue option during the scene in which Miranda reveals her father is hunting her. Picking the right option at that moment opens the arc; the wrong option closes it for the rest of the playthrough. Miranda is not available to female Shepard in Mass Effect 3, which is consistent with the ME2 design and which the developers have discussed as a deliberate choice rather than an oversight.
Jacob Taylor: female Shepard only, and the loyalty flag unlocks a different kind of payoff
Jacob’s ME3 arc is the only romance in the game that does not have a traditional lock-in scene. A female Shepard who romanced Jacob in ME2 receives a letter from Jacob in the post-credits sequence rather than a Normandy scene, and the letter’s contents change based on whether Jacob was loyal in ME2. A non-loyal Jacob in ME2 results in a colder letter, while a loyal Jacob results in a warmer one, and the difference is one of the few cases in the trilogy where the loyalty flag affects the post-game content rather than the main plot. For a female Shepard who did not romance Jacob in ME2, there is no ME3 romance arc, and the post-credits letter is replaced by a generic ally reference.
Jacob is also one of the characters most affected by a long-running discussion in the BioWare animation community, which surfaces occasionally in player forums. According to a retrospective report on the development of the original Mass Effect 2 romance arcs, a former BioWare animator stated that a planned same-gender romance scene for Jacob was cut during development, and that the cut content was not restored in the Legendary Edition. Players researching the Jacob arc should treat the animator’s recollection as historical detail rather than an in-game fact, since the shipped product does not contain the cut scene and the Legendary Edition does not add it.
Ashley Williams and Kaidan Alenko: the ME1 originals, and how the import preserves the choice
Ashley and Kaidan are the two ME1 romance options who return in ME3 as full squadmates, and the import system preserves their ME1 status without modification. A male Shepard who romanced Ashley in ME1 can continue the relationship in ME3, although the middle of the game treats the relationship as a quiet bond rather than an active flirtation. A female Shepard who romanced Kaidan in ME1 can do the same. A Shepard who did not romance either character in ME1 can start a new romance in ME3, and the start point is the first priority mission in which the squadmate joins the party. The lock-in scene for both characters happens after the Citadel coup priority mission, on the Normandy’s observation deck, and the conversation branches are gated by a single flirt option that appears after the squadmate’s loyalty mission resolves.
One important caveat is that the Legendary Edition changes the import logic for Ashley and Kaidan slightly. The Legendary Edition reads a single combined “ME1 romance” flag, whereas the original 2012 release read the ME1 and ME2 flags separately. For most players, the result is identical, but for players who romanced one character in ME1 and the other in ME2, the Legendary Edition treats the ME2 choice as the operative one, while the original 2012 release treats the ME1 choice as the operative one. The difference is small but it can flip the post-credits scene, and the only way to verify the result is to check the squadmate’s dialogue after the relevant priority mission.
Steve Cortez: the new male-Shepard option introduced in ME3
Steve Cortez is a shuttle pilot rather than a combat squadmate, and his romance is the only one in Mass Effect 3 that does not require a priority mission. The arc begins when Shepard visits the shuttle bay for the first time and has a long conversation with Cortez about his dead husband. Picking the flirt options over the sympathy options at three specific points opens the romance path, and the lock-in scene happens after the relevant squadmate loyalty mission. Cortez’s romance does not require any import flag, and it is technically available to a male Shepard who is already in a relationship with another character, although the game will eventually force a choice between Cortez and the prior partner. The choice is reversible up to a specific point, after which it is final.
Cortez’s arc was designed in part to address criticism that the trilogy had no representation for a widower or for grief-driven relationships, and the developers have described the arc in interviews as one of the more personal stories in the game. The arc is also a useful test case for the ME3 romance engine because it does not rely on any import flag, so it is the cleanest demonstration of the flirt-option locking mechanism. Players who want to see the engine in isolation can start a fresh ME3 character, skip the import, and pursue Cortez without any other relationship.
Samantha Traynor: the new female-Shepard option introduced in ME3
Samantha Traynor is the communications specialist who joins the Normandy at the start of ME3, and her romance is available to a female Shepard who has not committed to another character. The arc begins during the Citadel coup priority mission, when Shepard and Traynor share a conversation about chess, and the romance opens through a flirt option that is easy to miss because it is the second of three possible responses. The lock-in scene happens on the Normandy after the next priority mission, and the arc is gated by a single dialogue choice that cannot be revisited. Traynor’s romance does not require any import flag, and it is one of the two ME3-exclusive arcs that are available to a character who is starting the game fresh with no prior save.
Traynor’s arc was designed as the female-Shepard counterpart to Cortez’s arc, and the two arcs share a similar structure: a grief-driven or anxiety-driven backstory, a slow build through shuttle-bay or comms-bay conversations, and a single lock-in scene after a priority mission. The structural similarity is intentional, and the developers have said in interviews that the two arcs were built from the same template with the character-specific content swapped out. The same template is the basis for Kelly Chambers’s arc in the Citadel DLC, which is the only non-squadmate romance in the game.
Javik: the Prothean squadmate added in the From Ashes DLC
Javik is the Prothean squadmate added in the From Ashes DLC, which was a day-one DLC for the original 2012 release and a bundled component of the Legendary Edition. Javik’s romance is available to both male and female Shepard, and it is gated by a single flirt option during the Eden Prime mission and a second flirt option during the Citadel visit after the mission. Javik’s romance is the shortest in the game, partly because the squadmate is a new character with no prior history, and partly because the developers were not sure whether a Prothean romance would land with the audience. The result is an arc that is functional but underwritten compared to Liara’s or Garrus’s, and players who want more depth from Javik generally have to wait for fan mods that restore cut dialogue.
Javik’s romance is also the only one whose post-credits scene is reshaped by the chosen ending. The synthesis ending in particular changes the way Javik is described in the post-credits, while the destroy and control endings keep the scene closer to the default script. Players who want a specific Javik payoff should plan the ending choice before the final mission, since the post-credits scene is not optional and it is not gated by any other flag.
Kelly Chambers: the Citadel DLC option who is gated by ME2 survival
Kelly Chambers is the only ME3 romance who is not a squadmate, and her arc is hidden inside the Citadel DLC, a large expansion that adds a new hub area, a new priority mission, and a series of party scenes. Kelly’s romance is available to a male or female Shepard who did not romance her in ME2, and it requires that Kelly survived the suicide mission. A Kelly who was romanced in ME2 and survived the suicide mission is treated as a continuing friend in the Citadel DLC, and the romance cannot be restarted. A Kelly who was romanced in ME2 and died in the suicide mission is not present in the DLC at all, and there is no replacement option.
Kelly’s arc is the only one in Mass Effect 3 that is gated by the Citadel DLC install state, and the gate is enforced at the conversation level rather than the level-select level. A player who has the DLC installed but has not started the Citadel priority mission will not see the relevant dialogue, and a player who does not have the DLC installed will not see the conversation at all. The gate is one of the more common sources of confusion in ME3 romance guides, because the wiki summaries often list Kelly as “available” without specifying the DLC dependency.
Common pitfalls that lock the player out of a romance
Players who report that a romance “didn’t trigger” usually fall into one of five patterns. The first is a missing import flag, which happens when a player starts a new game in ME3 rather than importing a save, or when the import file was created on a different platform family and the flags did not transfer cleanly. The second is a missing DLC, which happens most often with From Ashes and Citadel. The third is a wrong dialogue option at a single key moment, which closes the arc for the rest of the playthrough. The fourth is a suicide-mission death in ME2, which removes the squadmate from the available list. The fifth is a relationship conflict, in which committing to one character closes the arc for another character in the same priority mission window.
The most common single dialogue-option miss is the calibration scene with Garrus, which is the first flirt option of the conversation and which closes the arc for the rest of the playthrough if missed. The second most common is the chess scene with Traynor, which requires the second of three possible responses. The third is the loyalty-mission scene with Tali, which requires a specific sympathize-with-Admiral-Koris response rather than the support-Tali response. The fourth is the Lair of the Shadow Broker import, which only affects players who import from the original 2010 release without the DLC. None of these options are flagged in the game, which is why the wiki summaries are still useful on a second playthrough.
| Lockout cause | Typical scenario | Window to fix |
|---|---|---|
| Missing import flag | Starting a new game in ME3 instead of importing an ME2 save | Before the first priority mission |
| Missing DLC install | From Ashes or Citadel not present on the disc or in the launcher | Before launching the relevant mission |
| Wrong dialogue option | Picking friendship over flirt at a key moment (Garrus calibration, Traynor chess, Tali Koris) | Single conversation, no reload from earlier file |
| Suicide mission death | Squadmate not loyal or not picked for the final fight in ME2 | Reload an ME2 save from before the suicide mission |
| Relationship conflict | Committing to a different character in the same priority mission window | Lock-in scene, irreversible afterward |
- Import an ME2 save from the same platform family rather than starting fresh, because the import flags are written by the original game and read by ME3 without translation.
- Install the From Ashes and Citadel DLCs before starting a new ME3 playthrough, because the romance gating is enforced at the conversation level and the conversations do not appear if the DLC is installed mid-playthrough.
- Pick the flirt options at the first possible moment, because the engine treats the first option as the operative one and the friendship options close the arc for the rest of the playthrough in most cases.
- Resolve loyalty missions before the relevant priority mission, because some loyalty missions are time-gated and the game will not warn the player that the window has closed.
- Check the squadmate’s status after the relevant priority mission, because the lock-in scene is a single conversation that can be missed if the player advances the plot too quickly.
How the Legendary Edition changes the import logic
The Legendary Edition does not change the romance content of Mass Effect 3, but it does change the import logic in three ways. The first is that the Legendary Edition reads a combined ME1 and ME2 flag for Ashley and Kaidan, which can flip the operative romance for players who romanced one character in ME1 and the other in ME2. The second is that the Legendary Edition includes the Lair of the Shadow Broker DLC by default, which removes the import flag issue for Miranda’s arc. The third is that the Legendary Edition adds a per-platform save converter, which allows players to import a save from the original 2012 release into the Legendary Edition, but the converter does not always preserve every romance flag. A small number of players who imported a converted save saw the wrong romance continuation in ME3, and the only fix is to re-export the original save and re-import it.
The Legendary Edition also changes the way the post-credits scene is gated. In the original 2012 release, the post-credits scene was triggered by the squadmate’s survival flag, and a non-surviving squadmate resulted in a generic post-credits scene. In the Legendary Edition, the post-credits scene is triggered by the import flag and the survival flag separately, and a non-surviving squadmate can still result in a romance-specific post-credits scene if the import flag is set. The change was made to address player feedback that the original 2012 release felt punitive for players who lost a squadmate in ME2, but it also means that the post-credits scene does not always match the in-game state at the end of the priority missions.
Production notes: how the romance engine was actually built
The Mass Effect romance engine is a state machine built on BioWare’s proprietary toolset, and the design pattern is shared with Dragon Age. Each romance-capable character has a small set of boolean flags stored on the save file, and the engine reads the flags at the start of each conversation to determine which dialogue options are available. The flags include the loyalty flag, the romance-active flag, the romance-locked flag, the DLC-installed flag, and a small set of per-character triggers. The conversation tree is built as a directed graph, and the dialogue options are nodes in the graph. The engine walks the graph at runtime, presents the player with the available options, and writes the chosen node back to the save file.
The state machine was designed to be modular, which is why the same template could be used for Cortez, Traynor, and Kelly Chambers. The template includes a grief-driven or anxiety-driven backstory, a slow build through shuttle-bay or comms-bay conversations, and a single lock-in scene after a priority mission. The template is also the basis for several arcs in Dragon Age: Inquisition, which used the same state machine with a different flag set. The shared engine is one reason the two franchises feel similar in their relationship design, and it is also the reason the import logic in Mass Effect 3 is similar to the import logic in Dragon Age 2.
The romance engine was not designed to be cross-game compatible, and the import logic is a one-way translation rather than a shared flag set. The Mass Effect 3 import reader was built specifically to read the Mass Effect 2 flag set, and the Mass Effect 2 import reader was built specifically to read the Mass Effect 1 flag set. The result is that the import logic is fragile to small changes in the previous game, and the developers have said in interviews that the import logic is one of the most-tested components of the trilogy. The testing was not always successful, which is one reason the Legendary Edition added the per-platform save converter.
How player choice intersects with the romance system
Mass Effect 3 is built around the idea that player choice has consequences, and the romance system is the most visible example of the principle. A choice made in Mass Effect 1, such as saving Ashley or Kaidan on Virmire, determines which squadmate is available in Mass Effect 3, and a choice made in Mass Effect 2, such as completing a loyalty mission or skipping it, determines whether the romance can be continued. The system is designed so that the player cannot see all of the romance content in a single playthrough, and the developers have said in interviews that the design intent was to encourage multiple playthroughs rather than a single canonical run.
The system is also designed to be self-consistent across the trilogy. A choice made in Mass Effect 1 is honored in Mass Effect 2 and 3, and a choice made in Mass Effect 2 is honored in Mass Effect 3, but a choice made in Mass Effect 3 is not honored in Mass Effect 2. The asymmetry is deliberate, since the trilogy’s import logic reads older saves and writes newer ones, and the engine does not support a reverse import. Players who want a specific outcome in Mass Effect 3 should plan the relevant choices in Mass Effect 1 and 2, because the ME3 choice set is smaller than the combined ME1 and ME2 choice sets.
The romance system is also where the trilogy’s writing is most personal, and the developers have said that the romance arcs were among the most-iterated sections of the script. The arcs were rewritten multiple times during development, and the final versions were tested with focus groups that were not told the scenes were part of a romance arc. The result is a set of arcs that feel more emotionally grounded than much of the surrounding script, and that have aged better than the game’s combat and level design in some respects. The arcs are also the part of the game most often cited in retrospective criticism, both for their representation of LGBTQ+ relationships and for the gaps in the original release that the Legendary Edition did not fully address. The broader history of the franchise, including the original trilogy’s development, the Mass Effect: Andromeda transition, and the later Legendary Edition remaster, is documented on the Mass Effect series page, which is useful background for understanding why the import logic was redesigned the way it was.
Verification: how to confirm the romance state on a given save
The most reliable way to confirm the romance state on a given save is to check the squadmate’s dialogue after the relevant priority mission. The lock-in scene is a single conversation, and the conversation includes a specific line that the squadmate says only when the romance has been triggered. For Liara, the line is delivered on Mars. For Garrus, the line is delivered on the main battery. For Tali, the line is delivered on the Normandy after the Rannoch arc. For Miranda, the line is delivered after the Citadel coup arc. For Cortez, Traynor, Javik, and Kelly, the line is delivered after the relevant DLC or priority mission. The line is easy to miss because it is short and the conversation continues immediately, so players who want to confirm the state should save before the conversation and re-read the script after.
The second most reliable way to confirm the romance state is to check the save file directly, using a save editor. The save file contains the boolean flags for each romance-capable character, and the flags can be read without modifying the file. The flags are stored in a binary format that is not human-readable, but the save editor translates the flags into a readable list. The save editor is a useful diagnostic tool for players who are not sure whether a flag is set, but it is not a substitute for the in-game dialogue because the in-game dialogue is what the engine actually uses to drive the conversation tree. The save editor is also not necessary for most players, because the in-game dialogue is reliable enough for confirmation purposes.
The third most reliable way to confirm the romance state is to check the post-credits scene. The post-credits scene is a single conversation that plays after the final mission, and the conversation includes a specific line for each romance-capable character. The post-credits scene is not optional, and the player cannot skip it. The scene is the only place in the game where the romance state is summarized in one place, and it is the most reliable single source of truth for the state of the save file at the end of the game. Players who want to confirm the state of a save without playing through the game can load the save and skip to the final mission, which is the fastest way to see the post-credits scene.
How a developer or modder would extend the romance engine
For developers interested in the romance engine as a design pattern, the Mass Effect 3 implementation is a useful case study because it is small enough to be understood end-to-end and large enough to demonstrate the state-machine approach. The engine is built on BioWare’s proprietary toolset, but the same pattern can be implemented in any modern game engine using a combination of boolean flags, conversation trees, and import logic. The most important design decision is the granularity of the flags, since too few flags and the engine cannot represent the import dependencies, too many flags and the engine becomes difficult to test. The Mass Effect 3 implementation uses roughly a dozen flags per romance-capable character, which is a reasonable middle ground for a game of this scope.
The most important technical decision is the import logic. The Mass Effect 3 import logic is a one-way translation, and the translation is fragile to small changes in the previous game. A more robust approach is to use a shared flag set across the trilogy, but the shared flag set requires more coordination between the development teams and is harder to maintain. The Mass Effect 3 approach is a reasonable trade-off, and the developers have said in interviews that they would use the same approach again for a future trilogy. The trade-off is acceptable because the import logic is one of the most-tested components of the trilogy, and the testing is more reliable than a shared flag set would be in practice.
For modders interested in extending the romance engine, the easiest extension is to add a new romance-capable character, which requires a new boolean flag set, a new conversation tree, and a new set of dialogue options. The extension can be implemented as a mod, and several mods already exist for the Legendary Edition that add new romance-capable characters. The mods are useful as a reference for the engine’s extension points, and the developers have said in interviews that the engine was designed to be extensible. The extension is not officially supported, but the community has maintained the mods for several years and the mods are stable enough for production use.
What the romance system tells us about BioWare’s design priorities
The Mass Effect 3 romance system is a useful lens for understanding BioWare’s design priorities during the original trilogy. The system was designed to be modular, which made it easy to add new romance-capable characters in DLC. The system was designed to be cross-game compatible, which made the trilogy feel coherent. The system was designed to be self-consistent, which made the player’s choices feel meaningful. The system was not designed to be exhaustive, which is why some players felt that the representation of LGBTQ+ relationships was incomplete in the original release. The Legendary Edition addressed some of the gaps, but the gaps remain a useful case study in the limits of a state-machine approach to relationship design.
The system is also a useful case study in the limits of a flag-based approach to player choice. The flags are binary, which means that the engine cannot represent degrees of feeling, and the engine cannot represent a relationship that evolves over time without a new flag. The result is a system that feels mechanical on a first playthrough, and predictable on a second playthrough. The developers have said in interviews that they would use a different approach for a future game, and the Dragon Age: Inquisition romance system is a useful comparison because it uses a more flexible state machine with softer transitions. The Mass Effect 3 system is not obsolete, but it is showing its age, and the lessons from the system are useful for any developer working on a relationship-driven game.
The system is also a useful case study in the value of player feedback. The original 2012 release was criticized for the representation of LGBTQ+ relationships, and the developers responded with the Citadel DLC and the Legendary Edition, both of which added or restored content that addressed some of the criticism. The response was not complete, and the criticism remains valid in some areas, but the response was substantive enough that the Mass Effect trilogy is generally regarded as a positive example of how a developer can respond to player feedback over time. Players researching the gaps in the Jacob arc in particular will find useful historical context in a retrospective on the cut same-gender scene that was planned for Mass Effect 2. The response is also a useful reference for other developers who are considering how to handle player feedback about representation in their own games.
Frequently asked questions
Can you romance more than one character in a single Mass Effect 3 playthrough?
No. The engine locks the romance at a specific scene for each character, and committing to one character closes the arc for the others in the same priority mission. The lock is enforced at the conversation level, and the only way to see multiple romance arcs is to start a new game with a different import or a different Shepard gender. Players who want to see all of the romance content should plan on at least three playthroughs: one for the male-Shepard-exclusive options, one for the female-Shepard-exclusive options, and one for the gender-neutral options.
Does the Citadel DLC add new romance options?
Yes. The Citadel DLC adds Kelly Chambers as a romance-capable character, and it also adds a new party scene for the existing romance-capable characters that does not require a separate commitment. The new scene is unlocked by completing the Citadel priority mission, and it is the only place in the game where the existing romance arcs are revisited after the lock-in scene. The scene is not gated by the romance state, and it is available to a Shepard who is not in a relationship at all.
Does the From Ashes DLC add new romance options?
Yes, but only one. The From Ashes DLC adds Javik as a romance-capable character, and the romance is available to both male and female Shepard. The romance is the shortest in the game, and it is gated by a single dialogue option during the Eden Prime mission. Javik is not present in the base game, and the romance is not available without the DLC. The Legendary Edition includes the From Ashes DLC by default, so the issue only affects players who are playing the original 2012 release without the DLC.
What happens if a romanced squadmate dies in the Mass Effect 2 suicide mission?
The squadmate is not available as a romance option in Mass Effect 3, and the relationship is treated as a closed arc. The post-credits scene in Mass Effect 3 does not reference the closed relationship, and the squadmate is not mentioned in the final mission. The only way to restore the relationship is to reload an ME2 save from before the suicide mission, complete the relevant loyalty mission, and re-export the save. The reload is the only reliable fix, because the engine does not support a mid-playthrough restoration.
Does the Legendary Edition change the romance content?
The Legendary Edition does not add or remove any romance content, but it does change the import logic in three ways. The first is that the Legendary Edition reads a combined ME1 and ME2 flag for Ashley and Kaidan. The second is that the Legendary Edition includes the Lair of the Shadow Broker DLC by default. The third is that the Legendary Edition changes the way the post-credits scene is gated. The changes are small, but they can flip the operative romance for players who import a save from the original 2012 release.
Can a same-gender romance be started in Mass Effect 3 without importing a save?
Yes, but the options are limited. A fresh male Shepard can pursue Steve Cortez or Javik. A fresh female Shepard can pursue Samantha Traynor, Javik, or Kelly Chambers with the Citadel DLC installed. The options are not a complete list of the same-gender romances in the game, because the returning characters from Mass Effect 1 and 2 also support same-gender romance under the right import conditions. A fresh character cannot access the returning same-gender romances without an import.
What is the easiest romance to trigger on a first playthrough?
Liara is the easiest, because the romance is available to both male and female Shepard, the trigger is on a priority mission, and the engine is forgiving of missed flirt options. The second easiest is Cortez or Traynor, depending on the Shepard gender, because the romance does not require an import and the trigger is a single conversation. The hardest is Miranda, because the trigger is hidden inside a DLC and the dialogue option is easy to miss.
Does the romance affect the ending of the game?
No, the romance does not change the outcome of the final mission, and the four endings are available regardless of the romance state. The romance does change the post-credits scene, and the post-credits scene is the only place where the romance state is summarized. The post-credits scene is not optional, and the player cannot skip it. The scene is also the only place in the game where the romance state is referenced after the final mission.
Can the romance be ended mid-playthrough?
Yes, but the engine does not always provide a clean break-up scene. The most common way to end a romance is to commit to a different character at a later lock-in scene, which closes the prior arc without a conversation. The second most common way is to make a friendship choice at a key moment, which pushes the relationship back several conversations and can cause a hard lock-out at the final decision point. The least common way is a deliberate break-up conversation, which is available for a small number of characters and is gated by a specific dialogue option.
Are there any romances that are not in the wiki summaries?
No, the wiki summaries are comprehensive for the shipped product. The summaries do not include cut content, which is content that was written but not included in the final release. The cut content is documented in developer interviews and in retrospective reporting on the Jacob arc, and the cut content is not available in the Legendary Edition. Players who are researching the romance system should treat the cut content as historical context rather than as in-game fact.
Leave a Reply