FF8/BattleStructure - Revision history

Myst6re at 22:30, 5 January 2020

2020-01-05T22:30:32Z

BukTop: 10 revisions imported

2019-05-23T02:22:19Z

10 revisions imported

my_wiki>BukTop: 8 revisions imported

2018-04-04T09:36:41Z

8 revisions imported

my_wiki>Albeoris: Created page with "By JeMaCheHi Scene.out contains enemy placement data and flags for each of the game's battle encounters. See the corresponding thread: http://forums.qhimm.com/index.php?topi..."

2018-03-24T00:13:10Z

Created page with "By JeMaCheHi Scene.out contains enemy placement data and flags for each of the game's battle encounters. See the corresponding thread: http://forums.qhimm.com/index.php?topi..."

my_wiki>JeMaCheHi at 11:55, 1 August 2015

2015-08-01T11:55:49Z

my_wiki>MaKiPL: Added original encounter codes wiki url

2015-07-27T17:58:12Z

Added original encounter codes wiki url

my_wiki>Shard: /* Notes */

2015-03-03T07:27:52Z

‎Notes

my_wiki>Shard: /* File Structure */

2015-01-15T17:29:11Z

‎File Structure

my_wiki>Shard: fixed formatting

2015-01-15T17:28:36Z

fixed formatting

my_wiki>Shard at 17:26, 15 January 2015

2015-01-15T17:26:44Z

@@ Line 71: / Line 71: @@
 ! align="left" | 0x78
 | 8
-| Enemy level. Each enemy level is 1 byte. Numbers from 0x0 to 0x64 are fixed levels up to 100. From 0x64 to 0xFF... Still don't know because it makes weird things...
+| Enemy level. Each enemy level is 1 byte. Numbers from 1 to 100 are fixed levels. From 101 to 199 are max levels fixed (min level remains 1). When 255, it is disabled (standard behaviour). And 215 (Deep Sea), 210 (Deep Sea), 251 (Final Bosses), 252 (Ultimecia Castle), 254 (Scripted battles)... Still don't know...
 |}

@@ Line 3: / Line 3: @@
 Scene.out contains enemy placement data and flags for each of the game's battle encounters.
 See the corresponding thread: http://forums.qhimm.com/index.php?topic=15816.0
 ==File Structure==
 Scene.out contains no header. It is a raw list of 1024 encounters. Each encounter block consists of 128 bytes and has the following structure:
