STEP:Mod Testing: Difference between revisions
From Step Mods | Change The Game
TechAngel85 (talk | contribs) (→Testing Procedure: Added screenshot and video capturing guidelines.) |
TechAngel85 (talk | contribs) (→General Information: updated some information) |
||
Line 11: | Line 11: | ||
==General Information== | ==General Information== | ||
This guide will attempt to lay out good practices for testing mods to | This guide will attempt to lay out good practices for testing mods marked for testing to be potentially included in S.T.E.P.; as well as, for testing mods should this be asked for or required by the S.T.E.P. team. With a guide as complex as S.T.E.P., it is beneficial to reduce as much variation as possible, since variation can breed a host of issues. This guide will outline standardized testing techniques. The approach will be bottom-up, meaning recommendations will begin at the hardware level, progressing to software and then to mods. | ||
=== Outline === | === Outline === | ||
* Read the | * Read the thread OP and Nexus page descriptions of the mod and make pertinent notes. Note an potential conflicts with other STEP mods or issues with the mod itself. | ||
* Read the Bethesda, Nexus, and Steam forums to develop a sense of user satisfaction and a list of possible bugs to attempt to confirm or deny. | * Read the Bethesda, Nexus, and Steam forums to develop a sense of user satisfaction and a list of possible bugs to attempt to confirm or deny. | ||
* Examine the documentation of the mod, note any lack of clarity, installation and uninstallation directions, and general completeness. | * Examine the documentation of the mod, note any lack of clarity, installation and uninstallation directions, and general completeness. | ||
* Validate the archive package, naming scheme, directory structure, and installation procedure. | * Validate the archive package, naming scheme, directory structure, and installation procedure. | ||
* Use TES5edit to determine quality of edits in any plugin files and the scope of mod. | * Use TES5edit to determine quality of edits in any plugin files and the scope of mod. Note any issue of not carrying over changes from the DLCs and/or from the Unofficial Patches. | ||
* DDSopt used to determine quality of texture compression. | * DDSopt used to determine quality of texture compression for texture mods. | ||
* Examine files in game (to accomplish this we need to research a quick and easy way of identifying the actual name of the (texture, mesh, etc) file corresponding to what we see in game. | * Examine files in game (to accomplish this we need to research a quick and easy way of identifying the actual name of the (texture, mesh, etc) file corresponding to what we see in game.) | ||
* Examine script source of mods for reliability and compatibility (if not available ask the author). | * Examine script source of mods for reliability and compatibility (if not available ask the author). | ||
* All mods with scripts must include methods for installing and uninstalling in game or at the very least stopping scripts with a console command. | * All mods with scripts must include methods for installing and uninstalling in-game or at the very least stopping scripts with a console command. | ||
* Review Papyrus logs for script issues. | * Review Papyrus logs for script issues (if applicable). | ||
* Each mod is examined in multiple ways in game to confirm functionality and compatibility. | * Each mod is examined in multiple ways in game to confirm functionality and compatibility. | ||
** Test in various key spots of the world using savegames. | ** Test in various key spots of the world using savegames. | ||
** Test in various key points of quest development using savegames. | ** Test in various key points of quest development using savegames. | ||
** Test | ** Test with a Baseline STEP installation that is complete and current (All Baseline mods installed. All mods up-to-date. No non-STEP mods installed.) | ||
** Test with a new game and with adding it to an existing game with | ** Test with a new game and with adding it to an existing game with Baseline STEP. | ||
** Note | ** Note quality changes to the game's Appearance, Gameplay, etc. | ||
** Note quantitative changes like VRAM, GPU, CPU, RAM, and FPS usage. | ** Note quantitative changes like VRAM, GPU, CPU, RAM, and FPS usage. | ||
* Complete the Mod Testing wiki form and submit. | * Complete the Mod Testing wiki form and submit. | ||
* Contact mod authors with hard evidence and constructive criticism to improve any area's in need of improvement before becoming a STEP | * Contact mod authors with hard evidence and constructive criticism to improve any area's in need of improvement before becoming a STEP recommended mod. | ||
= Quick Start Guide = | = Quick Start Guide = |
Revision as of 03:43, June 20, 2013
Template:Warning Template:Notice Mod Testing for S.T.E.P. -- by the S.T.E.P. Team and Wiki Editors
- Updated: 3:43:20 20 June 2013 (UTC)