2010-07-30, 02:33 PM
I still say they need to revamp the bug report system to something actually practical to make use of this. As others have already said, localization isn't as easy as many people make it out to be, although it is still significantly easier than creation of new content on a time basis. Issues can still come up within the style of formatting and partial or missing translations.
To make true use of a testing system for both parties, even if it is only a public version, they should have a database that testers can access of other user submitted bugs so as to not duplicate the same thing over and over. Additionally, they need to have a classification system to label the detrimental effect of bugs reported, i.e. A, B, C class and so on. Now, I know that NEXON does a terrible job overall for their content, but it does have to be accepted that when on a deadline, not ALL bugs can be addressed. Generally, the further from the release date, the more bugs can be addressed.
Ultimately, even if this is a volunteer job, NEXON needs to improve the one thing they've always been terrible at; Communication. If they can't form a bond between coders and testers, this will be a repeat of round 3 again. Granted when I worked it was more of a Love-Hate relationship, especially when I found hitting a button prior to company logos at the start of a game crashed the system when the title I was on when it was put into it's final format (ran fine on the test kit prior to that).
To make true use of a testing system for both parties, even if it is only a public version, they should have a database that testers can access of other user submitted bugs so as to not duplicate the same thing over and over. Additionally, they need to have a classification system to label the detrimental effect of bugs reported, i.e. A, B, C class and so on. Now, I know that NEXON does a terrible job overall for their content, but it does have to be accepted that when on a deadline, not ALL bugs can be addressed. Generally, the further from the release date, the more bugs can be addressed.
Ultimately, even if this is a volunteer job, NEXON needs to improve the one thing they've always been terrible at; Communication. If they can't form a bond between coders and testers, this will be a repeat of round 3 again. Granted when I worked it was more of a Love-Hate relationship, especially when I found hitting a button prior to company logos at the start of a game crashed the system when the title I was on when it was put into it's final format (ran fine on the test kit prior to that).