Our purpose is to provide varied and thorough playtesting for modders. They'll send us a mod, and we'll see how many ways we can break it! This will ease some of the workload on modders, allowing them to spend more time being creative and inventive and less time in testing. Further, testing by a variety of people with a variety of testing conditions (mod configuration, hardware, mod-using/modding expertise) will yield much more comprehensive results than one person testing with one or two configurations.
So, what's in it for the testers? More and better mods! Not to mention how cool it is to know we're getting the first peek at new content for a game we love to play. Thorough playtesting can be a tedious task, but sharing the workload in a community makes it less daunting... heck, it's fun. There, I said it.
Want to join us? If you have Oblivion patched to 1.2.0.416 and can successfully complete a standard drag-drop-and-overwrite mod installation, you're qualified. We need testers of all levels of expertise, with all manner of hardware, and all varieties of mod configurations. Just make a post in the "Join the Guild" thread of http://www.invision.tesalliance.org/forums/index.php?/topic/2116-join-the-guild/. We'll be glad to have you! We'll give you a quick test run, and then you can submit your info & testing conditions http://www.invision.tesalliance.org/forums/index.php?/forum/70-meet-the-testers/.
Are you a modder with a project in need of testing? Sign up at the same spot as testers. Then, check the Cooperative Testing section of our guild forum if you are willing to share your results with other modders for the best volume and variety of results (recommended). If you prefer absolute discretion or are looking for particular testers, check the Closed Testing section.
Rules for Modders
If you would like your mod tested by the Guild, we have two rules you agree to follow:
1. Remain respectful of all testers. They are here to help you and your mod, so whatever they say is for that purpose.
2. Do not use the service frivolously. To be specific:
It is not appropriate to submit a mod for testing if:
- The mod is nowhere near finished, and is not expansive enough to need to be tested in portions.
- The mod (or portion thereof) is so far from finished that testers are unable to discern what is an error and what is simply unfinished.
- The mod is not complex enough to warrant a team of testers.
- The mod has been submitted for testing before, and all the issues reported by the testers have not yet been corrected.
It is appropriate to submit a mod for testing if:
- The mod is finished, but the modder wants to be sure it will work with varying mod, character, and hardware configurations.
- The mod is HUGE, and needs to be tested in portions, thus it shouldn't wait till it's finished to be tested.
- The modder cannot progress further with the mod until it is playtested by someone else.
Rules for Testers
Testers must also adhere to certain rules, both to keep the peace and to make sure the service is worthwhile to the modder.
1. Remain respectful of all modders (and your fellow testers, of course).
2. Never distribute mods that were uploaded for testing.
3. Be timely with feedback and upfront about your availability.
4. If a modder has requested closed testing, don't share information about the mod with anyone except the modder.
5. Feedback should be objective, constructive, and honest, without being disrespectful. To be specific:
Appropriate feedback:
- Incompatibility with other mods
- Hardware limitations, such as debilitating slowdowns in certain areas or during certain quest stages
- Crashes
- Missing resources
- Playability: Could you use it, find it, play through it, etc... with the instructions given?
- Cosmetics (floating/sinking objects, texture quality, sound quality, etc.)
Inappropriate feedback:
- Questioning the modder's taste, not our place
- Questioning the modder's motives, e.g. "This mod is pointless, nobody will want it", also not our place
To clarify this point even further, testers will limit negative feedback to noting flaws in the intended construction of the mod. If a modder wants opinionated feedback, they are free to specifically request it in closed testing - so unless asked, keep negative commentary to yourself.
Respect between testers and modders is required. A show of disrespect in either direction will result in immediate removal from the guild.
Thanks for perusing! If you have any questions, head on over to http://www.tesalliance.org/ and ask!
:goodjob: