Underworld:Important Hex Addresses - Revision history

Tatters: /* Object Data */

2017-12-24T00:18:38Z

‎Object Data

Tatters: /* Type 2 Object Structure: (2 bytes) */

2017-12-24T00:14:35Z

‎Type 2 Object Structure: (2 bytes)

Tatters: /* Object Data */

2017-12-24T00:14:12Z

‎Object Data

Tatters: /* Push Block Data */

2017-12-23T23:34:09Z

‎Push Block Data

Tatters: /* Chest Contents */

2017-12-23T23:25:34Z

‎Chest Contents

Tatters at 23:25, 23 December 2017

2017-12-23T23:25:03Z

Tatters: /* (Inter Room) Torch Data */

2017-12-23T23:16:17Z

‎(Inter Room) Torch Data

Tatters: /* (Inter Room) Torch Data */

2017-12-23T23:14:54Z

‎(Inter Room) Torch Data

Tatters: /* Chest Contents */

2017-12-23T23:08:27Z

‎Chest Contents

Tatters at 22:11, 23 December 2017

2017-12-23T22:11:01Z

Show changes

@@ Line 78: / Line 78: @@
 ===Object Data===
-====Data location====
+{{box|[[Underworld:Important Hex Addresses/Object Data|Object data]]}}
 ===Dungeon Secrets Data===

@@ Line 188: / Line 188: @@
 |warp door?
 |}
 ===Dungeon Secrets Data===

@@ Line 78: / Line 78: @@
 ===Object Data===
 * {{$|0F8000}} to {{$|0F83BF}} = Pointer Table, 3 byte long addresses, indexed by room ID.
 * {{$|01EBA0}} to {{$|01FFF4}} = Data
 * {{$|050000}} to {{$|053729}} = Data
 * {{$|0F8780}} to {{$|0FFF4D}} = Data
 * Byte 0: {{red|aaaa}} {{blue|bbbb}}.
 **The a bits are transformed to {{red|aaaa}}{{hex|0000}} and select the type of empty space to fill in. Hyrule Magic calls this 'Floor 1' - Gets stored to {{$|7E0490}}
@@ Line 96: / Line 96: @@
 After that the bytes come in {{hex|3}} or {{hex|2}} byte object structures, used by routine {{$|01:88E4}}. Objects are loaded until an object with value {{0x|FFFF}} occurs. If a value {{0x|FFF0}} is loaded, the game will start loading Type 2 objects and will not go back to loading Type 1 objects until it is time to load the next layer. (Layer as in HM, not to be confused with the SNES' Backgrounds.) A value of {{0x|FFFF}} will also terminate the loading of Type 2 objects. The routine immediately terminates if that happens during the loading of either object type.
-Type 1 Object structure: (3 bytes):
+=====Type 1 Object structure: (3 bytes)=====
 * Byte {{hex|3}}: Routine to use. If this byte is ≥ {{0x|F8}} and < {{0x|FC}}, then it is a subtype 3 object. If the index is ≥ {{hex|FC}}, it is a subtype 2 object. If not, it is a subtype 1 object.
@@ Line 109: / Line 109: @@
 Use Byte {{hex|3}} * 2 as an index into the table at {{$|8200}}. This is the routine that is used to draw and otherwise handle the object. Subtype 1 objects have a maximum width and height of 4. Width and height are measured in terms of 32 {{x}} 32 pixels. (⟸ last part is questionable)
-*Subtype 2 Objects, 1st, 2nd, & 3rd bytes:
+======Subtype 2 Objects, 1st, 2nd, & 3rd bytes======
 ** Byte {{hex|3}}: {{white|ff}}{{purple|dd dddd}}
 ** Byte {{hex|2}}:  {{pink|eeee}} {{green|cccc}}
@@ Line 118: / Line 118: @@
 Might I add this is one messed up format? The {{purple|d}} bits are used as an index into the table at {{$|8470}}. Since such indices are going to be even, the {{purple|d}} bits are transformed into: {{hex|0000 0000 0}}{{purple|ddd ddd}}{{hex|0}}.
-*Subtype 3 Objects
+======Subtype 3 Objects======
 **Similar to Subtype 1, with a few small exceptions.
 **The vram address is calculated the same way. However, {{$|B2}} and {{$|B4}} are not used as length or width dimensions here. The routine that is used is determined as follows:
@@ Line 124: / Line 124: @@
 **Also, this value indexes into {{$|85F0}} instead of {{$|8200}}.
-Type 2 Object Structure: (2 bytes)
+=====Type 2 Object Structure: (2 bytes)=====
 *High Byte: {{green|cccc cccc}}
 *Low Byte: {{blue|bbbb}} {{purple|dd}}{{red|aa}}

@@ Line 201: / Line 201: @@
 ===Push Block Data===
-* {{$|0271DE}} to {{$|027369}} = Data
+The block data has three primary pointer locations. The pointer is stored as a long address.
 <Blockquote>
 bytes per entry:

@@ Line 257: / Line 257: @@
 !USA
 !JP
-!G
+!GER
 |-
 |{{0x|EBF6}}

@@ Line 218: / Line 218: @@
 !USA
 !JP
-!G
+!GER
 |-
 |{{0x|15B16}}, {{0x|15B1D}}, {{0x|15B24}}
@@ Line 244: / Line 244: @@
 !USA
 !JP
-!G
+!GER
 |-
 |{{0x|EBFB}}, {{0x|EC0A}}, {{0x|EC10}}

@@ Line 225: / Line 225: @@
 |}
-* In the USA version, the data goes from {{$|02736A}} to {{$|027489}}.
+* In the USA version, the data goes from {{0x|2736A}} to {{0x|27489}}.
 <Blockquote>
 Consists of variable length segments consisting of:

@@ Line 212: / Line 212: @@
 ===(Inter Room) Torch Data===
-* {{$|02736A}} to {{$|027489}} = Data
+The torch data has three primary pointer locations. The pointers are stored as a long address.
 <Blockquote>
 Consists of variable length segments consisting of:

@@ Line 225: / Line 225: @@
 ===Chest Contents===
-*{{$|00E96E}} to {{$|00EB65}} = Data
+The chest contents have three primary pointer locations. The values at each location point to the same pointer. Yes, you read that right. The pointer is stored as a long address.
 <blockquote>
 Array of chest information in 3 byte chunks. 168 entries in all ({{0x|A8}})