Other user's assetsAll the assets in this file belong to the author, or are from free-to-use modder's resources
Upload permissionYou are not allowed to upload this file to other sites under any circumstances
Modification permissionYou must get permission from me before you are allowed to modify my files to improve it
Conversion permissionYou can convert this file to work with other games as long as you credit me as the creator of the file
Asset use permissionYou must get permission from me before you are allowed to use any of the assets in this file
Asset use permission in mods/files that are being soldYou are not allowed to use assets from this file in any mods/files that are being sold, for money, on Steam Workshop or other platforms
Asset use permission in mods/files that earn donation pointsYou are not allowed to earn Donation Points for your mods if they use my assets
Author notes
This author has not provided any additional notes regarding file permissions
File credits
This author has not credited anyone else in this file
Brief This is a simple PowerShell script that monitors the papyrus log file, and alerts the user if there are stack dumps present.
Overview When running lots of mods -- especially script intensive mods -- there is a risk of the scripting engine becoming overloaded. If the number of active scripts exceeds a certain threshold, they will be dumped, which means that they are written out the logfile. Some scripts may get suspended as the Papyrus engine tries to recover.
This can be a sign that something has gone very wrong. So I wrote this monitor script to alert me.
Results During normal gameplay, the output of the monitor will look something like this. Note that having some errors and warnings is quite normal if you have mods installed.
--------------------------------------------------------------------------- When a stack dump has occurred, the output of the monitor will look like this. It will be accompanied by a beeping sound every 4 seconds and the PowerShell window changing color.