Is 2.0 worth it?
lololo555
Member Posts: 66
The graphics are awful, but are there any crucial changes to the gameplay?
1
Comments
1. I miss the old character sheet. This new one is goofy.
2. The Advanced AI should be set to off. I really hate having to turn off cast offensive spells. It seems the AI likes to cast a spell just as I'm ordering everyone to focus a particular target and then it cancels the spell. Much easier to just cast the acid arrow. Also the computer doesnt know not to save more powerful spells for things that need it. No, you dont need to cast Flame Arrow on the 1HD Goblin. Even Magic Missile is a waste.
3. The graphics are bad. I would take the old ones any day. Its an old game, leave it alone.
Theres probably more, but I'm at work and cant think of them.
But the main reason to go 2.0 is to be able to equip gear with different hand usage requirements at the same time. For example Longbow can be equipped while dual wielding, or sword/board. You don't have to manually unequip the off hand anymore.
edit: And the Shaman class is new and interesting.
If you are experienced, you can manage without often using the map, or know how to leapfrog. For example, leaving the Underdark I first needed to travel to an Eastern part of the city before I could click on the docks to travel there.
Multiplayer is shot, so do not plan to use it.
The character sheet is poorly designed, and quests appear broken but chunks of instruction can be seen if you click into the "Object Not Found" text. If you have experience, you do not use either of these very often (if at all) and so it is a minor (rather than major) irritant.
All in all, BG2 will be improved when the BG1 UI is adapted to it,
Anyone got any ideas how to solve that one?
Cheers.
Be patient dear complainers. It is a good thing you give them feedback however.
It's not unreasonable to expect bugs of that caliber not to make it to release. It should never get through internal QA. That it did means they were fine with that part of the game not working, simply because it only affects a minority. If you think that is okay, well, that is your prerogative.
And yes, I know you are gonna bring the "How can they miss a bug that breaks the entire game" argument to the table, but I'm sure it will be fixed with most haste, as the bug apparently (judging from your previous statement) is breaking the game for you (and probably several more.)
If you see something like the LoB bug making it to release, it's a clear signal that a decision was made that put LoB players into a category of marginally important users that will have an acceptable negative impact on overall sales. As you yourself said, you didn't play LoB and didn't encounter any issues - for you, the product is fine. For anyone who plays LoB or, gods forbid, *only* plays LoB like me, the game is, however, practically unplayable (you could technically play it if you start a new game *every time you load a savegame*, and why would you ever need to reload in the ultimate difficulty mode anyway, RIGHT?). Again, no one thinks they missed it, and what little insight we have into the bug reporting process (a little more since last week) shows us it was known and reported, in several forms, for a while. The fix "with most haste" is slated for Thursday (for all we know anyway, not like communication has been clear), which means two weeks post release of being unable to play at all. Half a month of not being able to play the product, except in a difficulty mode so trivial it is, to me at least, not worth playing at all. It is the equivalent of "normal" users being forced to play in Story Mode, which I'm sure you'll agree takes away significant amounts of fun if you're used to something else.
Now, of course the time frame for the fix is beyond objective evaluation, and I do understand the niche nature of LoB. Still, I cannot help but find myself in a position where my personal wishes as a consumer are not being met adequately. I also understand that it is unreasonable for me to demand that to change, possibly at the expense of a lot more people. However, that does not mean I should not draw consequences, and as a result spend my time and money on something else that matches my desires more. Which is what I'm doing, and urging anyone in a similar position to do as well. Not as a means of extortion, as some people portray it, but as a responsible consumer response. There are enough products out there waiting to be bought, and while they're certainly not identical, they are at least fungible to a degree that allows choice. That choice should be exercised, and hopefully it will end up creating some sort of feedback, somewhere, to allow for more, different choices in the future. Perhaps even including Beamdog products.
I am not criticizing their decision to do so, at least not unequivocally. I don't know all the processes and decisions that went into those last-minute changes that caused the bug to re-emerge, so I cannot say if they acted negligent in some way. I would suspect not, and that this was all a calculated decision made with the greatest good in mind.
That being said, I can understand the process behind a decision and still be upset with the result. It is not my job as a consumer to go through all the various steps of development, QA, and producing. I judge the end result, and though the process that led to it can influence that judgment, ultimately I am self-serving in my own choices. I spend money on what I enjoy most, and when I enjoy something less for some reason, I look into spending my money on something else. Details matter, but that's the gist of it.
I'm not talking about the 2.0 patch, because I didn't try it(I don't want to break my mods), but about the whole state of the industry. Oh but companies like Beamdog can now deflect criticism by stating that the mob is just furious that there is an trans character. /tantrum
are there any mechanics changing besides spell concentration checks?
I believe they also fixed the bug that exhausting ammunition in a range weapon would leave you with an unreasonably high APR in the melee weapon you pick up again - but that really is a bug fix