summaryrefslogtreecommitdiff
path: root/Discovering-GameShark-cheat-codes.md
diff options
context:
space:
mode:
Diffstat (limited to 'Discovering-GameShark-cheat-codes.md')
-rw-r--r--Discovering-GameShark-cheat-codes.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/Discovering-GameShark-cheat-codes.md b/Discovering-GameShark-cheat-codes.md
index 0a8198d..a4fee22 100644
--- a/Discovering-GameShark-cheat-codes.md
+++ b/Discovering-GameShark-cheat-codes.md
@@ -3,8 +3,8 @@ There are a lot of popular cheat codes in Pokémon games: walk through walls, ge
A GameShark cheat code looks like this: `ttvvllhh`
- `tt` is the code type. `01` is typical. `9x` will switch to WRAM bank `x`. `8x` will switch to SRAM bank `x`.
-- `vv` is the value to write into RAM.
-- `hhll` is the RAM address to write to.
+- `vv` is the value to write into RAM. It's a [hexadecimal](https://en.wikipedia.org/wiki/Hexadecimal) byte from $00 to $FF.
+- `hhll` is the RAM address to write to. Note that it's [little-endian](https://en.wikipedia.org/wiki/Endianness) in the code, low byte first.
We can reverse-engineer the meaning of particular codes, and discover our own new codes, with the [**symbol files**](https://github.com/pret/pokecrystal/tree/symbols). When we run `make` to build the ROM, along with the .gbc file it creates a .sym file. This file lists all the labels from the source code with their corresponding banks and addresses in the ROM.