summaryrefslogtreecommitdiff
path: root/Edit-the-Town-Map.md
diff options
context:
space:
mode:
Diffstat (limited to 'Edit-the-Town-Map.md')
-rw-r--r--Edit-the-Town-Map.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Edit-the-Town-Map.md b/Edit-the-Town-Map.md
index 3c34c46..4140d2c 100644
--- a/Edit-the-Town-Map.md
+++ b/Edit-the-Town-Map.md
@@ -40,7 +40,7 @@ The GBC screen is 20 tiles wide, so 5 more white tiles would need to be placed a
Now, editing the layout shouldn't be that hard, provided you've been paying attention so far. It might be easier to start with a mockup of your map, and then converting that information into RLE code.
-All you have to do here is take the number of the tile you want to be placed next, then how many of them you want in a row (as a [hexadecimal number](https://www.rapidtables.com/convert/number/decimal-to-hex.html)). Remember, you can only place 15 tiles in a row with one byte. In order to add more, simply use the next byte for the same tile.
+All you have to do here is take the number of the tile you want to be placed next, then how many of them you want in a row (as a [hexadecimal number](https://www.rapidtables.com/convert/number/decimal-to-hex.html)). Remember, you can only place 15 tiles in a row with one byte. In order to add more, simply use the next byte for the same tile. KEEP IN MIND THAT THE CODE MUST END WITH BYTE $00.
The beauty of the disassembly is that the data for the new tile map can be larger than the original, without tedious repointing. If you run out of room, you can simply make the file larger, and it will still compile perfectly.