STEP:Mod Testing: Difference between revisions
From Step Mods | Change The Game
MadWizard25 (talk | contribs) No edit summary |
MadWizard25 (talk | contribs) No edit summary |
||
Line 83: | Line 83: | ||
These ini tweaks will allow you to see if and mod issues are caused by errors in the mods scripts. Not all mods will contain scripts though. Again the easiest way to apply these is create a sperate ini file in Wrye Bash's INI Tweaks folder. This tweak is applied to the Skyrim.ini file. The log files can be found where your save games are, in the Scripts folder. | These ini tweaks will allow you to see if and mod issues are caused by errors in the mods scripts. Not all mods will contain scripts though. Again the easiest way to apply these is create a sperate ini file in Wrye Bash's INI Tweaks folder. This tweak is applied to the Skyrim.ini file. The log files can be found where your save games are, in the Scripts folder. | ||
Papyrus Logging (Skyrim.ini) | |||
[Papyrus] | [Papyrus] | ||
Line 94: | Line 96: | ||
'''Mod Tracing''' | '''Mod Tracing''' | ||
At the moment, in game mod tracing is very basic. Currently for textures, you can open the command console by pressing the ~ key, and click on the texture that you are interested in. In the console command screen you will see its name and reference ID (eight hexadecimal characters, ie "001C8F02"). | At the moment, in game mod tracing is very basic. Currently for textures, you can open the command console by pressing the ~ key, and click on the texture that you are interested in. In the console command screen you will see its name and reference ID (eight hexadecimal characters, ie "001C8F02"). The name and/ or the reference ID may be useful in tracing the object or texture of interest. | ||
= In Game Mod Testing Procedure = | = In Game Mod Testing Procedure = |
Revision as of 11:30, July 19, 2012
Template:Warning Template:Notice Mod Testing for S.T.E.P. -- by MadWizard25, the S.T.E.P. Team and Wiki Editors
- Updated: 11:30:18 19 July 2012 (UTC)