Almost all the text in Roody:2d (the exceptions being the title screen, the debug console, and the display block) is loaded from localization files. For officially supported languages (english), the text is in these files
The contents of all localization .txt files are UTF-8 encoded.
Their file names are ASCII. File names follow the format
[language] is the name that will be used to select the language in configuration files. Do not put an underscore or space in the middle of [language].
[optional_organizational_file_name] can be any string, or omitted.
All the contents can just be in one large
but it may be easier to split it up into separate files.

For custom languages, localization files can be loaded from
The "piratespeak_pack_v1" folder can be named anything. When distributing a custom language pack, distribute the "piratespeak_pack_v1" folder.

The Roody:2d debug console can be opened by pressing the tilde key ~. It is above the Tab key on most keyboards.
To change langues, use the console command
Where <string> is the [language] in the name of localization files. NOT the folder name of the pack.

Roody:2d has "text styles" that define the font and some meta data for a font.
The default text style for Roody:2d is pixel_8 with the font PressStart2p.ttf. It has very limited unicode support.



There is another text style, pixel_16 with the font GnuUnifontFull-Pm9P.ttf. It has much better unicode support.



You can change text style to pixel_16 in the graphics options menu by setting font to 16x16, or by running the command


If a user is installing a language pack, they probably want it to load automatically.
Create this text file
Open it with a text editor and write the commands you want to run on Roody:2d start up

A snippet of english_blocks.txt
"#" at the start of a line denotes a comment line

Every non-comment line follows the format of
Everything on the left side of the "=" forms the key, and everything on the right side of the "=" forms the text that will be displayed. There can be any amount of whitespace before the "=".
If a certain key is missing, roody2d will display the key string with asterisks.



Since the source code of Roody:2d is written in English, many keys and display texts are similar for the official English localization files. Do not change they keys, only change the values.
Text values end at the newline, unless the line ends in a backslash. A backslash can make multi-line text.



Most keys follow a format
KEY_TOPIC is mostly just organizational, but some KEY_TOPICs have special colors for sub localizations.


BLOCK_TITLE also has the same color as BLOCK
ENTITY_TITLE also has the same color as ENTITY

Localization texts can reference other translation keys with {}


In places that display a lot of text, like the guidebook, WAILA, and tutorial messages, this is where the KEY_TOPIC colors appear


It is possible add new keys just to get the color, but the KEY_TOPIC colors should only be used appropriately.



Creating individual keys for every permeation of capitalized and plural is tedious.
Sub-localizations have can have modifiers by appending a |
These modifiers are English specific, so when translating to a different language, this will only be of use when reading the official English localization files.



Text can show the currently bound key of actions with []. When translating, do not change the string inside the [], it is not displayed to the player.


It automatically updates when keys are rebound



Multiple inputs are concatenated with the 2 space characters and the translation key OPERATOR or
The names of inputs, like "RAlt" or "Delete" are not translatable.