LOL, Kitty is whining about people he says are whining. The thing is though, we're not. It would be whining if this game was free but we all paid good money for it so it should work. I understand that programming is complicated. See my earlier posts about Bethesda taking their time to get it right. This isn't some independent game that some guy made out of his basemant. This is one of the biggest multiplatform releases of the year made by one of the biggest gaming developers out there.
I'm not complaining about complainers, you pedant.
I'm pointing out your ignorance on just how difficult it can be to get so much code and scripting to play nice. It's always been a problem that's plagued Bethesda games because of their open-world game structure. I'm pointing out that no matter how much time they can give over to testing, they will still find a problem with something, somewhere in the game, especially in these kinds of games. For all the testing they can do, there will still be some player who will find a new way to "break" the game in a way that the testers and programmers hadn't thought of, simply because of the variety of choices available with the many different possible outcomes for every scenario.
Ever heard the expression, not to bother with making something idiot-proof? Because someone will always make a better idiot. That's kind of the idea I'm getting at.
I've been a software engineer in test for twelve years and I still disagree with you.
Systems are complex, but with good developers, writing decent loosely-coupled code with intelligent error handling, supported by good tests, following good build discipline and with test & beta test teams with good testing skills and adequate domain knowledge and communication channels you can reduce maintenance cost and risk to a point where debugging is not a unreasonably risky activity.
Developing professional software is difficult, but it's not a black art.
And regardless, if I release a build that contains bugs then I want to know about it. If people want to "whine", let them. They've paid their money too.
Then you would probably understand what I'm talking about, and you know well enough that it's not the easiest thing to stay on top of, keeping the coding clean and uniform when you have several teams of people working on various sections of coding and scripting. Especially in a game where much of the scripts intersect with each other, sometimes in ways that cause the conflicts that "break" the game and so on.
And yes, feedback is helpful and important for knowing what's wrong with a product. But whining is not very useful, as opposed to pointing out as much information as possible related to when the issue occurred.
What's more useful to someone needing to fix a game:
"UR GAME IS BROKE FIX IT!!!!!"
or
"There appears to be a problem with the scripting for certain quest objects in that once picked up, they cannot be dropped, even after the related quest is finished. The object is a musical instrument, and one of the quests related to such objects are triggered in the Bards' College in Solitude."
When you're needing feedback, which is more useful to you? The whining?
Me, personally, I'd prefer the reasoned explanation that has a lot more in the way of detail and actually TELLS me about what's happening and what could be related to the issue.
Moreover, I'd love to see some numbers from Bethesda in regards to just how many lines of code there are, and how many running scripts can be had at any given time in the game.
And Bethesda could communicate something, but in this day and age where even the most innocuous of tweets can be taken and turned into a huge pile of speculation or whatever, some companies are more inclined to wait until they have something official that they can make a statement on without having to backpedal or explain away things. They will announce something when they have something to announce, and in the meantime, do what they can to fix things well enough.