Msbt: Difference between revisions
update documentation and fix some errors (left a lot of the game-specific stuff untouched) |
m formatting + a typo |
||
| Line 2: | Line 2: | ||
<onlyinclude> | <onlyinclude> | ||
'''Message Studio Binary Text''' | '''Message Studio Binary Text''' | ||
<code>MSBT</code> is a binary file format belonging to LibMessageStudio (LMS). These files store the game's text and can contain "tags" that define how said text is displayed/interacted with. | <code>MSBT</code> is a binary file format belonging to LibMessageStudio (LMS). These files store the game's text and can contain "tags" that define how said text is displayed/interacted with.</onlyinclude> | ||
</onlyinclude> | |||
== File Layout == | == File Layout == | ||
<code>MSBT</code> files are composed of a file header followed by blocks (each with their own block header). All sections/blocks must be aligned to 0x10 (16) bytes. In BotW, the file layout is as follows: | <code>MSBT</code> files are composed of a file header followed by blocks (each with their own block header). All sections/blocks must be aligned to 0x10 (16) bytes. In BotW, the file layout is as follows: | ||
| Line 257: | Line 255: | ||
== Tags == | == Tags == | ||
{{expand section}} | {{expand section}} | ||
Message strings can contain tags that alter how the message is displayed or processed. These tags are processed by <code>nn::ui2d::TagProcessorBase</code> which in Nintendo EPD games is | Message strings can contain tags that alter how the message is displayed or processed. These tags are processed by <code>nn::ui2d::TagProcessorBase</code> which in Nintendo EPD games is extended by<code>eui::TagProcessor</code> which can then be further extended by the game to handle game-specific tags. The interpretation of tags is completely game-dependent. | ||
Tags are embedded directly inside of the text and begin with a brief tag header. | Tags are embedded directly inside of the text and begin with a brief tag header. | ||