FF7/Field/Script - Revision history

Akari: /* Section 1 Header */

2025-09-20T19:09:01Z

‎Section 1 Header

Akari: /* Section 1 Header */

2025-09-20T18:40:06Z

‎Section 1 Header

Akari at 18:39, 20 September 2025

2025-09-20T18:39:28Z

BukTop: 14 revisions imported

2019-05-23T02:14:06Z

14 revisions imported

my_wiki>BukTop: 12 revisions imported

2018-04-04T09:34:22Z

12 revisions imported

my_wiki>BukTop: Created page with "=== Section 1: Dialog and Event (Halkun, Lasyan, Qhimm and Ficedula) === The First section holds the Field..."

2018-03-24T14:47:11Z

Created page with "=== Section 1: Dialog and Event (Halkun, Lasyan, Qhimm and Ficedula) === The First section holds the Field..."

my_wiki>Myst6re at 21:41, 28 March 2014

2014-03-28T21:41:43Z

my_wiki>Myst6re at 19:02, 1 September 2012

2012-09-01T19:02:29Z

my_wiki>Myst6re: /* Akao blocks */

2011-11-28T09:35:18Z

‎Akao blocks

my_wiki>Myst6re: /* Akao blocks */

2011-11-28T09:12:12Z

‎Akao blocks

