Third-Party Credits and Licenses
After reading this page, you can see which external packages MLC depends on and where the credit for each one lives.
What this page covers
MLC does not bundle or redistribute any of the packages below. You install each one into the project yourself, and MLC connects to it by assembly reference or by public component name only.
The copyright notice and the license text of each package are therefore authoritative in that package's own distribution. This page states only which package is connected under which conditions.
The MLC runtime component and the core authoring UI live in assemblies that reference none of the packages below. Each integration assembly compiles only when its package is present in the project; when it is absent, MLC treats that backend as unavailable.
VRChat Avatars SDK
| Item | Detail |
|---|---|
| Package | com.vrchat.avatars |
| Required | Required — you need it to make a VRChat build |
| Connection | A dedicated VRC integration editor assembly. It references the VRCSDKBase, VRCSDKBase-Editor, and VRCSDK3A assemblies |
| Where the credit lives | The terms and notices included in the VRChat SDK package distribution |
Without this package the MLC window shows the following warning, and only configuration validation can continue.
VRCSDK Avatars was not found. The core compile plan can still be validated.
NDMF
| Item | Detail |
|---|---|
| Package | nadena.dev.ndmf |
| Required | Required — 1.0.0 or later |
| Connection | An NDMF integration editor assembly. It compiles only when NDMF and VRChat Avatars SDK 3.0.0 or later are both present |
| What it does | Provides the disposable avatar clone and the generated-asset store. MLC builds menus, parameters, clips, and FX on that clone and nowhere else |
| Where the credit lives | The license text included in the NDMF package distribution |
MLC registers itself in the NDMF pipeline as a phase that runs before Modular Avatar.
Modular Avatar
| Item | Detail |
|---|---|
| Required | Optional — one of the three attachment backends |
| Connection | Found by component name only, with no assembly reference |
| What it does | Creates a temporary child host on the build clone and attaches only the menu installer, parameters, and animator merge components. If it fails, it removes the unfinished host itself |
| Where the credit lives | The license text included in the Modular Avatar package distribution |
MLC does not install Modular Avatar for you.
VRCFury
| Item | Detail |
|---|---|
| Package | com.vrcfury.vrcfury |
| Required | Optional — one of the three attachment backends |
| Supported version | 1.1426.0 or later. The public API from that version on is the target |
| Connection | A dedicated VRCFury integration editor assembly. It references the VRCFury public API assembly |
| Where the credit lives | The license text included in the VRCFury package distribution |
If Attachment is set to VRCFury explicitly and the integration cannot be used, MLC does not fall back to another backend; it reports this instead.
The VRCFury provider is not installed. Install VRCFury or choose another build backend.
MLC does not install VRCFury for you.
MingToon
| Item | Detail |
|---|---|
| Required | Required — the target avatar must have MingToon materials |
| Relationship | MLC is a separately sold add-on. Installing it does not replace the MingToon shader package |
| Rights | Governed by the MingToon product license. The open-source credits MingToon itself carries are in the MingToon documentation |
The MLC editor assemblies do not reference MingToon directly, so MLC compiles even in a project where MingToon is not installed. In that state, though, there are no materials to attach to.
Contact
If you spot a third-party credit that is missing, please tell us at studioraming@gmail.com.