Using Rust to parse Godot .tres files and walk the resource graph
The article details the implementation of .tres file parsing in Rust for the Asset Hoard tool, enabling better handling of Godot engine resource files. It explains the challenges of the .tres format's complexity and external resource dependencies, which can break assets when moved between projects. The solution involves a two-phase parser that resolves resource graphs and ensures all dependencies are preserved when transferring assets.
- ▪The .tres file format in Godot appears simple but contains complex references to external resources by path or UID.
- ▪Asset Hoard v0.1.13 introduces full .tres support, allowing proper previews and drag-and-drop transfer of resources with their dependencies.
- ▪The parser separates structural parsing from type-specific body parsing and handles differences between Godot 3 and Godot 4 formats.
Opening excerpt (first ~120 words) tap to expand
← All Posts May 9, 2026 Parsing Godot .tres files and walking the resource graph A .tres file looks innocent. Open one in a text editor and you get something close to INI: a header, a few sections, some key-value pairs. Tiny. Readable. Surely a couple of regexes away from being parseable. This impression survives roughly five minutes. Godot resource files are a custom format that references other resources by path, by UID, and sometimes both. A StandardMaterial3D.tres is a small text file pointing at textures that live somewhere else. Move just the .tres to a different project and the material is broken on the other end. The textures cannot be found. The material falls back to magenta. Your asset is, for any practical purpose, useless. This is a problem for an external asset manager.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at AssetHoard.
Discussion
0 commentsMore from AssetHoard
