Character encoding (Generation III)
The Generation III games use a proprietary character encoding to store text data. The Generation III encoding is greatly different from the encodings used in previous generations, with characters corresponding to different bytes. Versions of the games in different languages may use different encodings, some more different than others.
Some text strings are stored in fixed-length structures while others are stored in a block of text with separate strings simply terminated by 0xFF. In the large, variable-length blocks, usually another structure will have pointers to the appropriate string(s) within that block of text. In the fixed-length structures, strings are still terminated by 0xFF, but any remainder of the allotted space is padded out with 0x00.
Every international game in Generation III (English, French, Italian, German, and Spanish games) contains two character sets: their native set and the Japanese set. The different international character sets are mostly identical save for a few regional differences.
For most text, the game's native character set is used, but if a Pokémon's origin language is Japanese, its nickname and its Original Trainer's name use the Japanese character set. The Japanese games only have the Japanese character set, but with the exception of
0xB8, all inputtable text is identical between international and Japanese character sets.
Note that 0x00 in the following tables is a space (" "), not empty.
Characters on a white background are the only characters that can be input in names;
0xF6 are only available for input in German games. Those on a light gray background may be used in other text strings (such as dialogue) depending on the language of the game. Characters on a dark gray background are unused values that mostly display as spaces in FireRed, LeafGreen, and Emerald; in Ruby and Sapphire, they are holdovers from the Japanese encoding. Characters with a dotted underline differ between regions.
0x83, marked by asterisks (*) above, print spaces 1-7 pixels wide (in ascending order of the hex value). While
0xB0 is "…" in the main fonts of Emerald, FireRed, and LeafGreen, it still displays as "‥" in certain other fonts that exist in the games - for example, the small font used on the party screen and the narrow font used in the Pokédex, bag, and stores.
Differences between games and revisions
In all revisions of Ruby and Sapphire,
0xB0 prints "‥". In certain languages,
0x64 also have differences in different games, as detailed in the section below.
All other differences concern unused character values.
In FireRed and LeafGreen,
0x83 are not used and print as spaces like other unused characters.
In Ruby and Sapphire, many values print Japanese characters, holdovers from the original Japanese encoding. These include:
- All unused characters (on a dark gray background above)
0xA0, in version 1.0 of the English Ruby and Sapphire only
A few characters differ between regions, and among them are quotation marks. These can be input into names, which means a Pokémon with quotation marks in its nickname or OT name will display differently if traded to a game of a different region.
In the table below, the underscores (
_) stand for spaces.
||_, _, MRS
_, _, _EFRLG
Only the characters on a white background below can be input in names. The characters on a dark gray background are printed as spaces in Pokémon FireRed, LeafGreen, and Emerald. Otherwise, the Japanese character set has no differences between games or revisions.
- 0xFA and 0xFB both mark a prompt for the player to press a button to continue the dialogue. However, they will print the new line of dialogue differently: 0xFA will scroll the previous dialogue up one line before printing the next line, while 0xFB will clear the dialogue box entirely.
- 0xFC is an escape character that leads to several different functions (see below).
- 0xFD is an escape character for variables, such as the player's name or a Pokémon's name (see below).
- 0xFE is a line break.
- 0xFF is a terminator, marking the ends of strings.
When 0xFC is followed by...
- 0x01, it will change the color of the text, depending on the byte following. The available colors are listed below.
- 0x02, the text will be highlighted, depending on the byte following. The available colors are listed below.
- 0x03, the text's shadow will have its color changed, depending on the byte following. The available colors are listed below.
- 0x04, the text will be colored and highlighted. The byte immediately following determines the text's color, while a second byte afterward will determine the highlight color. The available colors are listed below.
- 0x06, the text will change size, depending on the byte following. 0x00 will make the font smaller, while anything else will make the font the default size.
- 0x08 and another byte, it produces a pause in the text. The byte after 0x08 determines the length of the pause.
- 0x09, the game will pause text display, and resume upon pressing a button.
- 0x0C, it will escape the byte that follows 0x0C if it is a control character and print a new character. If the second byte after 0xFC is not a control character byte, that byte prints normally.
- When the third byte is 0xFA, "➡" is produced.
- When the third byte is 0xFB, "+" is produced (though in the Japanese games, within the Options screen, it produces "=").
- The other control characters do not produce any characters. In the English games, nothing is printed, while in the Japanese games, miscellaneous data appears to be printed.
- 0x0D, the text will be shifted by a certain amount of pixels, depending on the byte following this one. The effect wears off upon entering a new line.
- 0x10, music will begin to play. Music is specified by the two bytes following, in little endian format.
- 0x15, text will be rendered in the Japanese font
- 0x16, text will be rendered in the International font
- 0x17, music will be paused.
- 0x18, music will resume playing.
A table of available text, highlight, and shadow colors is shown below.
When 0xFD is followed by one of the following bytes, it prints a text variable or version-dependent text. Version-dependent text is only used in Pokémon Ruby, Sapphire, and Emerald; in Pokémon Emerald, all of these values are the same as Pokémon Sapphire, except the version name. The text printed by version-dependent text variable is constant within a single game, but varies between versions and languages.
- Text variables
- 0x01: the player's name
- 0x02, 0x03, or 0x04: whatever text has been assigned to one of three buffers using a variety of script commands
- 0x06: the rival's name
- Version-dependent text
|Variable ID||Description||English content|
|0x07||the game's name||RUBY||SAPPHIRE||EMERALD|
|0x08||the name of the villainous team||MAGMA||AQUA|
|0x09||the name of the non-villainous team||AQUA||MAGMA|
|0x0A||the name of the villainous team's leader||MAXIE||ARCHIE|
|0x0B||the name of the non-villainous team's leader||ARCHIE||MAXIE|
|0x0C||the name of the villainous team's Legendary Pokémon||GROUDON||KYOGRE|
|0x0D||the name of the opposing Legendary Pokémon||KYOGRE||GROUDON|
- In the name field for Eggs, the game places the bytes
0x60 0x6F 0x8Bcorresponding to タマゴ (tamago, the Japanese word for egg). This remains in the English version even though the characters have been replaced.
|This data structure article is part of Project Games, a Bulbapedia project that aims to write comprehensive articles on the Pokémon games.|