TREE (File Format): Difference between revisions

Line 42:

The TREE format uses script objects to set up the hierarchy. There are five object types present, each representing a different node type in the hierarchy: a category, a scan, an inventory item description, an options slider, or an options menu. There are a few common parameters to all these object types:

* They all include [[~~EditorParameters~~]], which contains an instance name, an "active" flag, and a position/rotation/scale, even though none of them actually needs it.

* They all include [[EditorProperties]], which contains an instance name, an "active" flag, and a position/rotation/scale, even though none of them actually needs it.

* Every node has a name. In the data, this is represented with a resource ID for a [[STRG (Metroid Prime)|STRG file]] that the name of one of the strings in that file. The name is used to look up the actual string, which is then displayed ingame in the pause menu.

@@ Line 42: / Line 42: @@
 The TREE format uses script objects to set up the hierarchy. There are five object types present, each representing a different node type in the hierarchy: a category, a scan, an inventory item description, an options slider, or an options menu. There are a few common parameters to all these object types:
-* They all include [[EditorParameters]], which contains an instance name, an "active" flag, and a position/rotation/scale, even though none of them actually needs it.
+* They all include [[EditorProperties]], which contains an instance name, an "active" flag, and a position/rotation/scale, even though none of them actually needs it.
 * Every node has a name. In the data, this is represented with a resource ID for a [[STRG (Metroid Prime)|STRG file]] that the name of one of the strings in that file. The name is used to look up the actual string, which is then displayed ingame in the pause menu.