Teleklos Archelaou
05-05-2007, 18:10
Haven't needed any for a little while now, but it's back to the point where we need a few new testers. We have had a new internal build for a while, but it's not getting the testing that it needs, and we have some specific tests we need run also. So, what would it take to be a beta tester for us?
-First you'd need some time on your hands. Not loads of it, but that doesn't hurt either, but enough to get a good dose of testing done every couple of days maybe.
-New players to RTW need not put themselves up to this, and new players to EB probably shouldn't either, as we need people who have a basic understanding of the mod at least. Seeing lots of problems where there really aren't problems is a hassle for us to explain after all.
-Another thing that we would prefer is if we sort of know you already, at least a little bit from being around the fora. Our first beta test experience famously failed as one of the testers leaked the build directly to other mods, and we definitely want control over who the testers are and we'd feel better about it if we knew you a little, or you've had a track record posting here or at TWC. There are a lot of new things that are added in the new build, and we need people who are going to keep their mouths shut about the new features for sure. So for us to understand the chances for this, be ready to tell us a little bit about yourself also (not in the first post really, unless you think it helps you a lot given things like a college major in one of these areas the mod deals with or other skills in modding and such, but we'll ask you in follow up PM's if we are interested).
-Finally, being really really interested in the mod certainly helps. The beta testers have also been a big source of new EB members over the last couple of years, but that is not to be expected for sure. Some of our last group of testers were so good at solving problems and finding bugs that we brought them onto the team just for that purpose - to help out on the fora answering questions and to keep working on bugs (it helped a lot that they didn't just tell us "there's a bug here", but they pointed out often what code part had a problem and helped find solutions).
That's all I can think of right now. We aren't sure how many folks we need, but I know there is a need right now and we don't have an active beta testing team currently either, so I'm trying to resolve the situation here. Who thinks they have what it takes? :grin:
-First you'd need some time on your hands. Not loads of it, but that doesn't hurt either, but enough to get a good dose of testing done every couple of days maybe.
-New players to RTW need not put themselves up to this, and new players to EB probably shouldn't either, as we need people who have a basic understanding of the mod at least. Seeing lots of problems where there really aren't problems is a hassle for us to explain after all.
-Another thing that we would prefer is if we sort of know you already, at least a little bit from being around the fora. Our first beta test experience famously failed as one of the testers leaked the build directly to other mods, and we definitely want control over who the testers are and we'd feel better about it if we knew you a little, or you've had a track record posting here or at TWC. There are a lot of new things that are added in the new build, and we need people who are going to keep their mouths shut about the new features for sure. So for us to understand the chances for this, be ready to tell us a little bit about yourself also (not in the first post really, unless you think it helps you a lot given things like a college major in one of these areas the mod deals with or other skills in modding and such, but we'll ask you in follow up PM's if we are interested).
-Finally, being really really interested in the mod certainly helps. The beta testers have also been a big source of new EB members over the last couple of years, but that is not to be expected for sure. Some of our last group of testers were so good at solving problems and finding bugs that we brought them onto the team just for that purpose - to help out on the fora answering questions and to keep working on bugs (it helped a lot that they didn't just tell us "there's a bug here", but they pointed out often what code part had a problem and helped find solutions).
That's all I can think of right now. We aren't sure how many folks we need, but I know there is a need right now and we don't have an active beta testing team currently either, so I'm trying to resolve the situation here. Who thinks they have what it takes? :grin: