summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke Stadem <bigbass1997.website@gmail.com>2021-08-02 06:15:04 -0500
committerGitHub <noreply@github.com>2021-08-02 06:15:04 -0500
commit93f8620f68bd10d41117ed751e4f005b398afbbe (patch)
treee2d283a8fcb45f7fb55cad9abbb0450611f94b47
parent0ba3d36571d6614af062f1c3e6d947bb21d4fd7d (diff)
downloadtasd-93f8620f68bd10d41117ed751e4f005b398afbbe.tar.gz
tasd-93f8620f68bd10d41117ed751e4f005b398afbbe.zip
Fixed special ASCII formatting characters
-rw-r--r--spec.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/spec.md b/spec.md
index 0ab4d87..8a7c82a 100644
--- a/spec.md
+++ b/spec.md
@@ -10,7 +10,7 @@ While files generated by emulator dump scripts should provide as much as much in
A very short binary header is used for special/unique data, in the following order:
```
54 41 53 44 00 01 02
-+---Magic #---+ +-Version-+ +-Key Width-+
+└───Magic #───┘ └─Version─┘ └─Key Width─┘
```
The magic number is the ASCII equivalent of `TASD`. The key width defines the how large each key is (in number of bytes). It's unlikely it'll ever be larger than 2 bytes, but it's specified for the sake of forward-compatibility.
@@ -23,16 +23,16 @@ Because a payload could be as small as a few bytes, or much larger than a 16-bit
Below is the hexadecimal representation of a package, with some 2-byte key, and a payload that is 5 bytes wide:
```
A8 2F 01 05 00 11 22 33 44
-+-key-+ +--+ +--+ +---payload----+
+└─key─┘ └──┘ └──┘ └───payload────┘
```
Here is another example of a different key, with a payload that is 260 bytes wide:
```
A8 2F 02 01 04 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
-+-key-+ +--+ +-----+ 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
+└─key─┘ └──┘ └─────┘ 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
......
F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF
- 00 01 02 03 04 +----payload--------------------+
- +---------------+
+ 00 01 02 03 04 ┌────payload────────────────────┘
+ └───────────────┘
```
## Key Definitions