@@ Line 8: / Line 8: @@
    struct FF7SCRIPTHEADER {
-     u8 eventDataVersion                 // Release game has 0x02
+     u8 eventDataVersion                 // Release game has 0x02 (early demo has 0x01)
-     u8 eventVersion;			// Release game has 0x05
+     u8 eventVersion;			// Release game has 0x05 (early demo has 0x03)
      char nEntities;			// Number of entities
      char nModels;			// Number of models

@@ Line 8: / Line 8: @@
    struct FF7SCRIPTHEADER {
-     u8 eventDataVersion;		// Release game has 0x02
+     u8 eventDataVersion                 // Release game has 0x02
      u8 eventVersion;			// Release game has 0x05
      char nEntities;			// Number of entities

@@ Line 8: / Line 8: @@
    struct FF7SCRIPTHEADER {
-     u16 unknown1;			// Always 0x0502
+     u8 eventDataVersion;		// Release game has 0x02
      char nEntities;			// Number of entities
      char nModels;			// Number of models

@@ Line 1: / Line 1: @@
-=== Section 1: Dialog and Event ([[User:Halkun|Halkun]], [[User:Lasyan|Lasyan]], [[User:Qhimm|Qhimm]] and [[User:Ficedula|Ficedula]]) ===
+===  Section 1: Dialog and Event ([[User:Halkun|Halkun]], [[User:Lasyan|Lasyan]], [[User:Qhimm|Qhimm]] and [[User:Ficedula|Ficedula]])  ===
 The First section holds the Field Script logic and Dialog data for that particular field file. The first section of the PSX DAT file (excluding the DAT header) and the data in this section are the same. A recap of the PSX DAT file format is later in this document.
 The data in this section also has a header with the following format.
-==== Section 1 Header ====
+====  Section 1 Header  ====
    struct FF7SCRIPTHEADER {
@@ Line 23: / Line 23: @@
    };
-==== Event Script Subsection ====
+====  Event Script Subsection  ====
-Here we have all of the pointers tables, one for each section. Pointers are 2 bytes length.  Each table has a length of 64 bytes, which means a section can have 32 scripts max. Each pointer refers to the first command of the current script.  The section number N begins at the offset header_length+N*64. Note: the only way to retrieve the length of a script is to subtract the position of the next script to the position of the current script.
+Here we have all of the pointers tables, one for each section. Pointers are 2 bytes length. Each table has a length of 64 bytes, which means a section can have 32 scripts max. Each pointer refers to the first command of the current script. The section number N begins at the offset header_length+N*64. Note: the only way to retrieve the length of a script is to subtract the position of the next script to the position of the current script.
-[[User:Cyberman|Cyberman]] 14:05, 30 Dec 2006 (CST) Unused events in the event script subsection point to a [[FF7/Field/Script/Opcodes/00 RET|00 RET]] opcode (each empty script has a unique RET opcode for it in the script). This must be strictly adhered too or the FF7 engine will crash.
+[[User:Cyberman|Cyberman]] 14:05, 30 Dec 2006 (CST) Unused events in the event script subsection point to a [[FF7/Field/Script/Opcodes/00_RET|00 RET]] opcode (each empty script has a unique RET opcode for it in the script). This must be strictly adhered too or the FF7 engine will crash.
-==== Event Script ====
+====  Event Script  ====
 The actual script follows immediately after the aforementioned pointer tables. For a list of opcodes and their arguments, see the [[FF7/Field/Script/Opcodes|opcode table]].
-==== Dialog Subsection ====
+====  Dialog Subsection  ====
-Right after the last script of the preceding section, we find the 2 byte dialog count, followed by the dialog pointer table. Using the dialog count, you can deduce the length of the table: number_of_dialogs*2. After these 2 bytes we have the pointers for each dialog. Be aware that the pointers are relative to the table, which means you must add the position of the table to each pointer in order to find the right position of the dialog.  The dialogs begin right after the table, and the code 255 means the end of the dialog. Note: some hidden dialogs are not referenced in the table!
+Right after the last script of the preceding section, we find the 2 byte dialog count, followed by the dialog pointer table. Using the dialog count, you can deduce the length of the table: number_of_dialogs*2. After these 2 bytes we have the pointers for each dialog. Be aware that the pointers are relative to the table, which means you must add the position of the table to each pointer in order to find the right position of the dialog. The dialogs begin right after the table, and the code 255 means the end of the dialog. Note: some hidden dialogs are not referenced in the table!
-==== Akao blocks ====
+====  Akao blocks  ====
-If there are any Akao offsets (as specified by nExtraOffsets and dwExtraOffsets), they follow after the dialog subsection, beginning with the four-letter AKAO. Akao blocks contain sound-related data such as the music file index for this field. In some fields (junpb_2, mds7pb_1, mds7pb_2 and msd7_w2), the Akaos are mixed with tutorials. I do not know why, but the PC version uses a separate file (junpb.tut, mds7_w.tut or mds7pb.tut) instead of these tutorials.<br>
+If there are any Akao offsets (as specified by nExtraOffsets and dwExtraOffsets), they follow after the dialog subsection, beginning with the four-letter AKAO. Akao blocks contain sound-related data such as the music file index for this field. In some fields (junpb_2, mds7pb_1, mds7pb_2 and msd7_w2), the Akaos are mixed with tutorials. I do not know why, but the PC version uses a separate file (junpb.tut, mds7_w.tut or mds7pb.tut) instead of these tutorials.<br />'''Note:''' Between dialogs and akaos there may be a padding to align the akaos section.

@@ Line 7: / Line 7: @@
 ==== Section 1 Header ====
-<cpp>
+  struct FF7SCRIPTHEADER {
      u16 unknown1;			// Always 0x0502
      char nEntities;			// Number of entities
@@ Line 22: / Line 21: @@
      u16 vEntityScripts[nEntities][32];	// Entity script entry points, or more
   					// explicitly, subroutine offsets
-};
+  };
 ==== Event Script Subsection ====
@@ Line 41: / Line 39: @@
 ==== Akao blocks ====
-If there are any Akao offsets (as specified by nExtraOffsets and dwExtraOffsets), they follow after the dialog subsection, beginning with the four-letter AKAO. Akao blocks contain sound-related data such as the music file index for this field. In some fields (junpb_2, mds7pb_1, mds7pb_2 and msd7_w2), the Akaos are mixed with tutorials. I do not know why, but the PC version uses a separate file (junpb.tut, mds7_w.tut or mds7pb.tut) instead of these tutorials.
+If there are any Akao offsets (as specified by nExtraOffsets and dwExtraOffsets), they follow after the dialog subsection, beginning with the four-letter AKAO. Akao blocks contain sound-related data such as the music file index for this field. In some fields (junpb_2, mds7pb_1, mds7pb_2 and msd7_w2), the Akaos are mixed with tutorials. I do not know why, but the PC version uses a separate file (junpb.tut, mds7_w.tut or mds7pb.tut) instead of these tutorials.<br>

← Older revision	Revision as of 02:14, 23 May 2019
(No difference)

← Older revision	Revision as of 09:34, 4 April 2018
(No difference)

@@ Line 9: / Line 9: @@
 <cpp>
 struct FF7SCRIPTHEADER {
-     u16 unknown1;
+     u16 unknown1;			// Always 0x0502
      char nEntities;			// Number of entities
      char nModels;			// Number of models
      u16 wStringOffset;			// Offset to strings
-     u16 nAkaoOffsets;			// Specifies the number of Akao blocks/offsets
+     u16 nAkaoOffsets;			// Specifies the number of Akao/tuto blocks/offsets
      u16 scale;                          // Scale of field. For move and talk calculation (9bit fixed point).
-     u16 unknown4[3];
+     u16 blank[3];
      char szCreator[8];			// Field creator (never shown)
      char szName[8];			// Field name (never shown)
      char szEntities[nEntities][8];	// Field entity names
-     u32 dwAkaoOffsets[nAkaoOffsets];	// Akao block offsets
+     u32 dwAkaoOffsets[nAkaoOffsets];	// Akao/Tuto block offsets
      u16 vEntityScripts[nEntities][32];	// Entity script entry points, or more
   					// explicitly, subroutine offsets

← Older revision		Revision as of 09:35, 28 November 2011
Line 41:		Line 41:
	==== Akao blocks ====		==== Akao blocks ====

−	If there are any Akao offsets (as specified by nExtraOffsets and dwExtraOffsets), they follow after the dialog subsection, beginning with the four-letter AKAO. Akao blocks contain sound-related data such as the music file index for this field. In some fields (junpb_2, mds7pb_1, mds7pb_2 and msd7_w2), the Akaos are mixed with tutorials.	+	If there are any Akao offsets (as specified by nExtraOffsets and dwExtraOffsets), they follow after the dialog subsection, beginning with the four-letter AKAO. Akao blocks contain sound-related data such as the music file index for this field. In some fields (junpb_2, mds7pb_1, mds7pb_2 and msd7_w2), the Akaos are mixed with tutorials. I do not know why, but the PC version uses a separate file (junpb.tut, mds7_w.tut or mds7pb.tut) instead of these tutorials.

← Older revision		Revision as of 09:12, 28 November 2011
Line 41:		Line 41:
	==== Akao blocks ====		==== Akao blocks ====

−	If there are any Akao offsets (as specified by nExtraOffsets and dwExtraOffsets), they follow after the dialog subsection, beginning with the four-letter AKAO. Akao blocks contain sound-related data such as the music file index for this field.	+	If there are any Akao offsets (as specified by nExtraOffsets and dwExtraOffsets), they follow after the dialog subsection, beginning with the four-letter AKAO. Akao blocks contain sound-related data such as the music file index for this field. In some fields (junpb_2, mds7pb_1, mds7pb_2 and msd7_w2), the Akaos are mixed with tutorials.