STEP:Mod Testing: Difference between revisions
From Step Mods | Change The Game
TechAngel85 (talk | contribs) No edit summary |
TechAngel85 (talk | contribs) |
||
Line 254: | Line 254: | ||
Read the mod's thread opening post (OP) or workflow in the Mod Testing Forum. | Read the mod's thread opening post (OP) or workflow in the Mod Testing Forum. | ||
:There an outline of what needs to be tested for the particular mod can be found. Make note of this and use it when testing begins. | :There an outline of what needs to be tested for the particular mod can be found. Make note of this and use it when testing begins. | ||
=====Step 2 - Nexus Page===== | =====Step 2 - Nexus Page===== | ||
Read the Nexus Page in it's entirety | Read the Nexus Page in it's entirety | ||
:Read the mod's Nexus page description completely as well as the changelog (if provided). Make note of any special installation/uninstall instructions, of any known issues with the mod or mod compatibility issues, and of any potential conflicts with the DLCs and/or other STEP mods. The changelog can often provide a sense of where the author is taking the mod and what might be expected from a mod and its author. | :Read the mod's Nexus page description completely as well as the changelog (if provided). Make note of any special installation/uninstall instructions, of any known issues with the mod or mod compatibility issues, and of any potential conflicts with the DLCs and/or other STEP mods. The changelog can often provide a sense of where the author is taking the mod and what might be expected from a mod and its author. | ||
=====Step 3 - Mod's Forums===== | =====Step 3 - Mod's Forums===== | ||
Read the Bethesda, Nexus, and Steam forums | Read the Bethesda, Nexus, and Steam forums | ||
:A complete read is not necessary; however, try to develop a sense of user satisfaction and a list of possible bugs to attempt to confirm or deny. This is also a good way to find out how active the author is with the mod. No replies from the author in a long period of time usually indicates they have been absent or may no longer be actively supporting the mod. | :A complete read is not necessary; however, try to develop a sense of user satisfaction and a list of possible bugs to attempt to confirm or deny. This is also a good way to find out how active the author is with the mod. No replies from the author in a long period of time usually indicates they have been absent or may no longer be actively supporting the mod. | ||
=====Step 4 - Documentation===== | =====Step 4 - Documentation===== | ||
Examine the documentation included with the mod | Examine the documentation included with the mod | ||
:Read the Readme and any other documentation which comes with the mod. Note any lack of clarity, installation/uninstall directions, and general completeness. If the mod does not include documentation, please make note of this as well for the final review and mod page creation. | :Read the Readme and any other documentation which comes with the mod. Note any lack of clarity, installation/uninstall directions, and general completeness. If the mod does not include documentation, please make note of this as well for the final review and mod page creation. | ||
=====Step 5 - Validation===== | =====Step 5 - Validation===== | ||
Validate the archive package, naming scheme, and directory structure using your mod manager or 7zip. Observe if the downloaded mod package is properly structured and configured for installation. Detailed information on proper mod package structure for WB can be found [http://wiki.step-project.com/Guide:Wrye_Bash#tab=BAIN_Installers here]. Mod Organizer can also use BAIN type installations; however, FOMODs are preferred which use XML. You can validate the FOMOD XML using an online validation tool. W3Schools has an always up-to-date [http://www.w3schools.com/xml/xml_validator.asp XML Validator]. | Validate the archive package, naming scheme, and directory structure using your mod manager or 7zip. Observe if the downloaded mod package is properly structured and configured for installation. Detailed information on proper mod package structure for WB can be found [http://wiki.step-project.com/Guide:Wrye_Bash#tab=BAIN_Installers here]. Mod Organizer can also use BAIN type installations; however, FOMODs are preferred which use XML. You can validate the FOMOD XML using an online validation tool. W3Schools has an always up-to-date [http://www.w3schools.com/xml/xml_validator.asp XML Validator]. | ||
=====Step 6 - DDSopt===== | =====Step 6 - DDSopt===== | ||
Used DDSopt to determine quality of texture compression for texture mods. The [http://wiki.step-project.com/Guide:DDSopt DDSopt Guide] can help; however, knowledge of texture compression and familiarity with DDSopt will be required. | Used DDSopt to determine quality of texture compression for texture mods. The [http://wiki.step-project.com/Guide:DDSopt DDSopt Guide] can help; however, knowledge of texture compression and familiarity with DDSopt will be required. | ||
=====Step 7 - TES5Edit===== | =====Step 7 - TES5Edit===== | ||
* Inspect the mod in TES5Edit to determine quality of edits in any plugin files and the scope of mod | * Inspect the mod in TES5Edit to determine quality of edits in any plugin files and the scope of mod | ||
:* Make note of any issues of not carrying over changes from the DLCs and/or from the Unofficial Patches. Also note any conflicts with mods already in STEP. Knowledge of TES5Edit and conflict resolution will be required for this step. Even though it's not for Skyrim, [http://newvegas.nexusmods.com/mods/38413/ this guide] will help in learning TES5Edit. | :* Make note of any issues of not carrying over changes from the DLCs and/or from the Unofficial Patches. Also note any conflicts with mods already in STEP. Knowledge of TES5Edit and conflict resolution will be required for this step. Even though it's not for Skyrim, [http://newvegas.nexusmods.com/mods/38413/ this guide] will help in learning TES5Edit. | ||
=====Step 8 - Installation/Uninstall===== | =====Step 8 - Installation/Uninstall===== | ||
Line 281: | Line 288: | ||
* Validate the uninstallation procedure | * Validate the uninstallation procedure | ||
:* Note any leftover files which the uninstallation failed to remove | :* Note any leftover files which the uninstallation failed to remove | ||
=====Step 9 - Inspection===== | =====Step 9 - Inspection===== | ||
Line 286: | Line 294: | ||
:* Make note of any file conflicts | :* Make note of any file conflicts | ||
Using a mod manager, take note of any conflicts that appear against vanilla Skyrim files and other STEP mods. The process is different for each mod manager so you should be familiar how to do this in your chosen manager (MO is the recommend manager for testing). For mods with BSA archives, extract these archives into loose files to be able to see the conflicts. This can be done easily using BSAopt for WB users. MO provides the option to extract BSAs during installation of the mod. | Using a mod manager, take note of any conflicts that appear against vanilla Skyrim files and other STEP mods. The process is different for each mod manager so you should be familiar how to do this in your chosen manager (MO is the recommend manager for testing). For mods with BSA archives, extract these archives into loose files to be able to see the conflicts. This can be done easily using BSAopt for WB users. MO provides the option to extract BSAs during installation of the mod. | ||
=====Step 10 - Before Testing===== | =====Step 10 - Before Testing===== |
Revision as of 05:21, October 15, 2013
Template:Warning Template:Notice Mod Testing for S.T.E.P. -- by the S.T.E.P. Team
- Updated: 5:21:11 15 October 2013 (UTC)