Third-party native binaries

Aurie (AurieCore.dll, AuriePatcher.exe) and YYToolkit (YYToolkit.dll) are prebuilt in lib/Aurie and lib/YYToolkit, so packaging needs nothing outside the repository. Each folder's README names the upstream commit, the SHA-256 of the binaries and the patch applied: Aurie's (lib/Aurie/stoneforge.patch) loads modules from <game>\aurie, and YYToolkit's (lib/YYToolkit/stoneforge.patch) stops its GML error hook from naming scripts (which faults on this GameMaker version and crashed the game on every GML error) and opens its console window only on request (see Crash windows and reports). Both are AGPL-3.0.

The MSL compatibility helper's binaries are in lib/MSL: ModShardLauncher 0.13.2.0's ModShardLauncher.dll, and the older UndertaleModLib.dll and UndertaleModTool.dll it was built with, all GPL-3.0. Its README pins their checksums and upstream revision. They run only inside the separate StoneForge.MslHost process (also GPL-3.0), never in the loader, and StoneForge's own newer UndertaleModLib stays apart from them.

MSL Enhanced (by Tbonex28b, GPL-3.0 per its mod page) is in lib/MSLE: the supplied build's ModShardLauncher.dll, UndertaleModLib.dll and UndertaleModTool.dll, pinned by SHA-256 (its file version is still 0.13.2.0), with the dependencies it came with (Magick.NET and ImageMagick, SharpZipLib, XamlAnimatedGif, Microsoft.Win32.SystemEvents). No source for the Enhanced fork was supplied; these are its binaries as given. Releases install it in dotnet/msle, and it runs in the same helper process as regular MSL.

Releases include the licences, the patches and those notes under LICENSES\.

To rebuild them from source (needs git and Visual Studio's C++ tools; clones into build\.thirdparty):

powershell -ExecutionPolicy Bypass -File build\BuildThirdParty.ps1

It prints the new checksums; update the READMEs with them. To move to a newer upstream version, change the commit in the script and check the patch still applies.