Debug trace question

[kitcat81]

Hey, can someone help me a bit, please?

I`m learning to write scripts and it`s going well apart from some certain things. To learn Papyrus I`m looking through base game scripts . And I just can`t understand what is this "debug trace " function and what it is used for. Wiki says that it " outputs a string to the Papyrus log on disk, and the Papyrus overlay." But it never explains what is this papyrus log and papyrus overlay and what is the purpose of outputing some strings to it. It also mentions something like that debug functions won`t work in the final release...This is all confusing and makes no sence.

Edited December 3, 2016 by kitcat81

[Reneer]

The debug functions are just that: functions to help script writers determine the execution and flow of a script or to output other useful information to disk to be viewed after the game session is over (or use the Papyrus overlay).

 

The Papyrus log needs to be enabled before the log files are created. You can look up what INI files need changing via Google.

[kitcat81]

The debug functions are just that: functions to help script writers determine the execution and flow of a script or to output other useful information to disk to be viewed after the game session is over (or use the Papyrus overlay).

 

The Papyrus log needs to be enabled before the log files are created. You can look up what INI files need changing via Google.

 

Thanks a lot ! It was almost like a mystery for me. I was not sure if this "debug.trace" is necessary for some scripts to work. I used debug.notification in my scripts to see if they work as expected. As I understood it`s something similar, but sends messages to the log instead of player so it can be checked later.

[Lisselli]

trace is good for really long checks that will otherwise be truncated or made in really tiny on-screen text by debug.notificaiton.

 

Notification for short checks

trace for longer more technical checks

Edited December 4, 2016 by Lisselli