Hiero Glyph wrote...
Atheosis wrote...
When I spend $60 on a product I have a right to expect it to work properly.
Yeah, compare this to purchasing a car. If you purchase a model with air conditioning, anti-lock brakes, satellite radio, bluetooth, etc. and only some of the features actually work properly would you tolerate waiting without a specific timeframe for these issues to get fixed? You purchased the car as advertised and the product was faulty, period. There is no "we'll get it to soon" or "you can still drive the car, right?" While I understand that some fixes may require patience to properly address, the very least the company can do is keep you informed of these issues and their timeframe, and this is at the very minimum.
I agree that it would be nice for them to publish a list of what bugs they are working on.
However-
You never want them to publish a timeframe for bug fixes or content release until the patch or content is ready to go. It just leads to disappointment. Reason is they don't know how long it is going to take to verify the bug, isolate the code, fix the code, verify it eliminated the bug, double check that they didn't break something else while fixing that one. Anyone who wants a timeframe knows squat about programing and how difficult it can be to find a bug as the problem code may be in a section of code entirely unrelated to what you think is happening.





Retour en haut






