> For the complete documentation index, see [llms.txt](https://stoneforgeteam.gitbook.io/stoneforgeteam-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stoneforgeteam.gitbook.io/stoneforgeteam-docs/development/third-party-binaries.md). # Third-party native binaries {% hint style="info" %} Paths and commands on this page are relative to a checkout of the [StoneForge repository](https://github.com/StoneForgeTeam/StoneForge). {% endhint %} 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 `\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](/stoneforgeteam-docs/development/crash-reports.md)). 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 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://stoneforgeteam.gitbook.io/stoneforgeteam-docs/development/third-party-binaries.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.