> For the complete documentation index, see [llms.txt](https://core-keeper-modding.gitbook.io/modding-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://core-keeper-modding.gitbook.io/modding-wiki/creating-mods/inspecting-base-game-content/inspecting-assets-in-game.md).

# Inspecting Assets In-Game

## Example Cases

### Fixing an imported MinecartEntity prefab by looking at the real one in game

This example talks about [fixing an imported prefab ripped from the game](/modding-wiki/creating-mods/inspecting-base-game-content/importing-ripped-assets-to-your-editor.md) using info in Unity Explorer.

1. Install [Unity Explorer](/modding-wiki/creating-mods/modding-tools/unity-explorer.md) and relaunch the game
2. Open the "Object Explorer" window from the newly added top bar
   1\.

   ```
   <figure><img src="/files/8vVjEu95oCwftYRfMYfX" alt=""><figcaption></figcaption></figure>
   ```
3. Switch to "Object Search" mode and type `MinecartEntity` into the "Name contains:" search box, then press Search
   1\.

   ```
   <figure><img src="/files/URFswGF2Z5DqMPH2A9W4" alt=""><figcaption></figcaption></figure>
   ```
4. Find the entry `"MinecartEntity" (UnityEngine.GameObject)` and double click it&#x20;
   1\.

   ```
   <figure><img src="/files/P02G6tY7QoDQiPXyW4l6" alt=""><figcaption></figcaption></figure>
   ```
5. In the "Components" column you can see a list of script components on the prefab. The default sorting order should be exactly the same as the sorting order of the scripts in the Unity editor.
   1\.

   ```
   <figure><img src="/files/3LnCkEopffkmRng8RHft" alt=""><figcaption></figcaption></figure>
   ```
6. Use [NG Tools Missing Script Recovery](/modding-wiki/creating-mods/modding-tools/ng-tools-missing-script-recovery.md) to fix as many Perfect Matches as you can, then use the entries in the Components column to specify what the rest of the scripts are.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://core-keeper-modding.gitbook.io/modding-wiki/creating-mods/inspecting-base-game-content/inspecting-assets-in-game.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.