TREE (File Format): Difference between revisions
m
→Header
>Aruki m (→Script Objects) |
>Aruki m (→Header) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 24: | Line 24: | ||
| 0x4 | | 0x4 | ||
| u32 | | u32 | ||
| '''Root Node | | '''Root Node Instance ID''' | ||
| | | Should point to a <code>SCND</code> object. The original file points to one named RootTreeNode. | ||
|- | |- | ||
| 0x8 | | 0x8 | ||
| Line 47: | Line 47: | ||
=== SCND (Category) === | === SCND (Category) === | ||
The <code>SCND</code> object represents a category. Categories don't have very many properties; they do most of their work through the connections system instead. Category nodes are able to use their connections to mark other nodes as children. They do this by sending the message ''Attach'' (<code>ATCH</code>) to the target child node on state ''Connect'' (<code>CONN</code>). The progress bars that appear on the right side of the | The <code>SCND</code> object represents a category. Categories don't have very many properties; they do most of their work through the connections system instead. Category nodes are able to use their connections to mark other nodes as children. They do this by sending the message ''Attach'' (<code>ATCH</code>) to the target child node on state ''Connect'' (<code>CONN</code>). The progress bars that appear on the right side of the pause screen are set up automatically based on how many children the category has and how many of them are visible. | ||
{| class="wikitable" | {| class="wikitable" | ||