Some Mass Effect 1 Quest Decisions Bugged

I don't think you have to worry as long as you have Good Plus ticked because I used one of my own old OG ME saves on that save editor and while my ME 2 save editor showed the right persuade flag, your editor had Intimidate on that particular full parameter and I used another paragon save- yet the same mismatched flag. The first save which was from a full run went through all three games and Feros was saved, all good and everything else

I'd be very careful using Save Editors at the moment for anything but cosmetic editing. It'd be very easy to break saves because they aren't interacting with the files properly. My original save editors were finished programs.

But short and sweet, the save file is fine- the save editor is botching the Jeong flag and they kept the bug for Conrad because it's a fairly iconic thing at this point so happy playing!

@Allison_X5-734I figured the bug was a 'feature' at this point as well, been a while since I have played ME1 and then 2 straight after so I forgot about it. I figured after discovering that they fixed Elanos Haliat in ME1 maybe Conrad 'should' have been fixed but was still bugging out.

I wouldn't touch save editors either at the moment either (at least for saving) It seems like the Trilogy Save Editor is on the way to having LE support but that seems a bit of a ways out, at least there's preliminary support.

So I guess this bug is a feature? Would be nice to know for sure 😃

@projsynchroYes, the bug carries over from ME2's first release years ago and was never fixed. Not even in LE.

There are two flags for dealing with Conrad Verner. Whether you did it paragon or renegade. The bug is, if you did it paragon, the renegade flag also mistakenly gets set.

This can easily be corrected by using the save editor you mentioned. The save editor is working just fine. Just load your save, go into Plot/Imported ME1, and uncheck "[The Fan] Intimidated Him" and save it again.

As long as the save you correct hasn't been to Illium yet, It'll work.

@projsynchro

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.