Game Toolkit for Unity
Having problems building your project or running your built project?
See if your issue is listed here or in the Unity troubleshooting pages for your build target. If you can’t find a solution, please contact me or post it in the community forum.
Using the IL2CPP scripting backend will result in Unity’s compiler stripping/removing code it considers unused. While this isn’t a problem in most cases, it can result in errors due to missing code or DLL files in your built game – especially when reflection is used to access code, which is the case for most Makinom plugins.
You can prevent this by adding link.xml files to your project – they can be placed anywhere in your Assets folder (including any subfolder) and you can add multiple to your project. The link.xml file is a simple text file that can define which code should or shouldn’t be stripped.
For example, to prevent anything in Makinom’s DLL files from being stripped, use a link.xml file with the following content:
This’ll prevent Makinom and the Unity UI module from being stripped. Replace Makinom2.UnityUI with the name of the DLL file of the UI module you’re using if you use a different UI module.
Another example, to prevent a plugin from being stripped:
You might notice the pattern – put in the name of the DLL file (without .dll being added).
You can find more information on this topic and the link.xml syntax in the Unity manual.
If you’re building your project for iOS, you may run into one of the following problems.
You can find information on other issues and more detailed instructions on the Unity troubleshooting page.
© 2015 Gaming is Love e.U.
Disclosure: This site may contain affiliate links, which means I may receive a commission if you click a link and purchase something that I have recommended. While clicking these links won’t cost you any money, they will help me fund my development projects while recommending great assets!