It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Katsunami: Well... it IS an Infinity Engine-like game, isn't it?

Even those games had a few patches to work out item, stat and scripting bugs. Beyond that, there have been many fixpacks made by the community to fix the remaining ones, which have amounted to hundreds of them :) This was done 15 years ago (although some fixpacks are still maintained, fixing bugs to this date), so most people take them for granted now.
avatar
gunman_: Not really. If you talk about Baldur's Gate, the only unofficial fixpack (baldurdash) that can be qualified as not a mod, only fixed about 20 minor things (see here). Of course, there are a lot of mods that rebalances spells and stuff, but they are not patches per se.

Also keep in mind that back then there was no open beta and the internet access was very limited, so QA was more difficult.

What happens today it seems that when they allocate the resources given the budget, the QA gets the smallest share, so they end up delivering insufficiently tested products on release date. Sometimes it gets so ridiculous I wonder how they didn't catch some glaring errors, the only rational explanation being there was no QA at all. When BG:EE was released, I spotted a typo in the first 5 minutes and one of the quests in the tutorial was broken :))
Mods or no mods, I don't really mind. There were (are) a lot of of them that fixed one thing or another in Baldur's Gate 1 and 2. Baldurdash, Dudleyville, the Gibberlings fixpacks, EasyTutu and BG:T include a huge amount of fixes on their own.
avatar
Katsunami: Mods or no mods, I don't really mind. There were (are) a lot of of them that fixed one thing or another in Baldur's Gate 1 and 2. Baldurdash, Dudleyville, the Gibberlings fixpacks, EasyTutu and BG:T include a huge amount of fixes on their own.
And, at least in Tutu's case, introduced some bugs. ;) I remember a pretty nasty one involving Beregost that took forever for modders to find and fix. I forget the particulars, but I do remember being very careful about it on my last BG Tutu play-through several years ago.

edit:
Seems it has been fixed for a while now though. And it wasn't the mod that introduced it, apparently. Oh well, it still shows how even the old IE games had some pretty insidious bugs. ;)
Post edited April 03, 2015 by Krypsyn
avatar
Cadaver747: f@ck I can't play in this unpolished state.

First time I broke my rule to wait 6 months from release and this, I'm pretty upset :((((((((((((((
avatar
Katsunami: Well... it IS an Infinity Engine-like game, isn't it?

Even those games had a few patches to work out item, stat and scripting bugs. Beyond that, there have been many fixpacks made by the community to fix the remaining ones, which have amounted to hundreds of them :) This was done 15 years ago (although some fixpacks are still maintained, fixing bugs to this date), so most people take them for granted now.

It's almost impossible to create a game as complex as this one and have it bug-free from the start.
True, it's almost impossible to catch the bugs that happen when you roll at a 15-17 degree angle at a wall then pausing 10-30 ms into the manouevre, unequipping your sword and equipping a fishing rod.

I say they could have probably caught a major bug that happens whenever you use your inventory. It doesn't seem too "out there" that someone in testing could have equipped an item before okaying this build.

Hopefully GoG can get this patch to us sometime this month.
Post edited April 03, 2015 by Rubarack
avatar
Katsunami: Mods or no mods, I don't really mind. There were (are) a lot of of them that fixed one thing or another in Baldur's Gate 1 and 2. Baldurdash, Dudleyville, the Gibberlings fixpacks, EasyTutu and BG:T include a huge amount of fixes on their own.
avatar
Krypsyn: And, at least in Tutu's case, introduced some bugs. ;) I remember a pretty nasty one involving Beregost that took forever for modders to find and fix. I forget the particulars, but I do remember being very careful about it on my last BG Tutu play-through several years ago.

edit:
Seems it has been fixed for a while now though. And it wasn't the mod that introduced it, apparently. Oh well, it still shows how even the old IE games had some pretty insidious bugs. ;)
The Beregost save game bug introduced by TuTu (and BG:T) was.... not fun. After encountering it once, I never used those mods. Also, TuTu has completely idiotic weapon proficiencies as a default. The worst thing when playing BG1 in the BG2 engine is that you can select weapon proficiencies for weapons that are not even in the game, although there are mods to replace weapons in many locations. Some longswords are replaced with Katana's, for example.