From 3906aeb776465d0a372b2596d7a4d58301d571f6 Mon Sep 17 00:00:00 2001 From: bigbass1997 Date: Sat, 15 Jul 2023 01:07:52 -0500 Subject: Fixed spelling mistakes in spec --- src/docs/draft-tasd-spec-0001.xml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'src') diff --git a/src/docs/draft-tasd-spec-0001.xml b/src/docs/draft-tasd-spec-0001.xml index cf9d6df..cd55fd9 100644 --- a/src/docs/draft-tasd-spec-0001.xml +++ b/src/docs/draft-tasd-spec-0001.xml @@ -43,7 +43,7 @@
Introduction - The Tool Assisted Speedrun Dump (TASD) interchange format is a file format for storing data to allow "Tool Assisted Speedruns" or "Tool Assited Superplays" to be played on physical video game console hardware using TAS replay devices. Created to be hardware and software agnostic, the TASD interchange format uses a key-based, binary, packet format to break up pieces of information into easily-parsable and forward-compatible chunks. The format is extensible by simply defining additional keys or value types as necessary. When parsing the file, software can skip any packets whose key is unknown or unsupported. + The Tool Assisted Speedrun Dump (TASD) interchange format is a file format for storing data to allow "Tool Assisted Speedruns" or "Tool Assisted Superplays" to be played on physical video game console hardware using TAS replay devices. Created to be hardware and software agnostic, the TASD interchange format uses a key-based, binary, packet format to break up pieces of information into easily-parsable and forward-compatible chunks. The format is extensible by simply defining additional keys or value types as necessary. When parsing the file, software can skip any packets whose key is unknown or unsupported. Keys can be used multiple times or completely omitted as needed. This reusability eliminates the need of a predefined delimiter to separate pieces of data such as a list of TAS authors. While files generated by emulator dump scripts should provide as much information as possible, because keys are optional, the file can be expanded later with any additional data as desired. No intermediary file format is necessary.
@@ -130,7 +130,7 @@ +-----------+===========+]]>
    -
  • In this example, enough variable boxes are in the packet diagram to require being split into 2 sections to take up less horizontal space in this documentation. The packet diagram is seperated by an ellipsis (...) on the same text row as the variable names to signify that the packet diagram is continuing.
    • +
  • In this example, enough variable boxes are in the packet diagram to require being split into 2 sections to take up less horizontal space in this documentation. The packet diagram is separated by an ellipsis (...) on the same text row as the variable names to signify that the packet diagram is continuing.
@@ -223,7 +223,7 @@
[00 10]
BLANK_FRAMES
[00 11]
VERIFIED
[00 12]
MEMORY_INIT
-
[00 13]
GAME_IDENIFIER
+
[00 13]
GAME_IDENTIFIER
[00 14]
MOVIE_LICENSE
[00 15]
MOVIE_FILE
[00 F0]
PORT_CONTROLLER
@@ -297,7 +297,7 @@
Specifies the core of the emulator used while dumping the TAS controller inputs. This packet type is OPTIONAL and a TASD file SHOULD NOT contain more than 1 of this packet type in direct form. Discussed in ().
[00 0A] - TAS_LAST_MODIFIED
Specifies when the TAS was last modified. Frequently used to specify the date and time when the TAS was published. This packet type is OPTIONAL and a TASD file SHOULD NOT contain more than 1 of this packet type in direct form. Discussed in ().
-
[00 0B] - DUMP_CREATEED
+
[00 0B] - DUMP_CREATED
Specifies when the TASD file was first created. This packet is OPTIONAL but SHOULD be included in a TASD file and a TASD file SHOULD NOT contain more than 1 of this packet type. Discussed in ().
[00 0C] - DUMP_LAST_MODIFIED
Specifies when the TASD file was last modified. This packet is OPTIONAL but SHOULD be included in a TASD file and a TASD file SHOULD NOT contain more than 1 of this packet type. Discussed in ().
@@ -1893,6 +1893,8 @@