Siansonea II wrote...
I really think this thread would be better served if we focus on what we want, rather than berating BioWare for what is essentially a fait accompli. No use cryin' over spilt milk, you know. ME2 is a done deal, so what do you want to see in ME3 and intervening DLC?
Well, the new dialogue system of Dragon Age 2 sounds promising. If it works as well as it sound, BioWare is more than welcome to insert it in Mass Effect 3.
I still believe that BioWare should make every romanceable NPC optional for either maleshep or femshep. Most of them were originally planned to be optional for both genders anyway. Doing that would insure that noone would feel left out.
As far as I remember, there have been two different arguments about this. The first one was that making every romanceable NPC bisexual would be unrealistic and would lessen the NPCs personality. Still, when faced with the fact, that neither of the six romanceable NPCs are interested in a s/s relationship is a credible scenario, they suddenly their point of views turn 180. They say I have reality every day, it's a game for crying out loud. A Fantasy. It doesn't have to be a real life simulation. It doesn't have to be realistic. Changing the sexual preference of a NPC wouldn't change his/her personality. For example: A lesbian Ashley would still love poetry, would still love her family, would still be wary of aliens. Only thing that would change is who she shares her bed with.
There are different solutions to this.
Here a few examples:
A: The NPC Sky from Jade Empire was quite easy to romance as a female. Yet it was quite hard as a male. Hard but not impossible. That would make Sky bisexuall but with a strong preference for women. Something similar is possible for Mass Effect.
B: The NPC Juhani from Knights of the old Republic was only romanceable as a female. Still there was no kiss or sex. Only a platonic scene were Juhani and Revan admit their love for each other. Platonic but fullfilling.
The second argument was that changing the sexuality of a NPC would damage the continuity. Honestly, how many TV-Series do you know were two lovers became an item after let's say 5 seasons, despite the fact that they were attracted to each other from the very beginning? For reasons like they didn't want to jeopordize their friendship, one of them was in a relationship already, they feared that they couldn't separate their private and professional life, blablabla. Let's say that John Shepard felt a connection between him and Kaidan but didn't pursue a relationship because fraternization was forbidden, he didn't want to any distractions from the mission and/or Kaidan is a guy. The impact of being literally dead for two years and having survived a suicide mission might force John to revalute his feelings. He might decide to do nothing. Still, he might come to the conclusion that life is too short, and decides to pursue Kaidan romantically, consequences be damned. Might be the best decision in his life.
And last but not least. I'd like the option to play cupid between two romanceable NPCs. Imagine Shepard and Tali are an item. That means 5 potential romantic partners are left single. On the brink of a Reaper invasion, I believe not only Shepard would try to find closure, just in case. Maybe Jacob and Miranda try to rekindle their relationship. Or Miranda and Jack decide to confront each other. (everyone who likes the idea of Miranda and Jack check out Metal Dragon Kiryus Clearly a Mistake on fanfiction.net) Depending on Shepards actions it ends in a catastrophe or a match made in hell.
One last thing. Don't know about you but lovers usually don't call each other by their surname. It irks me a little every time when the romantic partner of Shepard calls him/her Shepard. I know the first name is out, but aren't there petnames in the future anymore. A simple "hey handsome" or "hey beautifull" would do the trick.
Ce sujet est fermé
Retour en haut
