Elder wrote:Paralel wrote:Eh. People, glass houses, stones, etc...
The Vista incompatibility bug for Eternal Eden (which was fatal since it prevented the game from being played) that you didn't know about because you didn't test it on Vista (which was the current shipping OS for Windows based systems when EE was released) was a fairly major mistake as well.
Hey Parallel!

The fact is a little wrong here, Eternal Eden was fully tested under Windows XP and Windows Vista during the development. This bug was very subtle and couldn't be perceived before a special circumstance was met (it's to say that I couldn't know it before it was sold). The bug is a conflict between Windows Vista and the DRM wrapping, not Windows Vista alone. I've even made a fan release to test the selling phase, and this bug went undetected. Let's note that this bug wasn't occuring to everyone using Vista, me included. So it made it thorny to detect before sales. As an alternative, a compatible version (without the DRM wrapping) was shipped to people running Vista, thus no one was offended as the problem was immediately resolved when support was asked. I think 99% of the customers were satisfied with the customer service, even with the Vista Crash included. Since the beginning I received only two major complaints (one of them is a member that wrote a review on gamespot.com)
Anyway, I'm not trying to level myself above any other developer, I hope I’m not giving this impression… I'm not throwing stones at anyone, I'm just trying to inform future developers of the gravity of this situation as many tend to skip the beta testing phase because they think it's not so important. I’m regularly chatting with many new developers and I can confirm that they don’t see the interest of beta-testing when I try to persuade them to take more time before releasing their game. Beta testing is when a product is finished and is being tested as a final step before release.
If you remember well, Eternal Eden was finished during September, but was delayed until december to make sure it would be as clean as possible.
As I said, unexpected bugs can happen, no one can foretell every one of them, but a distinction must be done between someone who completely skipped the beta testing phase and someone who just couldn't see a bug because it was out of sight.
Aveyond and 3 Stars of Destiny are two examples of games that have been tested properly before being released. They weren't totally bug-free, but they could be played.
Not beta testing is unacceptable. Anyone that thinks not beta testing is acceptable either has no understanding of software development or just shouldn't be developing software in the first place. That can only be described as a lack of a fundamental understanding of how software is created. If I found out a buggy piece of software had no beta testing I would be doing a chargeback to my credit card and starting a dontbuythisproduct.com website and blog.
As far as Aveyond being ready before being released I would have to disagree. Version A, the very first version which was released to game portals, had terribly holes in it's story, incomplete dialogue, and several game breaking bugs related to the various modes of locomotion and environments. I got 1/2 way through Version A of Aveyond and actually uninstalled the game because I thought it totally sucked. Version B fixed nearly all of those problems and could actually be considered a complete and playable version of the game.
What can I say? I'm a harsh, but I believe fair, critic.
As far as EE is concerned, and the size of the team involved, all the bugs were handled very well. I think the handling of bugs for EE should be a case example for all other small developers of how it should be done.