21
edits
Character encoding (Generation I): Difference between revisions
From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
Re-edited changes back differently after discussion with Wowy.
(Undo revision 2948102 by Junebug12851 (talk) Not the correct way to do things) |
Junebug12851 (talk | contribs) (Re-edited changes back differently after discussion with Wowy.) |
||
| Line 10: | Line 10: | ||
===English=== | ===English=== | ||
Text codes are directly mapped to VRAM minus some exceptions for control codes, variables, and strings. Added is a color-coded raw snapshot from VRAM for better clarification. The early character codes map to whatever tilemap is loaded into VRAM currently and most of that is directly accessible from character codes. The parts of the tilemap that aren't accessible are special purpose codes such as control codes (new lines and string termination or null), variables (player name, rival name, or Pokemon Names in Battle), and strings (Pokédex or PKMN) all of which are represented by 1 byte. | |||
The rest of the character codes after the control codes all directly accesses the corresponding VRAM tile and most of it is text or drawing characters. Color coded in '''green''' in the image below are characters a player can select on the game keyboard. These are always guaranteed to be persistent whenever text is shown and will never render any differently because they are always placed in the same locations in VRAM (Tile 0xE1 will always be the PK tile when text is shown). Tiles in '''purple''' are only used by the game to draw a GUI and are not guaranteed to always be there. Tiles in '''blue''' are characters used in in-game dialog but are not on the in-game keyboard and are not always guaranteed to be present. Tiles in '''red''' are not used at all in the games but are still present and not always guaranteed to be there. Tiles in the '''Optional Tilemap Overflow''' are mostly empty and serve as a sort of overflow when game code needs more map tiles to display. One example of this is the Player Badge Screen which uses the tilemap overflow section. | |||
When a tile that isn't guaranteed to be there is ever not there, a leftover tile will be in it's place which is often blank. All tiles 0-255 or 0x00-0xFF are always accessible and will never throw errors. A tile not guaranteed to be present means it's contents could change often throughout game play. This can lead to some pretty fun effects with referencing the early character codes and enjoying that names or strings appear different in different areas of the game. | |||
[[File:English Gen I Character Set.png|450px|thumb|none]] | |||
In the Japanese games (as can be seen below), 0xF2 is distinguishable from 0xE8, with the former meant as a decimal point while the latter is punctuation. Presumably this intention was largely inherited when the English games were made, as most of the game's script uses 0xE8 exclusively; however, 0xF2 appears in the character table for user input, meaning it may appear in user-input names (and, conversely, 0xE8 never should). | In the Japanese games (as can be seen below), 0xF2 is distinguishable from 0xE8, with the former meant as a decimal point while the latter is punctuation. Presumably this intention was largely inherited when the English games were made, as most of the game's script uses 0xE8 exclusively; however, 0xF2 appears in the character table for user input, meaning it may appear in user-input names (and, conversely, 0xE8 never should). | ||
