Dyson350;n9901221 said:
But this quest is from a relatively small expansion in comparison to the main game...
It's not, actually. It's the same bug that can affect all other such quests in the game (like the infamous Wolf Gear Chest). From what I gather, whatever is causing the issue can affect literally any chest in any quest at any time.
Dyson350;n9901221 said:
The main problem I have at this point outside of what I just said, is the fact they say its fixed and just a random rare glitch that happens.
Well, not quite. They truly
thought they had it fixed. Later, players started posting...once again...that the @#$%!ng chest wouldn't open. Even if they began their games under the latest version, it would still crop up, if much less regularly. It was
then stated that it is still a random issue, as the problem was
believed resolved...but it actually
wasn't. Human error.
Dyson350;n9901221 said:
Look at how many views this post has, not to mention forums other places have people complaining about it too. It is quite obvious this isn't a rare issue. It is a very common glitch and for them to pretend its not is an insult to our intelligence.
Fixing things like this is not as simple as just spending a few hours carefully reading until the solution is found. It has taken the devs numerous attempts over two years to get even this far. The bug is likely a series of functions that rely on variable values that may or may not occur depending on that player's particular in-game options, choices, and save-state (as well as randomized game functions such as the weather or time-of-day for all we know) conflicting with something already loaded into RAM (which is also subject to enormous variation). Now, even an
exclusive team of programmers would need to systematically move through all of those variables over a period of potentially decades until the issue could be 100% re-created. At that point, I'm sure the root of the issue could be found -- however! -- it's entirely possible even then that the issue would be discovered to be
impossible to fix. Sometimes, the code that causes one bug is a necessary function for other, more important parts of a game. (For example, the fix that ensures the chest opens without fail may prevent creatures and NPCs from spawning until the entire map is reloaded from the main menu, and doing so would result in permanent corruption of the save file. The chest bug would have to remain.)
It's not that people don't care about the bug, it's that there's no way to reasonably continue pounding away at it. Again, in an ideal world where personnel, money, and time were not factors, this would not be an issue for the gaming industry. As it stands, humans are still bound by all of these stupid needs like food, shelter, sleep, family, and limited resources for all of it. Slows
everything down.
So, players will, unfortunately, have to play the expansion as a standalone or try to work around it. Also, while the numbers have accrued over time, we're still talking of (I'm guesstimating) ~100,000 reports of the issue since the game's release. That, believe or not, is almost
nothing. It's a rare bug, though it's extremely common to the people living in the community it affects. (100,000 people is a lot of folks!) But it's still 0.5% of the estimated number of total players. See the issue this creates when trying to "nail down the root of the bug"? This is literally a needle in a
wheat field. That 100,000 people have stepped on. As 20,000,000 people stampeded across the wheat field, many stepping on different needles that
were found.
It's just the reality of imperfect humans trying to do great things. The options are:
1.) Limit game design to simplistic, extremely limited code that can be 100% guaranteed bug-free.
or
2.) Take significant risks and create ambitious, extremely complex experiences that can be 100% guaranteed to contain errors.
As soon as someone discovers the 5th element, let me know and we'll put Leeloo in charge of a game development studio! Then, it will be...
perfect.