STEP:Mod Testing: Difference between revisions
From Step Mods | Change The Game
Line 15: | Line 15: | ||
=== Outline === | === Outline === | ||
* Examine the documentation of the mod | * Read the Description page and make pertinent notes. | ||
* 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. | |||
* 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 and scope of mod. | * Use TES5edit to determine quality of edits in any plugin files and the scope of mod. | ||
* DDSopt used to determine quality of | * DDSopt used to determine quality of texture compression. | ||
* 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 | * 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. | ||
* 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 as a solo mod and with a full current STEP installation | ** Test as a solo mod and with a full current STEP installation. | ||
** Note qualitative changes to the game Appearance, Gameplay, etc | ** Test with a new game and with adding it to an existing game with full STEP. | ||
** Note quantitative changes like VRAM, GPU, CPU, RAM, and FPS usage | ** Note qualitative changes to the game Appearance, Gameplay, etc. | ||
** Note quantitative changes like VRAM, GPU, CPU, RAM, and FPS usage. | |||
* 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 recommend. | * Contact mod authors with hard evidence and constructive criticism to improve any area's in need of improvement before becoming a STEP recommend. | ||
Revision as of 00:04, November 8, 2012
Template:Warning Template:Notice Mod Testing for S.T.E.P. -- by the S.T.E.P. Team and Wiki Editors
- Updated: 0:04:08 8 November 2012 (UTC)