Legacy of Bhaal mode, one life or bugged?
Tenrecc
Member Posts: 265
So, I've been immensely interested in doing a Legacy of Bhaal run, after having loved mods such as Tactics, Ascension, Solaufein etc. BG 2.0 just arrived, so I rolled a really OP party and set out.
First thing I noticed, I couldn't afford armors. No biggie, I'll pick up some soon enough. I set out, run into a pack of three gibberlings. Main character dies, I reload, gibberlings die in 1 second. I check difficulty, and it's set to Insane now. Check all saves, all are set to Insane except one in Candlekeep. I reload, try again, die with another character, reload, and it's back to insane.
Now, if this really is a built-in Iron Man mode, that really should say when you select the difficulty. Also, it's an incredibly stupid way to design the game. The fun in having really challenging content is doing it a lot of times, adapting each time and finally beating it. Being sliced to bits in seconds by the Eclipse encounter, and after 100 tries you can solo it with a freshly made sorc, for example.
Having your entire run ruined because of one lucky enemy crit is just dumb.
I sincerely hope this is a bug. I can't find any information on it though, wondering if someone here could shed some light on the situation.
First thing I noticed, I couldn't afford armors. No biggie, I'll pick up some soon enough. I set out, run into a pack of three gibberlings. Main character dies, I reload, gibberlings die in 1 second. I check difficulty, and it's set to Insane now. Check all saves, all are set to Insane except one in Candlekeep. I reload, try again, die with another character, reload, and it's back to insane.
Now, if this really is a built-in Iron Man mode, that really should say when you select the difficulty. Also, it's an incredibly stupid way to design the game. The fun in having really challenging content is doing it a lot of times, adapting each time and finally beating it. Being sliced to bits in seconds by the Eclipse encounter, and after 100 tries you can solo it with a freshly made sorc, for example.
Having your entire run ruined because of one lucky enemy crit is just dumb.
I sincerely hope this is a bug. I can't find any information on it though, wondering if someone here could shed some light on the situation.
1
Comments
If you are getting differences after loading the game in Game Difficulty modes, it's a bug. LoB is not intended to be "Iron Man" mode. There should be a documented way of filing a bug report (Look in the Road to 2.0 forum, you'll see it there).
For ANY of the three games, please file a bug if you're seeing a game that is not keeping LoB mode set after a load.
The bug described above just happened to me, so I can confirm it. The behavior is almost identical to http://redmine.beamdog.com/issues/20540 but appears to have gone either misreported or unreported during the beta. I really wish I had just bit the bullet and not worried about doing a clean run for my livestream so I could participate in the beta. I have no clear idea on how to replicate this, except to say that I've reloaded dozens of times this run, and didn't run into the issue until i reloaded an autosave, which triggered it immediately. That could be bad luck or an actual symptom.
I should note that deleting the files mentioned did not resolve the problem, unless the expected behavior for the fix includes "any files already contaminated are contaminated permanently so you'll need to restart from the beginning", which I have not tested, and frankly shouldn't need to. It should be in the description for the fix if it only prevents it from happening again and doesn't fix the damage already done.
In addition, if we have to manually delete game files in order to be able to play LoB mode without it randomly deactivating with no way of fixing the saves that are corrupted, you guys should really do a public service announcement telling all players to just delete those files rather than offering as a troubleshooting option.
There's also this bug redmine.beamdog.com/issues/21962 which also negates the LoB bonuses in an entirely different manner, and is almost impossible to avoid running into, because it happens any time you reload a save file with an creature loaded in the area. It's trivial to replicate to the point of being nearly impossible not to replicate.
Between those two bugs I'm stuck between a rock and a hard place. I have a couple save files contaminated by bug 2, several contaminated by bug 1, and no other save files to fall back on unless I go all the way back to candlekeep, and there's no guarantee that reloading that file won't trigger bug 1 again.
I really hope this gets fixed soon as it seems an entire difficulty setting isn't functioning. If anyone finds a quick and dirty fix to this please let us know.
Intended functioning - Legacy of Bhaal mode stays on regardless of loading saves or console commands.
Trust me when I say we've been working diligently to squash everything we could prior to release and will continue to do so post release.
I'm hoping this isn't the kind of thing where we need to wait for the next patch for it to be available. I assume it will take you guys a couple weeks to get to the next batch of fixes for this patch and that would be a bit disheartening.
In any case best of luck and we'll be there when you get it going.