Forum Discussion
5 years ago
@Psychotps Thanks I'll keep that in mind next time it comes up. I've already been through Illium so it's a bit late to fix it for me right now without losing some progress, I'm not that worried about it.
Personally I still think this bug should have been fixed considering how 'small' of an issue it is. It would make sense taking into consideration BioWare's other fixes for ME1.
Honestly I wouldn't be surprised if it came down to breakages in how the ME1 stuff is imported into later games that caused them to avoid fixing it. (That or for some weird nostalgic reason)
Personally I still think this bug should have been fixed considering how 'small' of an issue it is. It would make sense taking into consideration BioWare's other fixes for ME1.
Honestly I wouldn't be surprised if it came down to breakages in how the ME1 stuff is imported into later games that caused them to avoid fixing it. (That or for some weird nostalgic reason)
Psychotps
5 years agoSeasoned Ace
Remembering it for next time is probably best then.
Actually, from my own experience with bugs, it appears to be just the opposite. The larger the bug, (or the bigger stink players make) the more likely they'll fix it. Tiny bugs like this, even though they're simple to fix, the devs likely can't be bothered.
I always assumed it was a flaw in ME2's import of the ME1 game, but it's actually a flaw in ME1. I loaded an ME1 save into the save editor and it has the flag mistakenly set too. So, you can actually either load the ME1 save and correct it there, or load an imported ME1 save in ME2 and change it there also. Either will work.
About Mass Effect Franchise Discussion
The fate of the galaxy lies in your hands. Join the Mass Effect community forums and tell us how you'll fight for it.19,173 PostsLatest Activity: 18 hours ago
Recent Discussions
- 18 hours ago
- 2 days ago
- 3 days ago