-{| border="1" cellspacing="1" cellpadding="3" style="border: 1px solid black; border-collapse: collapse;"
+{| class="wikitable"
-! style="background:rgb(204,204,204)" | Offset
+! Offset
-! style="background:rgb(204,204,204)" | Length
+! Length
-! style="background:rgb(204,204,204)" | Description
+! Description
 |-
 ! align="left" | 0x00
@@ Line 21: / Line 19: @@
 ! align="left" | 0x01
 | 1
-| Flags to configure some battle parameters and it works like 8 binary flags (see below)
+| Refers to some battle aspects and it works like 8 binary switches (see below)
 |-
 ! align="left" | 0x02
 | 1
-| Main camera animation.  This is for the battle entrance animation (when the party and the monsters appear). The first nibble represents the '''camera number''', the second one the '''animation number'''. (See below about cameras)
+| Still don't know, but I suspect that it has something to do with camera movement. If you set it to 0xFF camera will always be fixed
 |-
 ! align="left" | 0x03
 | 1
-| Secondary camera. Works exactly the same as the main camera, but this one will be used less frecuently.(See below about cameras)
+| unkonwn
 |-
 ! align="left" | 0x04
 | 1
-| Hidden enemies. Hides an enemy for each activated bit in the byte. (see below for "enemy flags")
+| Visible enemies. Shows an enemy for each bit in the byte. (see below for "enemy switches")
 |-
 ! align="left" | 0x05
 | 1
-| Loaded enemies. Show the enemies that are been actually fought. Loaded enemies will attack you(also, refer to "enemy flags").
+| Loaded enemies. Show the enemies that are been actually fought. Loaded enemies will attack you.
 |-
 ! align="left" | 0x06
 | 1
-| Targetable enemies. Show the enemies which will appear in the target window. Careful with this, if you put untargetable enemies battle will never end. (see "enemy flags" too)
+| Targetable enemies. Show the enemies which will apear in the target window. Careful with this, if you put untargetable enemies battle will never end. (see "enemy switches" too)
 |-
 ! align="left" | 0x07
 | 1
-| Enabled enemies. Also works like eight binary flags. Each activated flag is an enabled enemy. If the flag for a certain enemy is disabled, the three previous sections will be ignored. See below
+| Number of enemies. Also works like eight binary switches. See below
 |-
 ! align="left" | 0x08
@@ Line 57: / Line 55: @@
 ! align="left" | 0x40
 | 16
-| Unknown. A certain enemy also has always the same value (f.e G-Soldier -> 0x7f70), and some of this values can be repeated between enemies. Slots with no enemies (with a dummy) always have the value 0x00C8.
+| unknown
 |-
 ! align="left" | 0x50
 | 16
-| Unknown. It always has the same value as the previous section.
+| Still under research, but this is usually the same as the previous field's value.
 |-
 ! align="left" | 0x60
 | 16
-| Unknown. A certain enemy has always the same value but different from the two previous sections. Slots with no enemies always have the value 0xEA60
+| unknown
 |-
 ! align="left" | 0x70
 | 8
-| Unknown. Once more, A certain enemy has always the same value but different from previous sections.
+| unknown
 |-
 ! align="left" | 0x78
@@ Line 76: / Line 74: @@
 |}
-==About flags==
+==Notes==
 Each 128block can have up to 8 enemies, but if more than 4 are shown at the same time, the game will crash. This could seem stupid, but it's not. If you think about some battles, like the final battle (where we have 8 enemies), all the monsters are present, but only one or two are shown at any given time. The rest appear through scripting.
-Some byte fields are just 8 flags contained in a byte. To configure it you just have to sum the values you need. Here's what I've found:
+Some byte fields are just 8 switches. Here's what I've found:
-The game engine will use one or other camera randomly, but will use the main one way more frequently (in my tests, for each 5 battles, the game used the main camera around 4 times)
+In 0x01:
-Also, a few considerations about these camera parameters:
+In 0x04, 0x05, 0x06, and 0x07
-:-Camera number. It can take values from 0 to 3. The original scene.out never has greater values. Values greater than 3 will result in no camera animations, having a fixed camera. Some stages have less than 3 camera numbers. This leads me to think that this camera stuff is really stored on .x files, and this values are just pointers, or indexes, or something of the kind.
+An important note: If you put an enemy that "summons" another one (Ultimecia summoning Griever, Sphinxara summoning jelleye...) it will summon the enemy from certain slot. This means that if you put that enemy in another battle, it will still summon that slot, because (I think) that summoning is scripted in its AI (in c9m???.dat)

@@ Line 21: / Line 21: @@
 ! align="left" | 0x01
 | 1
-| Refers to some battle aspects and it works like 8 binary switches (see below)
+| Flags to configure some battle parameters and it works like 8 binary flags (see below)
 |-
 ! align="left" | 0x02
 | 1
-| Still don't know, but I suspect that it has something to do with camera movement. If you set it to 0xFF camera will always be fixed
+| Main camera animation.  This is for the battle entrance animation (when the party and the monsters appear). The first nibble represents the '''camera number''', the second one the '''animation number'''. (See below about cameras)
 |-
 ! align="left" | 0x03
 | 1
-| unkonwn
+| Secondary camera. Works exactly the same as the main camera, but this one will be used less frecuently.(See below about cameras)
 |-
 ! align="left" | 0x04
 | 1
-| Visible enemies. Shows an enemy for each bit in the byte. (see below for "enemy switches")
+| Hidden enemies. Hides an enemy for each activated bit in the byte. (see below for "enemy flags")
 |-
 ! align="left" | 0x05
 | 1
-| Loaded enemies. Show the enemies that are been actually fought. Loaded enemies will attack you.
+| Loaded enemies. Show the enemies that are been actually fought. Loaded enemies will attack you(also, refer to "enemy flags").
 |-
 ! align="left" | 0x06
 | 1
-| Targetable enemies. Show the enemies which will apear in the target window. Careful with this, if you put untargetable enemies battle will never end. (see "enemy switches" too)
+| Targetable enemies. Show the enemies which will appear in the target window. Careful with this, if you put untargetable enemies battle will never end. (see "enemy flags" too)
 |-
 ! align="left" | 0x07
 | 1
-| Number of enemies. Also works like eight binary switches. See below
+| Enabled enemies. Also works like eight binary flags. Each activated flag is an enabled enemy. If the flag for a certain enemy is disabled, the three previous sections will be ignored. See below
 |-
 ! align="left" | 0x08
@@ Line 57: / Line 57: @@
 ! align="left" | 0x40
 | 16
-| unknown
+| Unknown. A certain enemy also has always the same value (f.e G-Soldier -> 0x7f70), and some of this values can be repeated between enemies. Slots with no enemies (with a dummy) always have the value 0x00C8.
 |-
 ! align="left" | 0x50
 | 16
-| Still under research, but this is usually the same as the previous field's value.
+| Unknown. It always has the same value as the previous section.
 |-
 ! align="left" | 0x60
 | 16
-| unknown
+| Unknown. A certain enemy has always the same value but different from the two previous sections. Slots with no enemies always have the value 0xEA60
 |-
 ! align="left" | 0x70
 | 8
-| unknown
+| Unknown. Once more, A certain enemy has always the same value but different from previous sections.
 |-
 ! align="left" | 0x78
@@ Line 76: / Line 76: @@
 |}
