| El Duderino said: @Gnizmo: Yeah I was thinking that... there even is a slim chance that even the tester responsible for this level never saw the bug... but those chances are very slim... if the tester writes there is a chance (even if its just one out of a thousand) that a bug might brake the game I don´t see how it could be overlooked... then again I myself am lazier that the average person and might have let it pass hoping its a one in a million rather than thousand glitch... also I have seen game breaking bugs in better games by better devs... Half Life 2 broke on me half way through because a elevator didn´t move... |
It could have been a case of:
A) Tester reports bug.
B) Devs check for bug, get luck and see it doesn't happen.
C) Tester runs through their testing again, and the bug isn't reproduced.
D) Game ships.
As a software developer myself, there are some bugs which are so difficult to reproduce, that it might take months before the actual problem is found and fixed. For example, we have a certain bug which occurs maybe once a month in our test environment, only occurs on the single machine at a time (the application works in a multi-user environment) and we have not been able to reproduce it on a development machine to debug as of yet.
While we have an advantage of being able to roll out a patch into production within 24 hours if required, and an ongoing development cycle, Games need to be 'finalised' at some point, and if the bug is considered 'uncommon' out the door it goes. Though it appears from these reports, this is common, and is a sign of a poorly produced game.
