Introduction
You can grab the tool on the front page by clicking one of the two versions available. There is no major difference between NET 8 and 9; if unsure, pick NET 9. Every time the tool receives a change, it will automatically build itself and the link will update, so you can use it every time you wanna get the latest version of the tool.
When inside the tool, you can see at the top of the window title the version code. If you ever get asked what version you are running, this is the one you should send ! In this example, the version code is 1370f10ee670fecfc02dce3333061728194569be; sending the beginning (1370f10) is enough.
The tool is composed of two main windows: the console and the main app. The console is useful for seeing everything that is happening and if any error happens it will be shown here.
Note
It is not because an error is shown that the tool is broken ! The implementations vary, and they can happen. Before reporting a bug, check if what you intended to do works; if it does, then ignore it. If it doesn't and you checked all of the documentation for the correct setup and known issues, then file a report.
In the main window, the main areas you need to look at are Scene Hierarchy, Asset List, and Preview.
-
Scene Hierarchy : It will show all the loaded
GameObject, you can use the search bar at the top to quickly find one - Asset List : All the assets loaded
- Preview : The preview of the currently selected asset (if said asset is previewable)
Tip
A game is made of assets (textures, 3D models, etc.), which are the ones in the asset list, and a GameObject is a collection of assets (for example, a playable character is a GameObject with its texture, model, and everything else a separate asset in the asset list)
You cannot preview a GameObject, but you can for individual assets, and you can usually make a GameObject yourself by manually extracting each required asset
Depending on your needs, look at the correct tab for if you need an object or asset. This section won't cover more on using the tool. I heavily suggest that you look at AssetStudio tutorials directly, as this tool has been out there for many years, if you need more help using it.
Studio tends to use a lot of RAM (and disk space if you run out), the maximum should be like 4 to 8GB of data loaded into it, you can do more if you want, but you've been warned. While this wiki covers working on Hoyo games, a good part of all we're doing is also because they are so big that they cannot be loaded at once. If you ever try to work on another big game, most of what is explained here should also be done to prevent killing your RAM.
On a side note, the tool does NOT auto-update. If you encounter any issue, make sure you have the latest version by comparing your version with the latest commit hash seen here :
If it doesn't match, update your tool first by re-downloading it, and if it doesn't work there, then you can file a report !