Quote from Doorsfan
Re-read what i stated please ; They had the very format of which the AH would obey to, already in a earlier form of development. Assuming that has not gone to be collecting dust somewhere, i can LOGICALLY assume that it is not hard to make this change - And it was also in response to a person who actually went to mock another user for being Vague, and now when i am not being vague for that person, i am getting attacked by pitchforks.
And how i know that it does not require extensive testing with the waller bug? Because they already did increase minimum range of the mortar, how hard it is to actually have a thing FUNCTION as it is supposed to, in contrast to writing me off as if i cannot speak on this forums with authority? The authority i can speak for, is what i paid for - That is a authority you cannot question. And when i payed for D3, it did not say "Littered with bugs".
It is in fact only a BAD thing, so don't make me have to re-evaluate my authority when i am the customer - I paid for this shit, if it's broken - It's to get fixed, the customer is always right.
And no, i do not manage Game systems, i am as a matter of fact a customer who just wants his moneys worth - And that goes above any white knighting you might do on a forum, because at the end of the day, I paid money for a product, that product is to work, if it does not, they are guilty to fix this - because the product cannot do anything but reflect what is advertised.
You want the bugs fixed. I can respect that... and sure, you can ask for them. I took issue with what you said here:
These are things that are actually really f'cking annoying, don't require weeks of testing and really does break the immersion of the game, and further more just serve to be rage inducing because it's such small issues that i repeat, DO NOT REQUIRE weeks of testing, just a f'cking fix.
These are not "small issues". You want them to change the collision detection of mortars; that's not the same as tweaking a number. Collision Detection is far more complex than that.
Yes, they had a different Auction House in 2008 that let you do more. I'm sure that there's a reason it was scrapped besides "they thought the new one looked better". As the amount of filters increases, the query time increases, the bandwidth use increases, etc. It could have been scrapped because it would take minutes to run a search in a real-world environment, or worse the AH webserver or AH dbserver could crash. It also could have been scrapped because of any number of User Experience concerns (accessibility, usability, etc).
I'm a developer in the test area of complex systems, work for a well-known company, and I have a background in game development. I'm not talking out my ass here. Bugs don't get magically fixed; it can take days to write the code to fix some bugs or implement some features. Then, test passes can take days or weeks, which in return cause new bugs to be filed against the unreleased code which also needs to be fixed, then tested again, etc. Once the system is stable, a patch can be released.
Hotfixes are quite different from bug fixes. Hotfixes are just changes to numbers. The mortar range change, for instance, was just a change of numbers in the range calculation: instead of MinRange=10 MaxRange=20, they made it MinRange=20 MaxRange=40. Very little testing needed. Another example of a hotfix is a crash issue; many times this is because the code tries to operate on a variable that hasn't been defined (an easy hotfix is to say "if this isn't defined, skip this operation").
I'm not coming at you with pitchforks; I'm just sick of reading people complain about "bugs with simple fixes" not getting fixed, when they aren't simple. I do the same thing when I hear a bunch of people complaining that Facebook is going to start charging users because they got a forwarded email and believed it.
0
You want the bugs fixed. I can respect that... and sure, you can ask for them. I took issue with what you said here:
These are not "small issues". You want them to change the collision detection of mortars; that's not the same as tweaking a number. Collision Detection is far more complex than that.
Yes, they had a different Auction House in 2008 that let you do more. I'm sure that there's a reason it was scrapped besides "they thought the new one looked better". As the amount of filters increases, the query time increases, the bandwidth use increases, etc. It could have been scrapped because it would take minutes to run a search in a real-world environment, or worse the AH webserver or AH dbserver could crash. It also could have been scrapped because of any number of User Experience concerns (accessibility, usability, etc).
I'm a developer in the test area of complex systems, work for a well-known company, and I have a background in game development. I'm not talking out my ass here. Bugs don't get magically fixed; it can take days to write the code to fix some bugs or implement some features. Then, test passes can take days or weeks, which in return cause new bugs to be filed against the unreleased code which also needs to be fixed, then tested again, etc. Once the system is stable, a patch can be released.
Hotfixes are quite different from bug fixes. Hotfixes are just changes to numbers. The mortar range change, for instance, was just a change of numbers in the range calculation: instead of MinRange=10 MaxRange=20, they made it MinRange=20 MaxRange=40. Very little testing needed. Another example of a hotfix is a crash issue; many times this is because the code tries to operate on a variable that hasn't been defined (an easy hotfix is to say "if this isn't defined, skip this operation").
I'm not coming at you with pitchforks; I'm just sick of reading people complain about "bugs with simple fixes" not getting fixed, when they aren't simple. I do the same thing when I hear a bunch of people complaining that Facebook is going to start charging users because they got a forwarded email and believed it.
2
Are you a game developer? Do you manage complex systems? How on earth do you think that a change to the collision detection system (waller fix) doesn't require extensive regression testing? How do you think that a change to the interface which requires a totally new UI to be built doesn't require a regression pass on all Pri-1/Pri-2 Auction House test cases, as well as usability and accessibility tests because it's a UI change.
Don't talk with such authority if you don't really know what you're talking about.