Differences

This shows you the differences between two versions of the page.

--- unity_build_information_detection [2021/12/25 00:38] – created archo
+++ unity_build_information_detection [2025/12/21 00:20] (current) – 139.177.229.80
@@ Line 1: / Line 1: @@
-====== Unity build information detection ======
+There is a special place in my heart for second-chance romance stories. Searching an archive of romance specifically for this trope yields amazing results. I download the most promising PDF titles and spend my evenings reading about couples finding their way back to each other. https://anarchiveofromancepdf.top/ An Archive Of Romance Romance Novel Pdf
-For determining what's used in shipped games (e.g. if you want to check that your extension DLL/code is used by the game) and to understand what information is exposed in your own builds.
-  * [Android] .xapk/.apk/.so can be traversed with [[https://www.7-zip.org/|7-Zip]]
-  * headers can be inspected with any hex editor or often even Notepad (most <500KB files only, Notepad may struggle to open bigger files)
-===== Unity version =====
-  * in ''.unity3d'' file header
-  * in resource file headers, for example:
-    * ''unity default resources''
-    * ''globalgamemanagers''
-    * ''level<number>''
-    * ''sharedassets<number>.assets''
-    * files with 32 characters long names using hexadecimal characters [0-9a-f]
-  * [Android, since 2017.4] ''lib/<arch>/libunity.so/.note.unity''
-  * [Windows] ''<executable>/.rsrc/version.txt''
-  * [Windows] ''UnityPlayer.dll'' - Properties / Details / File version
-===== Used assemblies ====
-(methods that work even with IL2CPP builds)
-  * [recent versions] ''ScriptingAssemblies.json''
-  * search for .dll in ''global-metadata.dat'' with a hex editor
-Use cases:
-  * can determine URP usage by looking for ''Unity.RenderPipelines.Universal.*.dll'' (e.g. ''Unity.RenderPipelines.Universal.Runtime.dll'')
-===== Various =====
-  * In non-IL2CPP builds, all code that made it into a build is also available to the end user and can be viewed with various tools (e.g. dnSpy for .dll files) relatively easily. Obfuscation can partially mitigate it, however the most effective obfuscation methods (runtime assembly generation/loading and other methods relying on JIT) are not compatible with IL2CPP so wouldn't be used by extension developers.
-  * ''global-metadata.dat'' appears to contain all the method/property/field names in UTF-8 (or at least those that were used and not stripped) from all the assemblies that were used by the build.