Some manual edits

Remove duplicated reference section in main readme that would be hard to maintain
A few edits based on review.

Author: SkowronskiAndrew

UnityDataTool/Commands/analyze.md

@@ -24,7 +24,7 @@ Analyze all files in a directory:
 UnityDataTool analyze /path/to/asset/bundles
 ```
 
-Analyze only `.bundle` files and save to a custom database:
+Analyze only `.bundle` files and specify a custom database name:
 ```bash
 UnityDataTool analyze /path/to/asset/bundles -o my_database.db -p "*.bundle"
 ```
@@ -34,6 +34,8 @@ Fast analysis (skip reference tracking):
 UnityDataTool analyze /path/to/bundles -s
 ```
 
+See also [Analyze Examples](../../Documentation/analyze-examples.md).
+
 ---
 
 ## What Can Be Analyzed
@@ -43,10 +45,12 @@ The analyze command works with the following types of directories:
 | Input Type | Description |
 |------------|-------------|
 | **AssetBundle build output** | The output path of an AssetBundle build |
-| **Addressables folder** | `StreamingAssets/aa` folder from a Player build |
+| **Addressables folder** | `StreamingAssets/aa` folder from a Player build, including BuildLayout files |
 | **Entities content** | `StreamingAssets/ContentArchives` folder for [Entities](https://docs.unity3d.com/Packages/[email protected]/manual/content-management-intro.html) projects |
 | **Player Data folder** | The `Data` folder of a Unity Player build |
 | **Compressed Player builds** | The `data.unity3d` file will be analyzed like AssetBundles |
+| **BuildReport files** | The build report is typically found at a path like `Library/LastBuild.buildreport`and is a binary serialized file |
+| **AssetDatabase Artifacts** | The tool will work to some extent with serialized files created in the AssetDatabase artifact storage, inside the Library folder |
 
 > **Note**: Some platforms require extracting content from platform-specific containers first (e.g., `.apk` files on Android).
 
@@ -56,9 +60,7 @@ The analyze command works with the following types of directories:
 
 The analysis creates a SQLite database that can be explored using tools like [DB Browser for SQLite](https://sqlitebrowser.org/) or the command line `sqlite3` tool.
 
-**Refer to the [Analyzer documentation](../../Analyzer/README.md) for complete database schema reference and usage examples.**
-
-See also: [Analyze Examples](../../Documentation/analyze-examples.md)
+**Refer to the [Analyzer documentation](../../Analyzer/README.md) for the database schema reference and information about extending this command.**
 
 ---
 

UnityDataTool/Commands/archive.md

@@ -66,8 +66,8 @@ contents/BuildPlayer-Scene2
 
 | Command | Output | Use Case |
 |---------|--------|----------|
-| `archive extract` | Binary SerializedFiles | When you need the raw files |
-| `dump` | Human-readable text | When you need to inspect content |
+| `archive extract` | Binary SerializedFiles, .resS anything else inside the archive content | When you need all the raw files inside an archive |
+| `dump` | text | When you want to inspect object content |
 
 The `dump` command can directly process archives without extracting first.
 

UnityDataTool/Commands/dump.md

@@ -103,5 +103,9 @@ PPtrs (Property Pointers) are Unity's mechanism for referencing objects:
 | `m_FileID` | Index into External References list (0 = same file) |
 | `m_PathID` | Object's Local File Identifier (LFID) in that file |
 
-Use external references to resolve cross-file references.
+A null reference will have value m_FileID = 0, m_PathID = 0
+
+The external reference table is used to resolve cross-file references. It always starts at index 1.  m_FileID 0 is used for references within the current file.
+
+
 

UnityDataTool/README.md

@@ -4,12 +4,12 @@ A command-line tool for analyzing and inspecting Unity build output—AssetBundl
 
 ## Commands
 
-| Command | Description | Documentation |
-|---------|-------------|---------------|
-| [`analyze`](#analyze) | Extract data from Unity files into a SQLite database | [Full docs →](Commands/analyze.md) |
-| [`dump`](#dump) | Convert SerializedFiles to human-readable text | [Full docs →](Commands/dump.md) |
-| [`archive`](#archive) | List or extract contents of Unity Archives | [Full docs →](Commands/archive.md) |
-| [`find-refs`](#find-refs) | Trace reference chains to objects *(experimental)* | [Full docs →](Commands/find-refs.md) |
+| Command | Description |
+|---------|-------------|
+| [`analyze`](Commands/analyze.md) | Extract data from Unity files into a SQLite database |
+| [`dump`](Commands/dump.md) | Convert SerializedFiles to human-readable text |
+| [`archive`](Commands/archive.md) | List or extract contents of Unity Archives |
+| [`find-refs`](Commands/find-refs.md) | Trace reference chains to objects *(experimental)* |
 
 ---
 
@@ -36,112 +36,6 @@ Use `--help` with any command for details: `UnityDataTool analyze --help`
 
 Use `--version` to print the tool version.
 
----
-
-## analyze
-
-Extract information from Unity Archives and SerializedFiles into a SQLite database.
-
-```bash
-UnityDataTool analyze <path> [options]
-```
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `-o, --output-file` | Output database filename | `database.db` |
-| `-p, --search-pattern` | File filter pattern (`*.bundle`) | `*` |
-| `-s, --skip-references` | Skip CRC/reference extraction (faster) | — |
-| `-v, --verbose` | Show detailed progress | — |
-| `--no-recurse` | Don't recurse into subdirectories | — |
-
-**Example:**
-```bash
-UnityDataTool analyze /path/to/bundles -o my_database.db -p "*.bundle"
-```
-
-📖 [Full documentation](Commands/analyze.md) — Troubleshooting, database schema, example inputs
-
----
-
-## dump
-
-Convert SerializedFiles to human-readable text format.
-
-```bash
-UnityDataTool dump <path> [options]
-```
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `-o, --output-path` | Output folder | Current folder |
-| `-f, --output-format` | Output format | `text` |
-| `-s, --skip-large-arrays` | Skip large array contents | — |
-| `-i, --objectid` | Only dump this object ID | All objects |
-
-**Example:**
-```bash
-UnityDataTool dump /path/to/file -o /output/path
-```
-
-📖 [Full documentation](Commands/dump.md) — Output format details, archive support
-
----
-
-## archive
-
-Work with Unity Archives (AssetBundles, `.data` files).
-
-### list
-
-```bash
-UnityDataTool archive list <archive-path>
-```
-
-### extract
-
-```bash
-UnityDataTool archive extract <archive-path> [options]
-```
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `-o, --output-path` | Output directory | `archive` |
-
-**Example:**
-```bash
-UnityDataTool archive extract scenes.bundle -o contents/
-```
-
-📖 [Full documentation](Commands/archive.md) — Sub-command details, comparison with dump
-
----
-
-## find-refs
-
-> ⚠️ Experimental
-
-Find reference chains leading to specific objects. Requires a database from `analyze` (without `--skip-references`).
-
-```bash
-UnityDataTool find-refs <database> [options]
-```
-
-| Option | Description |
-|--------|-------------|
-| `-i, --object-id` | Object ID to trace |
-| `-n, --object-name` | Object name to trace |
-| `-t, --object-type` | Type filter (with `-n`) |
-| `-o, --output-file` | Output filename |
-| `-a, --find-all` | Find all chains (slower) |
-
-**Example:**
-```bash
-UnityDataTool find-refs my_database.db -n "MyTexture" -t "Texture2D" -o refs.txt
-```
-
-📖 [Full documentation](Commands/find-refs.md) — Use cases, output format
-
----
 
 ## Installation