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/02/01 22:41] 139.135.81.163unity_build_information_detection [2026/03/26 08:58] (current) – old revision restored (2026/03/19 12:35) klea
Line 1: Line 1:
-The supernatural elements in the novel add layer of chilling suspense that defines the Gothic genreSearching for a Wuthering Heights PDF often leads readers to discover the ghostly aspects of the taleIs Catherine's ghost realor is it a figment of a tortured mind? The ambiguity is part of the book's brillianceWith an electronic version, you can read late into the night, illuminated by the glow of your devicewhich adds to the spooky atmosphereIt is the perfect way to experience the haunting presence that permeates the narrative from beginning to end.+====== Inspecting Information from Built Unity Players ====== 
 + 
 +It can be useful to inspect information from built Unity players. This can be helpful to check whether 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 a 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)) buildsall code that made it into a 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.1769985699.txt.gz · Last modified: 2026/02/01 22:41 by 139.135.81.163

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki