Template:RCO TOC entry types: Difference between revisions

Revision as of 08:15, 22 September 2021

RCO TOC entry types
[edit]
		ID (Second byte)
		0x00	0x01	0x02	0x03	0x04	0x05	0x06	0x07	0x08	0x09	0x0A	0x0B	0x0C	0x0D	0x0E	0x0F	0x10	0x11	0x12	0x13	0x14	0x15	0x16	0x17	0x18	0x19	0x1A	0x1B	0x1C	0x1D	0x1E	0x1F
TYPE (First byte)	0x01	unk	MainTree
	0x02	ScriptTree
	0x03	TextTree	Text
	0x04	ImageTree	Image
	0x05	ModelTree	Model
	0x06	SoundTree	Sound
	0x07	FontTree	Font
	0x08	ObjectTree	Page	Plane	Button	XMenu	XMList	XList	Progress	Scroll	MList	MItem	unk	XItem	Text	ModelObject	Spin	Action	ItemSpin	Group	LList	LItem	Edit	Clock	IList	IItem	Icon	UButton	unk	CheckboxGroup	CheckboxItem	Meter	EditBox
	0x09	AnimTree	Anim	MoveTo	Recolour	Rotate	Resize	Fade	Delay	FireEvent	Lock	Unlock	SlideOut
		Supported by and																											Supported by only

The entry_types with the suffix Tree (as example MainTree) are special and doesnt uses attributes, MainTree is always located as the first entry, doesn't have a parent, and doesn't have any previous or next "sibling", the maximun number posible of childrens for MainTree is 8 (containing all the other "trees"). The other "trees" (as example imageTree or soundTree) are siblings and are the childrens of "MainTree", Every one of those "trees" contains a variable number of entry_types that are its childrens
The attributes of the RCOXML Objects (entry_types starting with 0x08) and RCOXML Animations (entry_types starting with 0x09) can be grouped in standard attributes (used by most entryes of this type) and specific attributes (different for every entry_type). The standard attributes are always located before the specific attributes
First two bytes are swapped based on architecture (PSP in little endian, PS3 in big endian). The table shows the values in big endian

@@ Line 34: / Line 34: @@
 ! colspan="2" style="background:#ffffff; border-left:1px solid #ffffff; border-bottom:1px solid #ffffff;" | !! colspan="27" | Supported by {{icon content psp|50px}} and {{icon content ps3|50px}} !! colspan="5" | Supported by {{icon content ps3|50px}} only
 |}
-*The entry_types wich name contains the word '''tree''' (as example MainTree) are special and doesnt uses attributes, MainTree is always located as the first entry, doesn't have a parent, and doesn't have any previous or next "sibling", the maximun number posible of childrens for MainTree is 8 (containing all the other "trees")<!--actually it should be 9 trees max because the toc_unknown area at absolute offset 0x28 in the header is telling it exists another unknown tree-->. The other "trees" (as example imageTree or soundTree) are siblings and are the childrens of "MainTree", Every one of those "trees" contains a variable number of '''entry_types''' that are its childrens
+*The entry_types with the suffix '''Tree''' (as example MainTree) are special and doesnt uses attributes, MainTree is always located as the first entry, doesn't have a parent, and doesn't have any previous or next "sibling", the maximun number posible of childrens for MainTree is 8 (containing all the other "trees")<!--actually it should be 9 trees max because the toc_unknown area at absolute offset 0x28 in the header is telling it exists another unknown tree-->. The other "trees" (as example imageTree or soundTree) are siblings and are the childrens of "MainTree", Every one of those "trees" contains a variable number of '''entry_types''' that are its childrens
-*The [[RCOXML Objects]] (entry_types starting with 0x08) and [[RCOXML Animations]] (entry_types starting with 0x09) where the attributes can be grouped in standard attributes (used by most entryes of this type) and specific attributes (different for every entry_type). The standard attributes are always located before the specific attributes
+*The attributes of the [[RCOXML Objects]] (entry_types starting with 0x08) and [[RCOXML Animations]] (entry_types starting with 0x09) can be grouped in standard attributes (used by most entryes of this type) and specific attributes (different for every entry_type). The standard attributes are always located before the specific attributes
 *First two bytes are swapped based on architecture (PSP in little endian, PS3 in big endian). The table shows the values in big endian
 <noinclude>[[Category:Templates]]</noinclude>

Template:RCO TOC entry types: Difference between revisions

Revision as of 08:15, 22 September 2021

Navigation menu

Search