7
edits
Difference between revisions of "Enable Debug Logging"
m
Correcting paths
imported>Qazaaq (Added to a general tutorial stubs category) |
m (Correcting paths) |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
[[ | The [[Debug Script]] offers many methods for diagnosing and tracing execution of [[Papyrus]] scripts. | ||
The following are some of the most commonly used. | |||
<source lang="papyrus"> | |||
Debug.Trace("This message is written to the papyrus log file.") | |||
Debug.Notification("This message is displayed on the HUD menu.") | |||
Debug.MessageBox("This message is displayed in a message box.") | |||
Debug.CenterOnCell("QASmoke") | |||
Debug.DumpEventRegistrations(self) | |||
</source> | |||
However, these methods will not work unless you enable logging: | However, these methods will not work unless you enable logging: | ||
# Open the file "<code>..\Documents\My Games\Fallout4\Fallout4Custom.ini</code>". | |||
# Populate the <code>Fallout4Custom.ini</code> file with the following settings. | |||
Log output from [[Papyrus]] will be written to <code>..\Documents\My Games\Fallout4\Logs\Script\Papyrus.0.log</code> or <code>..\Documents\My Games\Fallout4\Logs\Script\User\</code> if you have configured a user log. | |||
==== ..\Documents\My Games\Fallout 4\Fallout4Custom.ini ==== | |||
<source lang="ini"> | |||
[Papyrus] | |||
bEnableLogging=1 | |||
bEnableTrace=1 | |||
bLoadDebugInformation=1 | |||
bEnableProfiling=1 | |||
sDefaultLogOverlay=Papyrus | |||
</source> | |||
[[Category:Game Configurations]] | |||
[[Category:Papyrus Configurations]] | |||