@PhillipDaigle what are your team up to? why the silence?
The weekend, mainly. Don't worry, we're still very much active between Monday and Friday.
What is approximately the status of the patch?
We have six things left to fix and test. One of them is a bit of a nightmare to track down, and it affects multiplayer, but the others should be done relatively quickly.
The quick loot bar is in and working, so for those of you waiting on that, it's coming. We're almost there now.
The work hasn't stopped on BGIIEE either, by the way. A lot of what you see in BGEE right now will directly improve the second game.</blockquote
OMG YES ...... i can smell the patch. make me happy my heroes :-D
We have six things left to fix and test. One of them is a bit of a nightmare to track down, and it affects multiplayer, but the others should be done relatively quickly.
That sounds like a job for the Order of the Errow!
We have six things left to fix and test. One of them is a bit of a nightmare to track down, and it affects multiplayer, but the others should be done relatively quickly.
That sounds like a job for the Order of the Errow!
We have six things left to fix and test. One of them is a bit of a nightmare to track down, and it affects multiplayer, but the others should be done relatively quickly.
That sounds like a job for the Order of the Errow!
I'm also up for it.
Me too. *puts on dark glasses* let the crashes begin! (joke, joke).
To be honest, the Order of the Errow was already working on it. @Gate70, @Troodon80, and I have been trying to figure out this bug since yesterday. We believe we have figured out as much as we can without developer help and have presented our work to @Dee and added some jingle logs to the ticket for the issue. Sorry for not inviting the rest of you! It is good to know we can call on you if we need you again!
Hmmm... Not finding much wrong with this beta, multiplayer aside. Still plugging away at the completist playthrough. Most of the southern maps cleared of quests. All good, apart from the Lightening Bolt spell appears to be broken. Instead of going through enemies and bouncing of walls, it now bounces off bodies... Causing extra mayhem, although I do not think it is intentional, or how it should be implemented.
@Anduin I use Open Broadcaster Software to grab in-game clips. Can be picked up from obsproject.com and took me a while to work out how to get it to focus on the game window but simple after that was done.
@Gate70 Thank you. Still need to master it. Until then. PICKIES
So... I was getting bored killing ogres so I thought... Lets electrify Imoen and Jaheria...
First up Imoen...
As you can see, upon activating the wand... A blast of electricity is sent straight through Imoen, to kill innocent bears in the woods beyond...
Next up Jaheria...
As you can see in the aftershock sprites surrounding Jaheria, she has been hit by a bolt of electricity, yet it has rebounded back at the caster (killing Neera!)
Is it due to Jaheria making a save? No. Blasted myself, a Gnome with high saves only to see me die... Is it because Jaheria is wearing armour? No. It is completely random...
So what is going on? I have no idea. I am vexed, it is the only niggle bothering me about the beta, I have found so far.
PLUS: How much quicker will the Xvart village / Gnoll Stonghold / Kobold Mines be able to be cleared of loot with the quick loot bar! Bring it on!
As you can see, upon activating the wand... A blast of electricity is sent straight through Imoen, to kill innocent bears in the woods beyond...
Next up Jaheria...
As you can see in the aftershock sprites surrounding Jaheria, she has been hit by a bolt of electricity, yet it has rebounded back at the caster (killing Neera!)
Obviously Jaheira had the good sense to wear some rubber boots whilst adventuring, whereas Imoen did not...
I'm guessing "soon". What's really frustrating about all of this is that these progress counters are made available that are supposed to indicate progress, except all of a sudden they stop being updated. And then we wait...
And then there's a new counter, and you tell yourself this time, they're going to stick to it and we'll see the progress advance every day or so. But once again, the counter stops ticking.
I think it would be much better to just stick to Blizzard-like announcements of "It's coming when it's ready" or "soon". These counters are just antagonizing and frustrating people without ever being a good indicator of progress.
EDIT: One other thing that stinks about these counters that I forgot to mention: the people that wander in afterwards and see the counter on the OP. They then make a post asking what's happening and why hasn't it been updated? Then someone of course has to respond "Oh that counter? That doesn't mean anything. They're hard at work behind the scenes, but that counter is useless." It should just be removed from the OP if it's not being used.
Sorry for the mini-rant, but I had to get that off my chest.
I'm guessing that while they fix the issues reported during this phase, there is little point in them counting yes votes. Regardless of the number of yes votes, they need to fix the issues reported during this phase—otherwise the community will see it as a 'half-baked' patch that introduces more bugs.
Regardless of the number of yes votes, they need to fix the issues reported during this phase—otherwise the community will see it as a 'half-baked' patch that introduces more bugs.
I completely agree with what you're saying (yes, I did only select a portion of what you said). However, for this part:
I'm guessing that while they fix the issues reported during this phase, there is little point in them counting yes votes.
I do not agree. Unless you keep up to date with the 11 pages of this thread, there is no way to know on the OP what is happening. So I agree it's not useful to count yes votes, but you shouldn't leave an out-of-date yes-vote count as the only information on your OP. The only information that can currently be gleamed from the OP: 1) there's a counter towards progress! 2) it hasn't been updated for nearly a week...
What would be more useful is an edited OP that states "Progress counter removed as we've found bugs that must be squashed! More news coming soon."
After this post, I promise to go back to my hole and only check the OP once every few days to see if anything has changed like I did before.
- Profsmax.2da "FIRST_LEVEL" value can now be set higher than 2 to let characters place more pips in a proficiency type at level 1 - Clswpbon.2da "GETS_PROF_APR" value can now be set to 1 to allow non-warrior classes and kits to benefit from APR bonuses - Non-party characters now receive proper bonuses and penalties for their weapon proficiencies (or lack thereof)
No, this behavior is intended; it keeps you from being mauled to death by bears when you're reorganizing your inventory or reading spell descriptions.
Well, if I think there are bears around, then I can just pause the game before reorganizing the inventory.
The lovely thing about the way Icewind Dale handled this is that it can go both ways. Baldur's Gate 1 forced the pause off, while Baldur's Gate 2 and Enhanced Edition force it on, but I would rather have the sweet middleground where I, as the player, would be the one to decide, without the game enforcing its own way over me.
Also, the message menu getting swarmed with "PAUSED" "UNPAUSED" "PAUSED" "UNPAUSED" is really irritating.
@Chow Not sure if someone's mentioned this already, but you can achieve this behaviour by playing the game in multiplayer mode. Entering the inventory screen has no effect on the pause/un-paused state of the game. Just found this out by accident.
Edit: and then I realized that some of the other foibles of multiplayer (no quick-load, having to confirm character arbitration every time you load, etc.) make this a pretty unattractive solution.
Just a small bug report. If you get the Madness Most Fowl quest from Kissiq after completing Restoring Melicamp, you're stuck with the quest in your journal.
Just a small bug report. If you get the Madness Most Fowl quest from Kissiq after completing Restoring Melicamp, you're stuck with the quest in your journal.
I don't mean to offend my saying this... But that issue is know from ages ago.
@Dee is currently on a (well-deserved) holiday, so updates to the OP probably won't occur until he returns in a week or so I believe, but work continues unabated.
@Beridel We tried 'it'll come soon!' and nobody liked it much. We can't really win in that respect, so we choose to be more open - given that time spent updating everything here (you'd be surprised at how much time it takes) is time not spent working on the game.
We tried 'it'll come soon!' and nobody liked it much. We can't really win in that respect, so we choose to be more open - given that time spent updating everything here (you'd be surprised at how much time it takes) is time not spent working on the game.
Still, I'd say it's a job not less important. There is a reason why companies have customer service department.
Comments
Woohoo!
Can be picked up from obsproject.com and took me a while to work out how to get it to focus on the game window but simple after that was done.
So... I was getting bored killing ogres so I thought... Lets electrify Imoen and Jaheria...
First up Imoen...
As you can see, upon activating the wand... A blast of electricity is sent straight through Imoen, to kill innocent bears in the woods beyond...
Next up Jaheria...
As you can see in the aftershock sprites surrounding Jaheria, she has been hit by a bolt of electricity, yet it has rebounded back at the caster (killing Neera!)
Is it due to Jaheria making a save? No. Blasted myself, a Gnome with high saves only to see me die...
Is it because Jaheria is wearing armour? No. It is completely random...
So what is going on? I have no idea. I am vexed, it is the only niggle bothering me about the beta, I have found so far.
PLUS: How much quicker will the Xvart village / Gnoll Stonghold / Kobold Mines be able to be cleared of loot with the quick loot bar! Bring it on!
Any dates for v1.3 release?
And then there's a new counter, and you tell yourself this time, they're going to stick to it and we'll see the progress advance every day or so. But once again, the counter stops ticking.
I think it would be much better to just stick to Blizzard-like announcements of "It's coming when it's ready" or "soon". These counters are just antagonizing and frustrating people without ever being a good indicator of progress.
EDIT: One other thing that stinks about these counters that I forgot to mention: the people that wander in afterwards and see the counter on the OP. They then make a post asking what's happening and why hasn't it been updated? Then someone of course has to respond "Oh that counter? That doesn't mean anything. They're hard at work behind the scenes, but that counter is useless." It should just be removed from the OP if it's not being used.
Sorry for the mini-rant, but I had to get that off my chest.
1) there's a counter towards progress!
2) it hasn't been updated for nearly a week...
What would be more useful is an edited OP that states "Progress counter removed as we've found bugs that must be squashed! More news coming soon."
After this post, I promise to go back to my hole and only check the OP once every few days to see if anything has changed like I did before.
Not sure if someone's mentioned this already, but you can achieve this behaviour by playing the game in multiplayer mode. Entering the inventory screen has no effect on the pause/un-paused state of the game. Just found this out by accident.
Edit: and then I realized that some of the other foibles of multiplayer (no quick-load, having to confirm character arbitration every time you load, etc.) make this a pretty unattractive solution.
And i don't agree that 1.1 looks ok...
EDIT: Fixed link.
@Beridel We tried 'it'll come soon!' and nobody liked it much. We can't really win in that respect, so we choose to be more open - given that time spent updating everything here (you'd be surprised at how much time it takes) is time not spent working on the game.
Sorry, couldn't resist.
Have a well deserved rest @Dee!