Editing BLO file
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 save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 12: | Line 12: | ||
== PAN2 == | == 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. | + | 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 even more. Every <code>PIC2</code> segment has a string which contains <code>pan2</code>. |
| − | * <code>0x12</code>: The name of the material. | + | * <code>0x12</code>: The name of the material being controlled. |
| − | * <code>0x20</code>: 2 floats representing x and y | + | * <code>0x20</code>: 2 floats representing x and y something. Don't seem to do anything. |
| − | * <code>0x28</code>: 2 floats representing x and y scale. | + | * <code>0x28</code>: 2 floats representing x and y scale. Usually 1. |
| − | * <code>0x3C</code>: 2 floats representing x and y coordinates | + | * <code>0x3C</code>: 2 floats representing x and y coordinates relative to root. |
| − | + | They seem to always end with a <code>BGN1</code>, but I'm not sure what its for. | |
== PIC2 == | == 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: | 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 | + | * <code>0x07</code>: string for <code>pan2</code>, could be what connects the single <code>pic2</code> to a <code>pan2</code>. |
| − | * <code>0x19</code>: Name of material, it likes to have <code>RE</code> before it | + | * <code>0x19</code>: Name of material being edited, it likes to have <code>RE</code> before it, but that's not part of the name. |
| − | * <code>0x28</code>: | + | * <code>0x28</code>: 2 more floats, again not sure what they do. |
* <code>0x30</code>: x and y scale. | * <code>0x30</code>: x and y scale. | ||
| − | * <code>0x45</code>: x and y coordinates relative to | + | * <code>0x45</code>: x and y coordinates relative to <code>PAN2</code> entry. |
| − | After that is a whole row | + | After that is some data I don't get, then a whole row of <code>0xFF</code>. |
== TBX2 == | == TBX2 == | ||
| Line 37: | Line 37: | ||
* <code>0x1A</code>: internal name of material being used. | * <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>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 | + | * <code>0x27</code>: x and y coordinates? |
* <code>0x30</code>: x and y scale. | * <code>0x30</code>: x and y scale. | ||
| − | * <code>0x43</code>: x and y | + | * <code>0x43</code>: more x and y stuff. |
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. | 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. | ||
| − | == | + | == Ending == |
| − | + | After the last <code>PIC2</code> or <code>TBX2</code> are multiple <code>END1</code> and an <code>EXT1</code> with padding to align it. If there's anything I need to correct, let me know on the Discord. Thanks for reading! PikHacker | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:File formats]] | [[Category:File formats]] | ||
[[Category:Pikmin 2]] | [[Category:Pikmin 2]] | ||
