User Tools

Site Tools


zxt:format_specification

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
zxt:format_specification [2021/08/06 08:46] asiezxt:format_specification [2021/08/11 06:21] (current) – Use propagating tag for ZAXMAKE/ZXTSPLIT links, instead of single version link. The propagation can be cancelled (even retroactively if needed) if changes are made that violate this specification. zzo38
Line 1: Line 1:
 ====== ZXT Extension Format Specification ====== ====== ZXT Extension Format Specification ======
  
-Version 0.XX+Version 1.0.0
  
 By Adrian "asie" Siekierka By Adrian "asie" Siekierka
  
-The specification follows a MAJOR.MINOR numbering scheme.+Special thanks: endgame, GreaseMonkey, Lancer-X, Noser, The Mysterious KM, WiL, zzo38 
 + 
 +The specification follows a MAJOR.MINOR.PATCH numbering scheme, where: 
 + 
 +  * Changes to the MAJOR number are expected to introduce breaking changes, resulting in a change of the extension header magic number; 
 +  * Changes to the MINOR number are expected to introduce changes which don't break backwards compatibility, such as giving meaning to reserved values or defining undefined behaviour; 
 +  * Changes to the PATCH number are expected to introduce changes which don't impact the meaning of the specification, such as fixing typos or clarifying used language. 
 +  
 +For example, a ZXT 1.1.x world which doesn't utilize functionality specific to ZXT 1.1.x would be expected to work as-is in a ZXT 1.0.x engine implementation; there is no such requirement placed on a ZXT 2.0.x world.
  
 ===== Introduction ===== ===== Introduction =====
  
-Extending and tweaking the functionality of the ZZT game engines ((ZZT and Super ZZT)) has always been an undercurrent in its world development community. While many games relying on edited executables or TSRs ((Terminate-Stay Resident programs)) have been released in the past, they ran into key problems, keeping their count small and the idea unpopular:+Extending and tweaking the functionality of the ZZT game engines ((ZZT and Super ZZT)) has always been an undercurrent in their world development community. While many games relying on edited executables or TSRs ((Terminate-Stay Resident programs)) have been released in the past, they ran into key problems, keeping their count small and the overall idea unpopular:
  
   * The lack of source code greatly increased the difficulty of performing non-trivial modifications.   * The lack of source code greatly increased the difficulty of performing non-trivial modifications.
-  * The requirement for special batch scripts or modified executables, typically made specifically for a given game, created additional hassle for the end user.+  * The requirement for special batch scripts or modified executables, typically made specifically for a given game, created additional hassle for the end user when trying to play such a game.
   * No consistent means of signaling required extensions was devised. For most worlds, this made them indistinguishable from ZZT 3.2-compatible ones for the end user or reimplementations, hurting compatibility.   * No consistent means of signaling required extensions was devised. For most worlds, this made them indistinguishable from ZZT 3.2-compatible ones for the end user or reimplementations, hurting compatibility.
  
Line 96: Line 104:
 | 2 | u32 | owner_id | Extension owner ID. | | 2 | u32 | owner_id | Extension owner ID. |
 | 6 | u16 | selector_id | Extension selector ID. | | 6 | u16 | selector_id | Extension selector ID. |
-| 8 | u8 | reserved_0 | Reserved. |+| 8 | u8 | reserved_0 | Reserved; must be set to 0. |
 | 9 | u16 | field_length | Field length. Values between 0 and 65534 refer to the length in bytes; if set to 65535, an u32 containing the 32-bit field length in bytes follows. | | 9 | u16 | field_length | Field length. Values between 0 and 65534 refer to the length in bytes; if set to 65535, an u32 containing the 32-bit field length in bytes follows. |
 | 11 | u8[field_length] | field_data | Field data. Extension-defined. | | 11 | u8[field_length] | field_data | Field data. Extension-defined. |
