When I see posts like these it perplexes me. I understand the frustration, as a gamer, that there are bugs that can affect my experience in a title I'm really enjoying playing. What I don't understand is the consistent bad behavior of BSN users who assume that game companies are out to get them, or trick them. I can guarantee you that no one spends years of their life on a project in order to pull one over on anyone, especially their fans. To assert otherwise, whether out of anger or misunderstanding, is naive. I think maybe ( very likely ) that the difference is in understanding of the industry, and development as an art. Allow me to drop some Realtalk in an attempt to shorten this gap between us :
How this got by BioWare testing is totally beyond me. There will always be issues and bugs when a game comes out but how testers did not walk up to the designers after 1 hour of play and tell them flat out that this was pure idiocy is beyond me. Either just leave treasure laying around to be picked up or if you want the player to do something give them small chests to open or even if you want to be real sneaky and go one step further and make players use their class to open a container like the doors fine. but to have clay pots that some fighters and rogues have a terrible time hitting, having pots regenerate after being destroyed, etc is looney tunes. As it is it is tough in half the games to loot the pots just because invariably you have one player who runs off to the next encounter well before things are looted.
This is one thing that just must be addressed in a patch. It hurts the fun factor and anything that does that for no good reason is a poor design or implementation decision.
"How this got by BioWare testing is totally beyond me." - It didn't. We have one of the best QA departments in the industry.
"... but how testers did not walk up to the designers after 1 hour of play and tell them flat out that this was pure idiocy is beyond me." - I would agree with you if that had actually happened, but this situation never occurred. In fact that's not even how our bug reporting process works.
"This is one thing that just must be addressed in a patch. It hurts the fun factor and anything that does that for no good reason is a poor design or implementation decision." - Ahh, here is the meat of your issue! Throw away the strawman of the company you've built and this should have been the content of your post. No one chose to introduce a bug into pot destruction. It was not a design choice, nor an implementation decision by engineers. I agree that it does have an impact on fun factor and that's why we're actively working to solve it!
I'm sure bioware knew about it, but the way game releases are working nowadays, (especially under "certain" publishers, EA being one of them) they only fix absolutely 100% game breaking bugs and glitches and push the game out asap to start making money asap and then get to work fixing the problems later (if at all, because they already have your money at this point). The problem is there are no standards or regulations when it comes to games still, so companies are trying to get away with as much as they can. Nice to see bioware isn't above that kind of stuff. Honestly, I'd be happy if they at least put out a statement saying what they are fixing and when it will be released, just ANY sort of communication. Instead all I see if one or two bioware staff members posting here in response to obscure bugs or questions, suspiciously ignoring the big ones that most people are talking about.
"... they only fix absolutely 100% game breaking bugs and glitches and push the game out asap to start making money asap and then get to work fixing the problems later (if at all, because they already have your money at this point). " - This is an extremely cynical and poisonous view of the industry that I see from time to time. The last thing I would want to do after sacrificing so much to ship a title is for someone to be tricked into purchasing it. Its not entirely your fault, there are a number of personalities who would like you to believe this is true because it gets them views and page clicks but I can tell you its unequivocally untrue. I love our fans and I love to see them happy and I am hardly alone in that view. If you buy into this ridiculous conspiracy theory your entire view of the industry will be colored by it, and probably you should find a new hobby until you can get out from under it.
"The problem is there are no standards or regulations when it comes to games still, so companies are trying to get away with as much as they can." - There have been standards in games ever since Nintendo's gold seal in the 80's. We go through stringent and expensive certification processes for the launch of the title and every change we make to it afterward with first party and internally. This is also why patches don't happen at the drop of a hat. They need to be certified so that the game gets better, not worse. If no one truly cared about quality or standards your games would look much different. There are plenty of examples from the NES days that serve as fine examples of this.
It's not "certain publishers", it's a standard practice in game development for a very good reason. Fixing bugs very frequently leads to other bugs. Fixing a pot that refuses to stay broken could very well create a bug that causes people to crash. At a certain point in development, you stop fixing non-critical bugs so that you aren't taking the chance of creating worse bugs. A lot of money goes into prepping for a launch, once the ball gets rolling it's just not worth it to delay launch so you can fix minor bugs that could just as easily be patched after release. It's just the nature of the beast. The issue isn't the practice, it's when deadlines are being set. Ideally, it'd be great if games only released when they were 100% ready, but that's just not how it works. I like devs that make good games to stay in business, and there's a big difference in game sales if a game is released in Nov/December vs if it's released in January. Besides, Bioware's got an excellent track record of patching their games, and at least as far as MP is concerned, providing great DLC completely free.
On a more relevant note, abilities don't deduct their cost or initiate their cooldown unless it hits an enemy (or in some cases, the recently deceased corpse of an enemy). The important part of that is that when playing a mage, you can drop an AoE on top of a pot to destroy it, though I don't believe it works with AoEs that derive their damage from status effects or non-targettable AoEs. Archers can also break pots by shooting at them, as arrows fly where you're aiming. Staves don't work that way because they have a sort of tracking element to their shots which keeps you from firing them up or down.
Also, I'm certain I've seen a dev acknowledge the issue with the pots and that it's being fixed. I just don't care enough to link it for you.
This one gets it. Thank you Azrus. The most important point - Development is an exercise of compromises. If we didn't ship with some bugs we would never ship a product and you would never get to play it. The hard part is balancing which bugs get fixed, and which ones you can live with. We prioritize crashes above broken pots, for instance, and I'm sure you can appreciate that!
This is all well and good but does not address my point that it should have been apparent a LONG time ago that the pots were an issue. I doubt if this just suddenly popped up as a problem. At some point in time they do test the game for how fun it is and how functional is long before any kind of lockdown. Getting really close to ship and not correcting a bug that pops up fine but I refuse to believe this was not in place a long time ago or at least the idea of how to dispense loot was not initiated a long time ago.
Yeah I know how bugs work, I am fully aware that they can come out of nowhere after a minor change elsewhere in a product. The respawning pots are not as much of the issue as having to destroy them with some weapons you have to line up perfectly to hit them with in the 1st place. I find it hard to believe that just popped up in the last moment.
Well, that's exactly how this issue was introduced. It was a very new bug that popped up while we were entering the final days of the project. Don't refuse to believe, come into the light : ) It takes some humility to accept the fact that you don't have a lot of knowledge about how game development works. I would implore you to try, and grow into a better community member. If you have frustrations feel free to post them, but remember that we're human beings and that you should act like a human being while you're here. This goes for a lot of the BSN'ers I've run into in the past weeks. Be excellent to eachother and expect excellence back.