Why aren't simple/obvious problems fixed?

[Vernah]

I have read several threads about people posting about certain things and what can be done to fix them. Some issues that come to mind include the auction house (search was a great added feature, but the AH could use more work), 20th completion for raids/quests (big one for me), ransacking a chest XX amount of times (and still not receiving an item), etc.

My main question is not what can be done to fix these things, but why haven't they been fixed yet? Unless I just don't understand coding more, these issues can be easily fixed and should be fixed, because a majority of the DDO population agree they need to be fixed.

Is it because Turbine has other priorities that need more attention? Maybe it is because if these were fixed, items would be much easier to obtain? Or perhaps the coding really is more advanced and takes more time to do?

Why do you think these haven't been fixed?

My first thread like this so please be easy on me!

[clkpacker]

It's very likely that while X might be the problem, because of the way Y was coded, X cannot be changed without also changing Y. And if Y is changed, then Z must also be looked at because changes to Y might affect Z. And so on. Large programs that have had lots of updates and changes and such tend to lose their compartmentalization if they're not very carefully managed.

[Eladiun]

Also, none of these sound like problems. They sound like preferences and suggestions. Problems are things like the second boss in Devil's Assault being stuck on a teleport loop.

[Dartwick]

Generally its because solutions are not as obvious as the issues.

[Khanyth]

1. Because what is a "problem" to you or me, may not be a "problem" to someone else.

2. Because what is a "solution" to you or me, may not be a "solution" to someone else.

3. Because some people's "problems" are aspects of the game that are supposed to be that way.

4. Because what you or I might consider to be an "easy and obvious" fix, may not be, coding wise.

5. Because what you or I might consider to be an "easy and obvious" fix, may not be worth it in terms of coding/dev hours that could be spend fixing other pressing issues.

6. Because some solutions offered may lead to bigger problems down the road.


Just 6 that I can think of off the top of my head.

[Amberyll]

Also, none of these sound like problems. They sound like preferences and suggestions. Problems are things like the second boss in Devil's Assault being stuck on a teleport loop.

I have to agree, the suggestions posted by the OP don't seem like problems, while that quoted above, is a problem.

[likuei]

I don't mean to be disrespectful.

One: Yes,the Auction House does have issues. RECENTLY, the most vocal of the people who want a fix are people who, by choosing which financial obligation to the game, are limited. It took awhile for the game to even get a 'search' function. When they figure out how to make improvements, I'm sure they will be implemented, BECAUSE there are so many complaints.

Two: Ransacking. There is NO NEED to fix Ransack. Learning game mechanics will relieve some of the frustration in farming a chest and not getting what you want. Once you get the ransack message, take a few days off so the chest can reset.

Three: 20th completions. Does NOT need a fix. Yes, it can cause grind when you do not have lots of extra time to play, but it is as random as possible. I am a casual player and I do get frustrated sometimes with my loot rolls. But I also learned that it is VERY up and down. When I do pull stuff, often it is an item that I can't use. Make trades or just make someone happy by giving it to a class that can use it (I hate people rolling on loot, give it someone who can use it is how I handle it).

[EyeRekon]

Hi Welcome!

*ducks*

[Vordax]

I have read several threads about people posting about certain things and what can be done to fix them. Some issues that come to mind include the auction house (search was a great added feature, but the AH could use more work), 20th completion for raids/quests (big one for me), ransacking a chest XX amount of times (and still not receiving an item), etc.

What needs to be fixed with 20th raid completion, seems to be working as designed?
What needs to be fixed with chest ransacking, seems to be working as designed also?
AH does not appear to be broken either so what needs to be fixed?

You are asking for fixes, but what you actually want is changes in behavior. Maybe you should actually state what you want.

Vordax

[Ganolyn]

Beacause <string table error; tableDID is taking up all their time and resources, resulting in a total shut down of all outside communication or stimulus until they find that bugger and squash him good!

This PSA brought to you by the haters of <string table error; tableDID

[Falco_Easts]

I've got to agree with the others, the things you mentioned aren't broken OP, they are WAI. They are just not working the way you would like.

[Hollowgolem]

I thought this was going to be about Superior Efficacy/Freeze/Inferno/etc.'s text.

Needless to say, I was disappointed.

[Veileira]

Hey they fixed the guy in COF and he doesn't fry no matter what anymore.

Baby steps, baby steps... maybe someday Turbine will learn how to walk.

[samthedagger]

I have read several threads about people posting about certain things and what can be done to fix them.

...

Why do you think these haven't been fixed?

My first thread like this so please be easy on me!

I think from Turbine's point of view it is a relative labor investment : reward ratio. Many things might seem to be simple fixes, but actually aren't because the way they are coded isn't as simple as it seems. Programmers sometimes make the mistake of using overly-complex code because of legacy issues or bad habit so the code isn't actually easy to fix.

Another possibility is that the fix may actually be simple (requiring only a single day of time from a single programmer) but the mechanic may already have a work-around that, while inconvenient, doesn't break the game. If this is the case, it is more important from a design standpoint to address more critical issues first.

I have no doubt that Turbine's lead developers have enormous laundry lists of stuff they want to fix and have entire meetings about just narrowing down which of those things they intend to address in the next update. Contrary to some popular thought, Turbine recognizes that if the game is too buggy people won't pay for their product. It is therefore incumbent upon them to fix things that are critical to gameplay before simply things that are merely an inconvenience.

And for the record, just because a game mechanic is perceived to be overpowered doesn't mean it is broken. There will always be something that rises to the top and therefore nerfing one thing or buffing another to balance every character ability against each other is never going to change that. You can't have variety without some level of imbalance. I think the developers are satisfied as long as there are a number of viable options to character building, even if some are perceived as better than others.

[Chai]

An interesting demographic would be a ratio of the number of people who complain about fixing obvious issues and try to state as an absolute that its easy to do off the cuff -vs- the number of those same people who have experience in software development, QA, or support.

I bet there are a few people out there who have a pretty clear understanding of how this all works and still make an off base comment from time to time, but I would put my money on people making this type of assumption not having the experience they need to make the statement 95 times out of 100.

Things I hear ALOT in the software industry.

- If something is an "obvious bug" there must be an easy obvious fix, right.

The sarcastic reply: "Yeah sure, we just dont give it to you to make you and thousands of other users squirm. Theres no other reason really" "We have been tossing the disc with the fix on it at eachother over the walls of our office cubes the entire month like frisbee dodge ball. Its currently stuck in the ceiling above the accounting reps desk. We will get to it eventually, and hopefully before the cleaning crew does."

- It used to work in the last version / build. Why cant you just roll the code back?

The sarcastic reply: "Sure, lets just roll back all the new features, content, and other bug fixes, so you can have the fix for the one bug youre moaning about." All this wonderful new stuff that just came out is part of the same code after all.

-Everyone on the internet is having the same issue!!!

The sarcastic reply: And a whopping three of those people out of a customer base of hundreds of thousands, have contacted us about that issue in the 478 days this version has been out. Mass Exodus, ZOMG!!!

- The car analogy!! (customers ALWAYS banter the friggen car analogy) If I bought a car and this happened, they would give me my money back on the spot.

The sarcastic reply: Yeap, those whacky car dealers are always willing to walk into the back lot there where all the money trees are growing and clip a few branches off for a customer each time they call in with an obvious issue. Its just like every pizza joint has a few free pies ready, for every customer who complains about the poor quality food after they ate the entire 16 inch pizza they ordered by themselves, heh.