FF7/Field/Encounter - Revision history

BukTop: 13 revisions imported

2019-05-23T02:14:02Z

13 revisions imported

my_wiki>BukTop: 11 revisions imported

2018-04-04T09:34:22Z

11 revisions imported

my_wiki>BukTop: Created page with "== Overview == The encounter section provides encounter data for the field by referencing battle IDs and providing probabilites for each type o..."

2018-03-30T04:26:52Z

Created page with "== Overview == The encounter section provides encounter data for the field by referencing battle IDs and providing probabilites for each type o..."

my_wiki>Myst6re at 21:44, 28 March 2014

2014-03-28T21:44:39Z

my_wiki>Myst6re: /* Encounter Table Structure */

2011-11-15T22:04:13Z

‎Encounter Table Structure

my_wiki>Myst6re: /* Encounter Entry Types */

2011-11-13T23:01:24Z

‎Encounter Entry Types

my_wiki>Synergy Blades: /* Encounter Structure */ enc_id needs u16.

2007-07-06T01:16:41Z

‎Encounter Structure: enc_id needs u16.

my_wiki>Synergy Blades: /* Switching Between Tables */

2007-02-01T23:45:17Z

‎Switching Between Tables

my_wiki>Synergy Blades: PSX not section 7, I suppose

2007-02-01T21:01:48Z

PSX not section 7, I suppose

my_wiki>Synergy Blades: /* Encounter Entry Types */

2007-02-01T14:16:16Z

‎Encounter Entry Types

@@ Line 1: / Line 1: @@
-== Overview ==
+==  Overview  ==
 The encounter section provides encounter data for the field by referencing [[FF7/Battle/Battle_Scenes|battle IDs]] and providing probabilites for each type of encounter required. The section consists of two ''encounter tables'' that hold sets of these battle configurations; these tables may be switched between using field scripting. The two encounter tables are contiguous and follow directly after the section's length description; due to the presence of the two encounter tables regardless of whether they are used or not, the section length is always 48 bytes.
@@ Line 9: / Line 9: @@
    };
+==  Encounter Table Structure  ==
    struct ENC_TABLE
@@ Line 26: / Line 26: @@
 Following these are the ten encounter structures; these are divided into two groups of six and four, as detailed below. There is also a further two-byte "padding" value, used for alignment.
-=== Switching Between Tables ===
+===  Switching Between Tables  ===
-The purpose of two tables is to allow the scripting system to switch between a choice of two sets of encounter data. This is used in-game to allow two levels of difficulty within one field, so that if the player revisits an area in a later part of the game (such as  areas of Midgar), the enemies will be suitably more difficult. This can be implemented by placing "easier" encounters in the first table, harder encounter IDs in the second table, and switching appropriately (perhaps by checking the Plot Point Variable).
+The purpose of two tables is to allow the scripting system to switch between a choice of two sets of encounter data. This is used in-game to allow two levels of difficulty within one field, so that if the player revisits an area in a later part of the game (such as areas of Midgar), the enemies will be suitably more difficult. This can be implemented by placing "easier" encounters in the first table, harder encounter IDs in the second table, and switching appropriately (perhaps by checking the Plot Point Variable).
 Tables are switched between by simply passing a 0 or 1 to the [[FF7/Field/Script/Opcodes/4B_BTLTB|BTLTB]] opcode, representing the required table. The first table is the default if no BTLTB opcode is specified; either table may be empty, but if switched to using BTLTB, encounters will be deactivated as there will be no encounter data set for that table.
-== Encounter Structure ==
+==  Encounter Structure  ==
    struct ENCOUNTER                      /* pseudo */
@@ Line 42: / Line 42: @@
    // Create from two-byte value
    u16 enc_entry;                        /* holds the read value */
-   u8  prob         = enc_entry >> 10;
+   u8  prob         = enc_entry &gt;&gt; 10;
-   u16 encounter_id = enc_entry & 0x03FF;
+   u16 encounter_id = enc_entry &amp; 0x03FF;
 Each individual two-byte encounter entry is further split into two groups of bits.
@@ Line 51: / Line 51: @@
 The second ten bits denote the [[FF7/Battle/Battle_Scenes|ID]] of the battle.
-=== Encounter Entry Types ===
+===  Encounter Entry Types  ===
 The set of ten battles is split into two groups. The first six battles are generic battles, intended for general use, whose probabilities must total 64. The final four battles are intended to be used in the following order:

@@ Line 3: / Line 3: @@
 The encounter section provides encounter data for the field by referencing [[FF7/Battle/Battle_Scenes|battle IDs]] and providing probabilites for each type of encounter required. The section consists of two ''encounter tables'' that hold sets of these battle configurations; these tables may be switched between using field scripting. The two encounter tables are contiguous and follow directly after the section's length description; due to the presence of the two encounter tables regardless of whether they are used or not, the section length is always 48 bytes.
-<cpp>
+  struct SECTION_ENCOUNTER
 struct SECTION_ENCOUNTER
+      u32       section_length;    /* 0x30 */
-    u32       section_length;    /* 0x30 */
+      ENC_TABLE tables[2];
-    ENC_TABLE tables[2];
+  };
 };
 == Encounter Table Structure ==
-<cpp>
+  struct ENC_TABLE
 struct ENC_TABLE
+      u8        enabled;
-    u8        enabled;
+      u8        rate;
-    u8        rate;
+      ENCOUNTER enc_standard[6];
-    ENCOUNTER enc_standard[6];
+      ENCOUNTER enc_special[4];
-    ENCOUNTER enc_special[4];
+      u16       _pad;
-    u16       _pad;
 The first byte of the table provides a switch to signify whether this table is used or not. If set to ''0'' encounters will not be used, regardless of the table contents; ''1'' signifies the table will be used. The second byte signifies the main encounter rate, and ranges from 0xFF (battles occur infrequently) to 0x01 (battles occur very frequently). 0x00 value causes a division by zero.
@@ Line 37: / Line 34: @@
 == Encounter Structure ==
-<cpp>
+  struct ENCOUNTER                      /* pseudo */
 struct ENCOUNTER                      /* pseudo */
+      bit       prob[6];
-    bit       prob[6];
+      bit       encounter_id[10];
-    bit       encounter_id[10];
-</cpp>
+  // Create from two-byte value
 Each individual two-byte encounter entry is further split into two groups of bits.

@@ Line 25: / Line 25: @@
 </cpp>
-The first byte of the table provides a switch to signify whether this table is used or not. If set to ''0'' encounters will not be used, regardless of the table contents; ''1'' signifies the table will be used. The second byte signifies the main encounter rate, and ranges from 0xFE (battles occur infrequently) to 0x01 (battles occur very frequently).
+The first byte of the table provides a switch to signify whether this table is used or not. If set to ''0'' encounters will not be used, regardless of the table contents; ''1'' signifies the table will be used. The second byte signifies the main encounter rate, and ranges from 0xFF (battles occur infrequently) to 0x01 (battles occur very frequently). 0x00 value causes a division by zero.
 Following these are the ten encounter structures; these are divided into two groups of six and four, as detailed below. There is also a further two-byte "padding" value, used for alignment.

@@ Line 63: / Line 63: @@
 * Back Attack 1
 * Back Attack 2
-* Pre-Emptive Attack
+* Side Attack
 * Attack From Both Sides

@@ Line 47: / Line 47: @@
 u16 enc_entry;                        /* holds the read value */
 u8  prob         = enc_entry >> 10;
-u8  encounter_id = enc_entry & 0x03FF;
+u16 encounter_id = enc_entry & 0x03FF;
 </cpp>

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

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