Difference between revisions of "Enable Debug Logging"
Jump to navigation
Jump to search
imported>Cobalt027 |
imported>Cobalt027 |
||
| Line 1: | Line 1: | ||
[[Category:Bethesda_Scripting_Tutorial_Series]] | |||
The [http://www.creationkit.com/fallout4/index.php?title=Debug_Script Debug] Script offers many methods for diagnosing and tracing execution of Papyrus Scripts such as: | The [http://www.creationkit.com/fallout4/index.php?title=Debug_Script Debug] Script offers many methods for diagnosing and tracing execution of Papyrus Scripts such as: | ||
Revision as of 04:39, 28 July 2016
The Debug Script offers many methods for diagnosing and tracing execution of Papyrus Scripts such as:
Debug.Trace("I'm logged as an INFO message")
Debug.Trace("I'm logged as a WARNING message",1)
Debug.Trace("I'm logged as an ERROR message",0)
Debug.DumpEventRegistrations(self)
However, these methods will not work unless you enable logging:
- Open the file : <Documents>\My Games\Fallout 4\Fallout4Custom.ini
- Populate the Fallout4Custom.ini file with the following:
[Papyrus] bEnableLogging=1 bEnableTrace=1 bLoadDebugInformation=1 bEnableProfiling=1 sDefaultLogOverlay=Papyrus
NOTE: Log output from Fallout 4 will be written to <Documents>\My Games\Fallout 4\Logs\Script\