The STEP Extended v3.0.0 Guide is now in a (mostly) complete state. I say mostly because it's complete, but still needs some testing done. This testing would normally be completed by our staff, however, we no longer have the staff surrounding the management of Guide release we once did. Due to this, we'd like open v3 of the Extended Guide up to a few beta testers. If you're interested, please continue reading.
What will testers do?
Beta testers will simply play the game with the Extended mod set installed and set up as the Guide dictates. During gameplay testers will keep an eye out for any issues they find. These issues, or bugs, may be caused by individual mods or by the STEP installation. Partly tracking down the cause of bugs will be the job of the testers so modding knowledge is required. Testers will then give full feedback about the bugs found so we can address them and have them fixed before release.
First things first, beta testers must meet the following requirements, no exceptions:
- Beta tester systems must meet the recommend requirements for running the Extended Guide (listed here)
- Testers must have intermediate level of modding knowledge and skill and be willing to help track down issues
- Testers must install the Extended Guide exactly as it is laid out; no deviations, no extra mods
- Testers must start a new game for testing
- Testers must be willing to put in a few hours into playing the game each week
Why the requirements?
Users must meet the requirements to ensure they have stable systems and can provide useful feedback for us to utilize to fix issues when they are found. Lets break these down a bit so everyone is fully aware of our process in this:
- User systems meeting the requirements will allow some standardization and eliminate issues caused by users attempting to play the game on sub-par hardware.
- Intermediate knowledge and skills are required to track down issues. Testers should be comfortable jumping into xEdit to track down plugin related issues, as well as, be able to track down other potential issues. At the very least, testers should be able to describe the issue they've encountered and have a general idea of what is causing the issue.
- For example, "the weapon sounds are playing twice" is not an acceptable level of feedback. This is feedback a beginner level modder would give.
- "The weapons are playing twice due to the mod order and plugin combination of ModX and ModZ" is far better. The issue has been, at least partially, tracked down.
- "The weapons are playing twice due to the mod order and plugin combination of ModX and ModZ on record 01234567" is best. This issue has been fully tracked down.
- The more details we're given, the faster we can sort out issues.
- The next two requirements should be obvious. They are listed to ensure users aren't muddying the waters with extra mods not found in the Guide and to ensure our systems are all the same as far as installation and initialization, which makes testing and tracking down bugs easier and streamlined.
- Finally, testing requires playing. Running randomly around the game is good too and many issues can be found in this manner, but we're also interested in the actual playability of the game. STEP isn't for users wanting to take pretty screenshots and stare at the scenery. It's built for gameplay and gameplay is what testers need to be involved in.
Want to be considered for testing?
So you think you want to be a beta tester after fully reading and understanding the requirements asked of you? Good! We'd be glad to have you on board. To be considered, please post below with the following:
- Your system statistics
- Level of knowledge/skill with the following: xEdit, CK, MO, and general modding knowledge.
- Using your own words, please state your understanding of what the standard BSA/Plugin relationship is and why it matters.
- Using your own words, please state what the STEP Mandates are, your understanding of them, and why they exist.
- Why do you want to be a beta tester?
Answering these things will help us narrow down testers to users who understand STEP and the modding process. This also cuts out annoyances of having to constantly restate why we're doing/using X instead of Y. We want testers who actually understand STEP.
Keep in mind we will only be accepting a limited number of testers, therefore, not everyone who posts will be getting a spot. Users who do get an invitation will be contacted via PM with further instruction, will be given access to a private forum for feedback, and will be added to the "Contributors" user group, which will open up access to a few more forums and let everyone know you've helped shape STEP in one way or another. The testers will also have the first opportunity for future beta testing, when we're in need of this.
- Use this topic to apply with the information above in your post.
- We will not be replying to all users here, though we will answer questions.
- Users will be contacted via PM, if they are being invited into the beta testing.
- What users see and gain knowledge of during the beta testing is confidential.
- You will be asked to keep all knowledge to yourself until release time or until we official announce the information