Editing BLO file

== Types of BLO ==
The <code>BLO</code> filetype is used by several Nintendo games such as ''Pikmin'', ''Pikmin 2'', ''Super Mario Sunshine'', and ''The Legend of Zelda: The Wind Waker'' to control screen data, such as which sprites appear and where. There are 3 main types of a blo file, <code>scrnblo1</code> (which ''Sunshine'' and ''Wind Waker'' use), <code>scrnblo2</code> (which ''Pikmin 2'' uses), and the format ''Pikmin'' uses, sometimes called <code>scrnblo0</code>. There are several differences between them and they are not interchangeable. This page will focus on <code>scrnblo2</code>, the flavour ''Pikmin 2'' uses.

== TEX1 ==
The first main segment of a <code>scrnblo2</code> file, this is where the game loads BTI textures in <code>/new_screen/eng/*screen szs*/timg</code>. You can change the filenames of the textures to be loaded, and possibly add or remove entries. The number of textures to load is defined in a BE 32 bit integer 0x08 away from the sections magic <code>TEX1</code>.

== FNT1 ==
This section is dedicated to loading fonts, hence the name <code>FNT1</code>. In ''Pikmin 2'', this only ever loads <code>piki2_font00.bfn</code>.

== MAT1 ==
This section creates screen "objects" with internal names that the game uses to control them. Its by far the biggest segment of the <code>BLO</code>. The important part is where the names of the materials are listed. They always follow the naming convention of <code>mat_name_v</code>. The main makeup of this section is padding.

== PAN2 ==
This section acts like a group, it holds many <code>PIC2</code> and <code>TBX2</code> segments together so you can easily move a whole object as one piece. There is always a <code>PAN2</code> section called <code>ROOT</code> in every <code>scrnblo2</code>, and sometimes more.

* <code>0x12</code>: The name of the material.
* <code>0x20</code>: 2 floats representing x and y size coordinates. Does nothing in PAN2.
* <code>0x28</code>: 2 floats representing x and y scale. Often 1.
* <code>0x3C</code>: 2 floats representing x and y coordinates, relative to parent PAN2.

A PAN2 is like an opening curly bracket, everything after it will be a child of it, until you reach and "END1" command, which acts like the closing bracket. You can have PAN2 objects nested in other PAN2s as well.

== PIC2 ==
This is very similar to the last segment, but for an individual sprite object. They are notably longer than <code>PAN2</code> segments. You probably shouldn't change their parameters if you have the option to edit their whole <code>PAN2</code> segment instead. Here's some info about them:

* <code>0x07</code>: string saying <code>pan2</code>
* <code>0x19</code>: Name of material, it likes to have <code>RE</code> before it for some reason, but that's not part of the name.
* <code>0x28</code>: x and y pixel dimensions.
* <code>0x30</code>: x and y scale.
* <code>0x45</code>: x and y coordinates relative to parent <code>PAN2</code> entry.

After that is a whole row for the RGBA gradient colors for each corner of the sprite.

== TBX2 ==
These are a lot like <code>PIC2</code>, and are also part of a <code>PAN2</code>. The difference is they write text using the loaded font.
* <code>0x07</code>: string for <code>pan2</code>, could be what connects the single <code>tbx2</code> to a <code>pan2</code>.
* <code>0x1A</code>: internal name of material being used.
* <code>0x21</code>: text ID used. The developers like to put placeholder text IDs here when the screen could show multiple messages, so it only really works for fully static text.
* <code>0x27</code>: x and y dimensions of containing box
* <code>0x30</code>: x and y scale.
* <code>0x43</code>: x and y offset to parent.

After that is some random data, followed by the text itself, in an early version where things like color and size change and text box terminators are called by their internal names. Can show early scripts of the games text in some areas.
@@ Line 42: / Line 42: @@
 After that is some random data, followed by the text itself, in an early version where things like color and size change and text box terminators are called by their internal names. Can show early scripts of the games text in some areas.
-== Colors ==
-{{todo|Cleanup. Also, what JSON is this referring to?}}
-There are three BLO colors for a single object, TevColors, MatColors and Color1 and Color2
-TevColors are shown like this in the json:
-  "tevcolors": [
-    "00000000008c0000",
-    "00000000008c00ff",
-    "0000000000000000",
-    "0000000000000000"
-Colors here are Hex values, and each RGBA value has a "00" before each value, so "00ff00ff00ff00ff" is white. this colors the entire bti.
-MatColors are shown like this:
-  "matcolors": [
-    [
-,
-,
-,
-    ],
-    [
-,
-,
-,
-    ]
-I rarely see vanilla blo files use this aside from alpha values most of the time. Because I have rarely seen them, I assume this is for coloring the top and bottom of the bti respectfully.
-Color1 and Color2 are shown like this, and are located in the Pane section of an object, rather than the material section, unlike MatColors and TevColors
-  "color1": {
-      "unk1": 812,
-      "unk2": 813,
-      "unknowns": [
-,
-,
-,
-    ],
-      "col1": [
-,
-,
-,
-    ],
-      "col2": [
-,
-,
-,
-    ]
-  },
-  "color2": {
-      "unk1": 814,
-      "unk2": 815,
-      "unknowns": [
-,
-,
-,
-  ],
-      "col1": [
-,
-,
-,
-  ],
-      "col2": [
-,
-,
-,
-  ]
-These values color the top and bottom corners of the bti/object. col1 is for the left corners, and col2 is for the right corners, color1 is for the top corners, color2 is for the bottom corners
-[[Category:File formats]]
-[[Category:Pikmin 2]]