Merge pull request #86 from gl1tch638/patch-1

Clarify new unhollower assembly destination for MelonLoader versions over 0.6.0

docs/modders/quickstart.md

@@ -196,7 +196,8 @@ As seen in the previous `OnGUI` example, calling game/Unity methods is as simple
 However, compared to Unity, you have to reference all the game and Unity assemblies manually.
 
 For games using the [Mono runtime](https://www.mono-project.com), all the game/Unity assemblies can be found in `[Game Directory]\[Game Name]_data\Managed\`.<br>
-For games using the IL2CPP runtime, all the game/Unity assemblies can be found in `[Game Directory]\MelonLoader\Managed\` (make sure you have ran the game with MelonLoader at least once!).
+For games using the IL2CPP runtime, all the game/Unity assemblies can be found in `[Game Directory]\MelonLoader\Managed\` (make sure you have ran the game with MelonLoader at least once!).<br>
+For games using IL2Cpp and MelonLoader versions 0.6.0 and over, assemblies are instead generated in `[Game Directory]\MelonLoader\Il2CppAssemblies\`, with 'IL2CPP' affixed at the beginning of generated assemblies (still required to run the game at least once!).
 
 Since IL2CPP converts all game assemblies to C++, MelonLoader is using [Il2CppInterop](https://github.com/BepInEx/Il2CppInterop), an IL2CPP proxy assembly generator which allows us to use IL2CPP assemblies from C#.
 Before we can use any assemblies generated by the Unhollower, it's required to reference the following assemblies first: