TSCN

Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.

Godot Scene Preview.

At a glance

How much Poka reads

B4 Summary. The container and metadata are read and summarised (counts, properties, structure), but the main content is not rendered.

Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-26: read parsers/poka-godot-tscn/src/main.rs (308 lines) and plugin.json. No unit tests or tests/samples.rs, and the corpus has no .tscn, .tres and .gd sample. Covers .tscn, .tres and .gd. The card reads the [gd_scene] or [gd_resource] header (format version, load steps, UID) and every section header: counts of nodes, instanced sub-scenes, external and sub-resources and node types, and lists the first 8 external resources and the first 8 nodes with type and parent. Judgement: B4: the scene is summarised but not shown as a tree or with properties.

What Poka does not read

• Node and resource properties (the key = value lines under each section) are not read
• The node hierarchy is not drawn as a tree; only the first 8 nodes are listed
• GDScript files (.gd) are routed here but refused, because they have no [gd_scene] header (the module comment says they are treated as text)
• Binary scenes and resources (.scn, .res) are not read
• Files over 8 MiB are cut (flagged)

Libraries

Libraries Poka uses or has assessed for this format, with the status, licence and language the registry records.

• godot_parser (candidate; MIT; Python; https://github.com/stevearc/godot_parser) — Parses Godot .tscn and .tres; author notes it may not cover every feature.
• godot-tscn-parser (candidate; MIT; Go; https://github.com/atomicptr/godot-tscn-parser) — Parses TSCN with node-path lookup; built on participle. Only non-default values appear in TSCN files.

Sources

• parsers/poka-godot-tscn/src/main.rs
• parsers/poka-godot-tscn/plugin.json