- A project without build scenes plays one of its scenes (a menu or main scene when there is one, logged; Unity's editor would play the last scene open, which projects don't keep). Build scenes moved since they were listed are found by their GUID, as Unity does.
- Json.NET (13.0.3, MIT) ships beside the runtime; projects listing com.unity.nuget.newtonsoft-json compile against it from every script assembly, as Unity auto-references the package's DLL.
- Binary compatibility: Object.Destroy(Object) and DestroyImmediate(Object, bool) are separate overloads, as in Unity, rather than optional parameters: precompiled plugins (DOTween here) call each signature by name. Other optional-parameter APIs may have the same problem; a signature-level coverage check against Unity's modules would find them.
- Unity 2018 projects reference Sprites-Default under the built-in shaders' GUID; it resolves there too.
- Corpus: 7 of 14 compile, 6 load a scene (4 before). UnityMatch3 plays with its DOTween DLLs and no warnings or exceptions. The tower defense opens its main scene, but 4 of the 11 assets it uses aren't in its repository. GoCube (Unity 5.3) keeps its settings and scenes in Unity's binary format, which isn't read. UnityChess now needs UI Toolkit and Addressables.
Phase 6 · Slice 9 ·