devicenull
11-23-2004, 16:36
At the moment, the SDK isn't even released, meaning there's nothing to beta test. In fact, it might be awhile before there is anything to alpha test.
However, a lot of you seem excited about beta testing, and I think malex did a good job of commenting about it :)
We would love nothing more than to open up the beta program this instant. Because the SDK isn't out yet, however, there just isn't anything to beta. Be patient. We will put a call out for beta testers, with the requirements and questionnairs to help us find the proper mix of test servers to maximize test-case coverage.
While waiting for the first releases of SourceMod, there are some things you can do to help us pick you as a member of the elite testing team.
The first, and probably most important, thing you have to learn is how to write properly. We are more likely to pick someone who can properly communicate his thoughts in complete, well formed sentences. Sounding like a kid does not help you, even if you are a kid.
Second, learn the technology. Anyone asking to be a private beta tester, and asking about an installer for the first release, is likely to be laughed at. Learn about the Source engine, the console commands, the filesystem layout. Learn about Steam. Learn about the operating system you will be running this on, be it Linux or Windows. Learn how to separate OS problems from application problems. Most of you asking to be on the beta team probably know these things already, but it doesn't hurt to refresh your memory. It also doesn't hurt to know C++ and debugging, so you could not only find problems but also help fix them.
Third, learn how to properly report bugs. This is related to the first and second points, as you have to know the technology to report bugs properly, and you have to know how to write for us to understand you. Read through the AMX Mod X forums for examples of good and bad bug reports; you should be able to sort the good ones from the bad ones easily.
Until there is something testable, sit tight, learn, study, play, whatever. When we have something, we will find you.
\malex\
However, a lot of you seem excited about beta testing, and I think malex did a good job of commenting about it :)
We would love nothing more than to open up the beta program this instant. Because the SDK isn't out yet, however, there just isn't anything to beta. Be patient. We will put a call out for beta testers, with the requirements and questionnairs to help us find the proper mix of test servers to maximize test-case coverage.
While waiting for the first releases of SourceMod, there are some things you can do to help us pick you as a member of the elite testing team.
The first, and probably most important, thing you have to learn is how to write properly. We are more likely to pick someone who can properly communicate his thoughts in complete, well formed sentences. Sounding like a kid does not help you, even if you are a kid.
Second, learn the technology. Anyone asking to be a private beta tester, and asking about an installer for the first release, is likely to be laughed at. Learn about the Source engine, the console commands, the filesystem layout. Learn about Steam. Learn about the operating system you will be running this on, be it Linux or Windows. Learn how to separate OS problems from application problems. Most of you asking to be on the beta team probably know these things already, but it doesn't hurt to refresh your memory. It also doesn't hurt to know C++ and debugging, so you could not only find problems but also help fix them.
Third, learn how to properly report bugs. This is related to the first and second points, as you have to know the technology to report bugs properly, and you have to know how to write for us to understand you. Read through the AMX Mod X forums for examples of good and bad bug reports; you should be able to sort the good ones from the bad ones easily.
Until there is something testable, sit tight, learn, study, play, whatever. When we have something, we will find you.
\malex\