Editing Resource Container (RCO)

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 190: Line 190:


===Attributes===
===Attributes===
Attributes are located after the element definition (at entry relative offset 0x28), only exists for the elements that uses attributes, each '''entry_type''' uses different attributes, are explained in detail in other wiki pages
After the common area (at entry relative offset 0x28) appears the '''attributes''', the attributes are different for every '''entry_type''' and are explained in detail in other wiki pages, see the links in the table below
 
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
 
An special mention is needed to 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
{{RCO TOC entry types}}
{{RCO TOC entry types}}


Some of the attributes are a '''reference''' to load other entry
Some of the attributes are a '''reference''' to load other entry, are composed by two values, the first is the '''reference_type''' that indicates the "tree" of the entry that is going to be loaded, and the second is a '''pointer''' to a text string with the '''label''' of the entry that is going to be loaded. The reference_type '''event''' doesnt loads an entry from a "tree" though, it runs a code function from either a .sprx (by storing the text '''native:/''' as part of the text string inside the RCO) or from a [[VSMX]] script (by storing the text '''script:/''' as part of the text string inside the RCO)
{{RCO TOC reference types}}
{{RCO TOC reference types}}


Please note that all contributions to PS3 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS3 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)