-==Notes==
+==About flags==
 Each 128block can have up to 8 enemies, but if more than 4 are shown at the same time, the game will crash. This could seem stupid, but it's not. If you think about some battles, like the final battle (where we have 8 enemies), all the monsters are present, but only one or two are shown at any given time. The rest appear through scripting.
-Some byte fields are just 8 switches. Here's what I've found:
+Some byte fields are just 8 flags contained in a byte. To configure it you just have to sum the values you need. Here's what I've found:
-In 0x01:
+In 0x01 (battle configuration flags):
-{{:FF8/Field/Script/Opcodes/069 BATTLE}}
+:+0x80: Not random fight. Every scripted battle has this one enabled.
-In 0x04, 0x05, 0x06, and 0x07
+In 0x04, 0x05, 0x06, and 0x07 (hidden/loaded/targetable/enabled enemies).
-:+128: 1st enemy relative
+:+0x80: 1st enemy flag
-:+64: 2nd enemy relative
+:+0x40: 2nd enemy flag
-:+32: 3rd enemy relative
+:+0x20: 3rd enemy flag
-:+16: 4th enemy relative
+:+0x10: 4th enemy flag
-:+8: 5th enemy relative
+:+0x08: 5th enemy flag
-:+4: 6th enemy relative
+:+0x04: 6th enemy flag
-:+2: 7th enemy relative
+:+0x02: 7th enemy flag
-:+1: 8th enemy relative
+:+0x01: 8th enemy flag
-An important note: If you put an enemy that "summons" another one (Ultimecia summoning Griever, Sphinxara summoning jelleye...) it will summon the enemy from certain slot. This means that if you put that enemy in another battle, it will still summon that slot, because (I think) that summoning is scripted in its AI (in c9m???.dat)
+An important note: If you put an enemy that "summons" another one (Ultimecia summoning Griever, Sphinxara summoning jelleye...) it will summon the enemy from certain slot. This means that if you put that enemy in another battle, it will still summon that slot, because (It's now confirmed) that summoning is scripted in its AI (in c9m???.dat) as an enemy ability.

@@ Line 3: / Line 3: @@
 Scene.out contains enemy placement data and flags for each of the game's battle encounters.
 See the corresponding thread: http://forums.qhimm.com/index.php?topic=15816.0
 ==File Structure==

@@ Line 80: / Line 80: @@
 In 0x01:
-*+128: Not random fight. Every scripted battle has this one enabled.
+{{:FF8/Field/Script/Opcodes/069 BATTLE}}
 In 0x04, 0x05, 0x06, and 0x07
-*+128: 1st enemy relative
+:+128: 1st enemy relative
-*+64: 2nd enemy relative
+:+64: 2nd enemy relative
-*+32: 3rd enemy relative
+:+32: 3rd enemy relative
-*+16: 4th enemy relative
+:+16: 4th enemy relative
-*+8: 5th enemy relative
+:+8: 5th enemy relative
-*+4: 6th enemy relative
+:+4: 6th enemy relative
-*+2: 7th enemy relative
+:+2: 7th enemy relative
-*+1: 8th enemy relative
+:+1: 8th enemy relative
 An important note: If you put an enemy that "summons" another one (Ultimecia summoning Griever, Sphinxara summoning jelleye...) it will summon the enemy from certain slot. This means that if you put that enemy in another battle, it will still summon that slot, because (I think) that summoning is scripted in its AI (in c9m???.dat)

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

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

← Older revision		Revision as of 17:26, 15 January 2015
Line 1:		Line 1:
		+	By JeMaCheHi
		+
	Scene.out contains enemy placement data and flags for each of the game's battle encounters.		Scene.out contains enemy placement data and flags for each of the game's battle encounters.

Line 4:		Line 6:

	==File Structure==		==File Structure==
		+	Scene.out contains no header. It is a raw list of 1024 encounters. Each encounter block consists of 128 bytes and has the following structure:
		+
		+	{\| border="1" cellspacing="1" cellpadding="3" style="border: 1px solid black; border-collapse: collapse;"
		+	! style="background:rgb(204,204,204)" \| Offset
		+	! style="background:rgb(204,204,204)" \| Length
		+	! style="background:rgb(204,204,204)" \| Description
		+	\|-
		+	! align="left" \| 0x00
		+	\| 1
		+	\| Battle scenario. The value here corresponds to the number in the a0stg???.x files (into battle.fs file). You have to convert it to hex
		+	!-
		+	\| align="left" \| 0x01
		+	\| 1
		+	\| Refers to some battle aspects and it works like 8 binary switches (see below)
		+	!-
		+	\| align="left" \| 0x02
		+	\| 1
		+	\| Still don't know, but I suspect that it has something to do with camera movement. If you set it to 0xFF camera will always be fixed
		+	!-
		+	\| align="left" \| 0x03
		+	\| 1
		+	\| unkonwn
		+	!-
		+	\| align="left" \| 0x04
		+	\| 1
		+	\| Visible enemies. Shows an enemy for each bit in the byte. (see below for "enemy switches")
		+	!-
		+	\| align="left" \| 0x05
		+	\| 1
		+	\| Loaded enemies. Show the enemies that are been actually fought. Loaded enemies will attack you.
		+	!-
		+	\| align="left" \| 0x06
		+	\| 1
		+	\| Targetable enemies. Show the enemies which will apear in the target window. Careful with this, if you put untargetable enemies battle will never end. (see "enemy switches" too)
		+	!-
		+	\| align="left" \| 0x07
		+	\| 1
		+	\| Number of enemies. Also works like eight binary switches. See below
		+	!-
		+	\| align="left" \| 0x08
		+	\| 48
		+	\| Enemy coordinates. Its a set of 6x8 bytes which describes each enemy's coordinate in (x,y,z) format. So, first 6 bytes would be enemy 1's coords, next 6 enemy 2's ones, and so on.
		+	!-
		+	\| align="left" \| 0x38
		+	\| 8
		+	\| Enemies. Each byte represents an enemy. To know what enemy you're working with, you can check the c0m???.dat files in battle.fs. You just have to convert it to hex and add 0x10. Be careful, if you put numbers under 0x10 as enemies, battle will crush.
		+	!-
		+	\| align="left" \| 0x40
		+	\| 16
		+	\| unknown
		+	!-
		+	\| align="left" \| 0x50
		+	\| 16
		+	\| Still under research, but this is usually the same as the previous field's value.
		+	!-
		+	\| align="left" \| 0x60
		+	\| 16
		+	\| unknown
		+	!-
		+	\| align="left" \| 0x70
		+	\| 8
		+	\| unknown
		+	!-
		+	\| align="left" \| 0x78
		+	\| 8
		+	\| Enemy level. Each enemy level is 1 byte. Numbers from 0x0 to 0x64 are fixed levels up to 100. From 0x64 to 0xFF... Still don't know because it makes weird things...
		+	\|}
		+
		+	==Notes==
		+	Each 128block can have up to 8 enemies, but if more than 4 are shown at the same time, the game will crash. This could seem stupid, but it's not. If you think about some battles, like the final battle (where we have 8 enemies), all the monsters are present, but only one or two are shown at any given time. The rest appear through scripting.
		+
		+	Some byte fields are just 8 switches. Here's what I've found:
		+
		+	In 0x01:
		+	*+128: Not random fight. Every scripted battle has this one enabled.
		+	*+64: Setting this on will make that you will always be back attacked.
		+	*+32: Setting this on will make that you will always be surprise attacked
		+	*+16: Doesn't show exp screen at end.
		+	*+8: If you set this one up not exp will be gained at the end of battle (like in boss battles)
		+	*+4: Shows the timer. Like in dollet withdraw combats.
		+	*+2: Can't figure it out. Some boss battles have it enabled but don't know its function
		+	*+1: Can't escape.
		+
		+	In 0x04, 0x05, 0x06, and 0x07
		+	*+128: 1st enemy relative
		+	*+64: 2nd enemy relative
		+	*+32: 3rd enemy relative
		+	*+16: 4th enemy relative
		+	*+8: 5th enemy relative
		+	*+4: 6th enemy relative
		+	*+2: 7th enemy relative
		+	*+1: 8th enemy relative
		+
		+	An important note: If you put an enemy that "summons" another one (Ultimecia summoning Griever, Sphinxara summoning jelleye...) it will summon the enemy from certain slot. This means that if you put that enemy in another battle, it will still summon that slot, because (I think) that summoning is scripted in its AI (in c9m???.dat)