Client Script unload leaves references - causes client to spam to scripting.log
- Operating System: Windows 10
After disconnecting from a server, the client starts logging the message below to Scripting.log which makes it hard to find the output of your own functions. This may also cause problems with hdd space or ssd live time, because it uses up quite some space and write actions after just 10 minutes.
[2017-01-07 00:05:28]: There is still a reference to a script function which package has been stopped
- What is the expected behavior?
The client should remove all references to scripts that has been unloaded. Alternatively it should only output this information once and state the package the reference originated from.
- Steps to reproduce:
- connect any server (tested with freeroam with a syntax failed own script)
- check logs/Scripting.log