Line 115: Line 123:
 | 8 .. 15 | reserved | Reserved. | If set, an implementation MUST NOT continue parsing of the extension block. | | | 8 .. 15 | reserved | Reserved. | If set, an implementation MUST NOT continue parsing of the extension block. | |
  
-It is important to note that the flags can be distinct from the ID pair; for instance, the same ZZT-OOP extension can be defined as "recommended for playing" if optional for gameplay, but "mandatory for playing" if required for gameplay. However, an extension standard may require you to set or clear certain bits.+It is important to note that the flags can be distinct from the ID pair; for instance, the same ZZT-OOP extension can be defined as "recommended for playing" if optional for gameplay, but "mandatory for playing" if required for gameplay. However, an extension standard may require you to set or clear certain bits for compliance.
  
 ===== Extension IDs ===== ===== Extension IDs =====
Line 123: Line 131:
 ==== Owner ID Ranges ==== ==== Owner ID Ranges ====
  
-  * The range ''00000000'' - ''000000FF'' is reserved for **standard extensions** - potential "obvious" changes everyone agrees upon, as well as potential expansions to this standard.+  * The range ''00000000'' - ''000000FF'' is reserved for **standard extensions** - types of changes everyone agrees upon, as well as potential expansions to this standard.
   * The range ''00000100'' - ''FFFFFEFF'' is available for **public extensions** - you are free to claim them via signaling intent on the [[zxt:owner_ids|ZXT Owner IDs]] page.   * The range ''00000100'' - ''FFFFFEFF'' is available for **public extensions** - you are free to claim them via signaling intent on the [[zxt:owner_ids|ZXT Owner IDs]] page.
   * The range ''FFFFFF00'' - ''FFFFFFFF'' is reserved for **private use extensions** - prototypes and/or experiments within internal/development versions of worlds and engine implementations. Publicly released worlds and engine implementations SHOULD NOT use this range.   * The range ''FFFFFF00'' - ''FFFFFFFF'' is reserved for **private use extensions** - prototypes and/or experiments within internal/development versions of worlds and engine implementations. Publicly released worlds and engine implementations SHOULD NOT use this range.
Line 150: Line 158:
  
   * ZXT standard compliance concerns only the game engine's operation. The user interface and other external factors not impacting gameplay or game presentation are not in scope.   * ZXT standard compliance concerns only the game engine's operation. The user interface and other external factors not impacting gameplay or game presentation are not in scope.
-  * An implementation MAY choose to be compatible only with ZXT worlds containing certain extensions. Compatibility with un-extended ZZT worlds is OPTIONAL.+  * An implementation MAY choose to be compatible only with ZXT worlds containing certain extensions. Compatibility with un-extended ZZT worlds for a ZXT implementation is OPTIONAL.
  
 ==== Engine Accuracy ==== ==== Engine Accuracy ====
Line 215: Line 223:
  
 ===== Implementations ===== ===== Implementations =====
 +
 +This is not a formal part of the specification.
 +
 +==== Libraries ====
 +
 +=== ZXT 1.0.x ===
 +
 +  * [[https://github.com/OpenZoo/ClassicZoo/blob/0b39c34b2437f5e73b3601044545cefa586cf5dc/SRC/ZXTMGR.PAS|ZXTMGR v0.3.1]] - Turbo Pascal 5.5-compatible library, intended for using within a ZZT fork.
 +
 +==== Tools ====
 +
 +=== ZXT 1.0.x ===
 +
 +  * [[http://zzo38computer.org/fossil/freezzt.ui/dir?ci=zxt1.0&name=zxt|ZAXMAKE]], PostScript tooling for defining ZXT extension headers.
 +  * [[http://zzo38computer.org/fossil/freezzt.ui/dir?ci=zxt1.0&name=zxt|ZXTSPLIT]], C utility for extraction, listing and maintenance of ZXT/ZAX files.
 +
 +==== Engines ====
  
 TBD TBD
zxt/format_specification.1628239597.txt.gz · Last modified: 2021/08/06 08:46 by asie