Originally Posted by kanisatha
Originally Posted by Try2Handing
I haven't got back to WotR for 3 days (still at the market quest in the prologue) cause I've been doing my 2nd Kingmaker run and still having fun and I want to finish it. But the posts in here make me think it's best if I hold off on getting back to WotR, but man I'd rather not have to wait for another 2-3 years like with Kingmaker.
Oh come on. Kingmaker was in a perfectly playable (no bugs worth mentiong) state within about 6 months of release max. And claims here of WotR being "buggy" are clearly exaggerated. Yes there are bugs but nothing truly show-stopping, which is eminently reasonable at launch.

And for people whose standard is no bugs at all, good luck finding such a game (and that includes future BG3).

I do have to argue this - I have ran into at least two show-stopping bugs in my playtime, one of which is now preventing me from even continuing the story at all. Full crashes trying to enter Gwerm's Mansion in Kenabres, and then of course constantly crashing attempting to load the Drezen seige. With any luck, the fix they were promising in two weeks time to these x% load crashes will resolve them, but they are still quite disabling. The latter has certainly rained on my parade.

This is not taking into account a copious amount of gameplay and class-related bugs. A simple look at the bug report area on the Owlcat forums will show that there are still quite a few things needing to be ironed out, though no one expected perfection. And from what I've heard of Kingmaker, this is certainly better - so they are learning and improving! Which is great.

I was not expecting bug free, of course - not with how huge this game is, the dearth of options available to you, etc. I was at least hoping there wouldn't be anything to cause complete crashes that effectively halt your progression of the story, though. frown

Originally Posted by ash elemental
Originally Posted by MarbleNest
I honestly saw the Evil "immediately attack" option as a way to be a murder hobo, if one so desires. There have been instances of more analytical or pragmatic yet harsh approaches that are also considered "evil", though, so I think overall there's a fairly good blend in terms of player dialogue options.
"Murder them all" you can do all the same in BG3, and also for the most part in BG1 and 2 (with notable exceptions of immortal npcs). This is why I call it lazy writing, because it requires no thought or effort on the writers part. It is only a matter which npcs the programmers let you kill. The issue is that this is the only option that comes often for now. My character is neutral aligned and I wanted to play a slow corruption before taking the mythic path. I am not interested in playing "suddenly starts killing random folk". I guess she will stay neutral instead.

Well, no one is forced to take the murder hobo options if they don't want to.

Of course it's lazy, because the aspect of being a murder hobo in a tabletop game is one of the laziest and least interesting approaches to playing D&D/Pathfinder/etc. I genuinely do not expect any company making a D&D/esque game to spend all that much time or thought on a murder hobo route's writing, because there's little and less to write for it. It's there for the few types who enjoy it, but at least in my time playing up until the Drezen seige, I saw plenty of evil-coded dialogue options that were fairly subtle or at least pragmatic, a little bit of being a jerk, and overall pretty good options to lean more towards the selfish and 'evil' side of things while not just being a lazy caricature who murders anyone in sight.

Now the reactions to it, I can't really say much about - as, at best, I would take quite neutral options at the lowest, and good options most all other times. It's simply how I play. But by no means do I think their evil options are lacking and shoehorned into being a murder hobo - that's simply one option. The laziest and the easiest.

Originally Posted by Saito Hikari
On the topic of bugs, there is something in all of this. I remember when POE2 launched, there were a lot of people talking about major gamebreaking bugs at various points in the game, though I somehow did not run into any personally as I pretty much marathoned the game in a week.

As far as I recall, my bugs in Deadfire were the result of apparently managing to do quests out of order, which mucked something up in the code. It effectively locked me out of doing the ending I wanted (the Huana), which was incredibly disappointing after I'd poured so many hours into the game, and the things I had apparently done wrong to cause the issue were so far back that I'd effectively have to replay the whole thing again.

I still adore Deadfire, if not quite as much as POE1, but yeah - some of the bugs it still had even so long after launch were pretty crippling at times.

Last edited by MarbleNest; 08/09/21 12:34 PM.