Page 1 of 1

most verbose debug log

Posted: Thu Mar 07, 2019 2:09 pm
by Bene Hrethgir
I'm sure this is a stupid question but I am working on updating an older mod and the snippet of debug information that the debug handler shows when an exception occurs is hardly enough, my question is can I get a more full print out of the problem so that one can attempt to remedy the situation?

Re: most verbose debug log

Posted: Tue Aug 27, 2019 4:34 pm
by Kemsha
There isn't much more information unless you buid it yourself

Use the print command and see the result on the "te4_log.txt" file

Or use the LUA console to check the environment and test some simple instructions