Uninomicon

Documenting the dark corners of the Unity Engine.

User Tools

Site Tools


unity_build_information_detection

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
unity_build_information_detection [2026/01/27 08:19] 159.65.245.255unity_build_information_detection [2026/03/26 08:58] (current) – old revision restored (2026/03/19 12:35) klea
Line 1: Line 1:
-There is a unique joy in following the lives of the March sisters as they navigate the challenges of poverty and the pressure to conformTheir story is a testament to the power of individuality and the strength of sisterhoodIf you are looking to read this book for the first time or the fiftieth, a digital copy is incredibly practicalSearching for a Little Women PDF enables you to have the book on your smartphone or tabletThis means you can steal a few pages of this heartwarming classic during your lunch break or while travelingkeeping the spirit of the March family with you.+====== Inspecting Information from Built Unity Players ====== 
 + 
 +It can be useful to inspect information from built Unity playersThis can be helpful to check whether a certain DLL is used by the game, or verify that the player built properly. 
 + 
 +===== High Level ===== 
 + 
 +  * [Android] .xapk/.apk/.so can be traversed with [[https://www.7-zip.org/|7-Zip]] 
 +  * Unity asset file headers can be inspected with any hex editor((Even Notepad works, although only for files <500KB. Notepad may struggle to open bigger files.)) 
 + 
 +===== Unity Version ===== 
 + 
 +Find this information in: 
 +  * ''.unity3d'' file header 
 +  * resource file headersfor 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 ==== 
 +These methods work even with IL2CPP builds. 
 + 
 +  * ''ScriptingAssemblies.json'' 
 +  * Search for ''.dll'' in ''global-metadata.dat'' with hex editor. 
 + 
 +Use cases: 
 + 
 +  * We can determine URP usage by looking for ''Unity.RenderPipelines.Universal.*.dll''((e.g. ''Unity.RenderPipelines.Universal.Runtime.dll'')) 
 + 
 +===== Notes ===== 
 + 
 +  * In non-IL2CPP((ie. Mono)) builds, all code that made it into build is also available to the end user and can be viewed with tools ((dnSpy or ILSpy for .dll files)) relatively easily. Obfuscation can mitigate this, however the most effective obfuscation methods((runtime assembly generation/loading and other methods relying on JIT)) are not compatible with IL2CPP so can't be used by 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.
unity_build_information_detection.1769501946.txt.gz · Last modified: 2026/01/27 08:19 by 159.65.245.255

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki