If the user add the STTS script to a mission and configures it (sets up the directory and port), but somehow the executable itself is not available (was not installed, has been moved, is not accessible by the current user, etc.), then an error pops up and DCS is frozen.
This little change ensures that, the first time STTS is used, it will check if the executable file is actually there.
Then, this information is cached for better performance.
If the user add the STTS script to a mission and configures it (sets up the directory and port), but somehow the executable itself is not available (was not installed, has been moved, is not accessible by the current user, etc.), then an error pops up and DCS is frozen.
This little change ensures that, the first time STTS is used, it will check if the executable file is actually there. Then, this information is cached for better performance.