Ultimate Amiga

Games Corner => The Crypt of Bloodwych => Bloodwych Editors and Modifications => Topic started by: Hungry Horace on January 23, 2011, 10:12:15 PM

Title: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:12:15 PM

Hacking : General Overview

The intention of this section is to provide a reference for all the information known about the Bloodwych data structure.

I have attempted to compile as much knowledge about how the game binary can be modified and where possible show where this data is  shared within save games. It is my hope, that with this, more life can be breathed into the game and I have the goal of hopefully one day creating a completely new set of dungeons for Bloodwych.


This research has all been done using the Amiga version of the game, although where known, reference will be made to where data is shared between other 16-bit versions (PC and Atari) , and is in no way complete.

Where reference to memory locations is given, ($EAD4) will represent a memory location, which (unless stated) is the location in the memory of an Amiga 500 512k with kickstart 1.3 booting from the Bloodwych_103.ipf SPS release. BloodwychDataDisksVol.1 _43 is used for the Extended Levels.

A location given as [$656] refers to the location of the data within the Bloodwych binary itself, found in the 'c/' folder of the original disk.

Bloodwych is referred to as BW for short-hand, and The Extended Levels Volume 1 is referred to as BEXT .

The game binaries are here; BLOODWYCH  BEXT


The resource is broken down into the following sections;

      Map-Data Structure (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39942.html#msg39942)
          Map-Location Data - (0) Spaces (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39944.html#msg39944)
          Map-Location Data - (1) Stone Walls (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39945.html#msg39945)
          Map-Location Data - (2) Wooden Walls (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39946.html#msg39946)
          Map-Location Data - (3) Misc. (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39947.html#msg39947)
          Map-Location Data - (4) Stairs (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39948.html#msg39948)
          Map-Location Data - (5) Metal Doors (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39949.html#msg39949)
          Map-Location Data - (6) Pads, Triggers & Holes (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39950.html#msg39950)
          Map-Location Data - (7) Magic Locations (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39951.html#msg39951)

      Map-Location Data Table (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39943.html#msg39943)
      Pad / Floor Traps & Triggers  (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39952.html#msg39952)
      Switches (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39953.html#msg39953)  
      Teleportation Gems (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg3995$.html#msg39954)
      Tower Entrance / Exit Locations (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39955.html#msg39955)
      Wall Scrolls (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39956.html#msg39956)

      Object Data Structure (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39957.html#msg39957)
      BW Object Lookup Table (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39958.html#msg39958)
      BEXT Object Lookup Table
 (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39959.html#msg39959)
      Monster Data Structure (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39960.html#msg39960)
      Monster Lookup Table (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39961.html#msg39961)

      BW Champion Data Structure (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39962.html#msg39962)
      BEXT Champion Data Structure (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39963.html#msg39963)
      BW Pockets Data Structure (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39964.html#msg39964)
      BEXT Pockets Data Structure (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39965.html#msg39965)

      Menu Layout (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39966.html#msg39966)
      Keyboard Controls (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39967.html#msg39967)

      Joystick / Mouse Control (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39968.html#msg39968)
      Quickstart Defaults (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39969.html#msg39969)
      Keyboard Reading Routines (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39970.html#msg39970)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:22:04 PM

Hacking : Map-Data Structure

The main structure of a the BW map data, is contained with a $1000 byte block for each Tower or Dungeon.

In the PC version of the game, this is found as a self contained .map file.

In the Amiga and ST versions, these blocks are found at various offsets in the BW game binary - see Data Locations below.


Data Definition:

Each block contains $38 bytes of 'header' data, giving information about the layout of the Tower / Dungeon, this is then followed by $FC8 bytes of data containing the map data itself.

$00-$07 : contain the Width values of the respective Floors of the the Tower, starting with the lowest floor.
$08-$0F : contain the Height values of the respective Floors of the the Tower, starting with the lowest floor.

$10-$1F : are used to contain the offset values of the respective Floors of the the Tower, starting with the lowest floor - these are equivalent to the offset values used to assign the position of objects within a map (see: Object Data Structure (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39957.html#msg39957))

$20-$27 : contain the X-alignment values in relation to each other floor,  for each of the respective Floors of the the Tower, starting with the lowest floor.
$28-$2F : contain the Y-alignment values in relation to each other floor,  for each of the respective Floors of the the Tower, starting with the lowest floor.

$30-31 : contains the width of one specifically specified floor for each tower - the relevance of this is unknown.
$32-33 : contains the height of one specifically specified floor for each tower. (as above)
$34-35 : contains the offset value of one specifically specified floor for each tower. (as above)

$36-37 : contains the number of the top floor of the tower.

$38-$0FFF : contain the map data for the tower.


Data Locations: (Amiga - IPF: 102)

[$0EC7C]    The Keep    
[$1007E]    Serpent Tower    
[$11480]    Moon Tower    
[$12882]    Dragon Tower    
[$13C84]    Chaos Tower    
[$15086]    Zendicks Tower


Example Data: The Keep

0C 15 0F 1F 13 04 00 00  <<< Widths of Floors 0-7
01 15 0F 1F 13 05 00 00  <<< Heights of Floors 0-7

00 00  << offset at which floor 0 begins
00 18  << offset at which floor 1 begins
03 8A  << offset at which floor 2 begins
05 4C  << offset at which floor 3 begins
0C CE  << offset at which floor 4 begins
0F A0  << offset at which floor 5 begins
0F C8  << offset at which floor 6 begins (although there is no floor 6 in the Keep)
00 00  << offset at which floor 7 begins

08 05 08 00 06 0B 00 00 <<< X offsets of Floors 0-7
05 05 08 00 06 0C 00 00 <<< Y offsets of Floors 0-7

00 15 00 15                   <<<< Width / Height of "special" floor (floor 1 for the keep)
00 18                             <<< offset at which "special" floor begins (floor 1 for the keep)

00 05                             <<<  Number of Top Floor

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:27:02 PM

Hacking : Map-Location Data Table


Stored as two bytes (word) per map-location; AB CD

Value for D represents one of the following map types:

          0 - Spaces (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39944.html#msg39944)
          1 - Stone Walls (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39945.html#msg39945)
          2 - Wooden Walls (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39946.html#msg39946)
          3 - Misc. (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39947.html#msg39947)
          4 - Stairs (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39948.html#msg39948)
          5 - Metal Doors (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39949.html#msg39949)
          6 - Pads, Triggers & Holes (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39950.html#msg39950)
          7 - Magic Locations (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39951.html#msg39951)

C is usually used for "generic" detail (such as N/E/S/W rotation) for wall-types which fill the space.
For map-data which is not "occupied" (e.g wood walls, trigger pads etc) , a more generic system is used for C which defines any other occupancy in that location. This can be found in the sub-section regarding 'Spaces'.

 AB are used to define the detail of the map-data. This would be such as, colours of gems used, types of doors and locks etc.

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:28:34 PM

Hacking : Map-Location Data - (0) Spaces

Spaces are identified within the map data, in the second byte within the location's map data word (AB CD), whereby the final digit (D) is equal to '0'.

please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:29:23 PM

Hacking : Map-Location Data - (1) Stone Walls

Stone Walls are identified within the map data, in the second byte within the location's map data word (AB CD), whereby the final digit (D) is equal to '1'.

To best understand the definition of each wall, it is best to translate the two bytes (AB) and (CD) to binary, and consider which binary bits (right to left) contain defining information.


The Type of Wall

Bit 7 of the (CD) byte is used to determine that the wall is not 'plain' - i.e. contains a Shelf / Sign / Switch or Gem Hole, and is switched 'on' or 'off' for this purpose.

Bits 0-1 of the (AB) byte are used to allocate the wall a number from 0-3.
This number will define the type of wall in occurrence. A plain wall will use a zero here.
    0 = Shelf
    1 = Sign
    2 = Switch
    3 = Socket (Crystal/Gem Hole)


The Direction of the Wall

Any wall which is not plain, i.e. with Bit 7 of (CD) set, can face in one direction only, N/E/S/W.
Bits 4-5  of the (CD) byte,stores a 0-3 value number, which translates to the direction; N/E/S/W.


Shelves

Where a wall has been designated a shelf, there is only one parameter available.

Bit 3 of the (CD) byte, if set, will designated the shelf as "Concealed", as in how it is becomes after the use of the Conceal spell. No shelves in the original games begin in this state.

All other values are redundant.


Signs

For all wall signs, including wall Scrolls, additional information which will define the appearance of the scroll is contained with Bits 2-7 of (AB). These bits can be converted to a number, from 0-63, which will act as a reference.

Where a sign has a '0' reference value, a seeded colour sign, determined by the game itself, will be placed.

Where a sign has a reference value greater than or equal to 5, the sign will be of the 'wall text' type, and will directly link to a numbered scroll from the scroll data block. Note that the 'starting reference' (i.e. wall scroll number 1) will refer to a different section of text within the Wall Scroll Data, depending on the Tower.

The text which is linked to this particular reference number, including it's layout, is defined in a separate data-block. For information on this see: Wall Scrolls (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39956.html#msg39956)

The value defined by bits 2-7 of (AB) therefore, produces the following signs;

   0 = 'generated colour'
   1 = Serpent Sign
   2 = Dragon Sign
   3 = Moon Sign
   4 = Chaos Sign
   5-63 = Wall Scroll Sign, with reference number (value minus 5)


Switches

Where wall data is defined as a 'switch', used to trigger some other in-game event, such as the removal of another wall, there are two parameters available.

Bit 2 of the (AB) byte will determine if the switch is 'lit' or 'dim' - the 'on' value determines the switch as being dim (assume used)

Bits 3-7 of (AB) assigns the switch to a pre-defined function  These bits can be converted to a number, from 0-31, which will act as a reference to the action performed by the switch.

The action performed by the Switch / Trigger;

The action performed by this reference number is defined in a separate data-block. For information on this see: Wall Switch (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39953.html#msg39953)



Sockets (Gem / Crystal Holes)

Where wall data is defined as a 'socket', for teleportation gems, or crystals, there are two parameters available.

Bit 2 of the (AB) byte will determine if the socket is 'full' or 'empty' - the 'on' value determines the socket as being empty.

Bits 3-5 of (AB) assigns the socket to a particular type / colour. These bits can be converted to a number, from 0-7, which will determine this as follows;

   0 = Serpent Crystal
   1 = Chaos Crystal
   2 = Dragon Crystal
   3 = Moon Crystal
   4 = Grey *
   5 = Bluish
   6 = Brown *
   7 = Tan

It should be noted that the Grey and Brown gems do not appear in the game, and do not appear to operate.

The Bluish and Tan gems act as teleports, and for each tower use two location references (x/y coordinates) between which to jump. There is no 'floor' coordinate specified, and as such teleports will operate across the same floor only.

The locations specified for each pair of teleportation gems in each tower is defined in a separate data-block. For information on this see: Teleportation Gems (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg3995$.html#msg39954)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:29:43 PM

Hacking : Map-Location Data - (2) Wooden Walls

Wooden Walls and Doors are identified within the map data, in the second byte within the location's map data word (AB CD), whereby the final digit (D) is equal to '2'.

To understand this data block, it is necessary to translate the map data word (AB CD) into a wall-data parameter by taking the first byte (AB) alone.

The value of (AB) should then be split into 4 items of data, which are read in "base 4". However, it is much easier to look at this data in Binary (base 2) in order to break it down and translate it.

So, any given number for (AB) should be represented as an 8 bit binary value, and spaced into 4 blocks, each of which represent the possible wooden walls in the North, East, South and West directions of the floor-space.

Bits 0/1 define what is present in the "north" of the location.
Bits 2/3 define what is present in the "east" of the location.
Bits 4/5 define what is present in the "south" of the location.
Bits 6/7 define what is present in the "west" of the location.


Each N/E/S/W location can then be defined as one of 4 possibilities;

00 = No wall or Door Present.
01 = Wooden Wall
10 = Wooden Door (open)
11 = Wooden Door (closed)

The status of a wooden door, as to whether or not it is locked, is defined bit 0 of the (C) parameter of the map-data. If the bit is set (i.e. true) then all wooden doors within this location are locked with a common key.

Because all doors in the location are locked by setting a single bit, there is no data within the original game maps which defines two wooden doors from a single piece of map data. Adjacent doors are always defined on separate map-data entries.


Example Data

Map-Data value $00 02  = %00 00 00 00   =  No walls / doors defined
Map-Data value $41 02 = %01 00 00 01   =  Wall to the North, Wall to the West
Map-Data value $0C 12  = %00 10 11 00   =  Closed door to the East, Locked.


Location Occupancy

The value of C determines the current occupancy of this location, as previously defined in: Map-Location Data - (0) Spaces (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39944.html#msg39944)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:30:20 PM

Hacking : Map-Location Data - (3) Misc.

Two miscellaneous items are identified within the map data, in the second byte within the location's map data word (AB CD), whereby the final digit (D) is equal to '3'.

The byte (AB) defines this map-data as one of two items;

00 = Bed
01 = Pillar

All other values for this byte produce the 'bed' graphic, but it is not known if they still function correctly as a bed in-game.

It should be noted that a bed is only visible from a maxium of 2 spaces away, and as such is always contained within a room of maxium width 3 (including the bed space) in the original map-data.

It should also be noted that the bed graphic does not rotate, and is therfore always 'contained' by surrounding walls (wood or stone) in the original game's map-data, in order that it can only be approached / viewed from one direction.


Location Occupancy

The value of C determines the current occupancy of this location, as previously defined in: Map-Location Data - (0) Spaces (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39944.html#msg39944)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:30:47 PM

Hacking : Map-Location Data - (4) Stairs

A staircase is identified within the map data, in the second byte within the location's map data word (AB CD), whereby the final digit (D) is equal to '4'.

To best understand the definition of the staircase, we can translate the two bytes (AB) and (CD) to binary, and consider which binary bits (right to left) contain defining information.

The type of Staircase

The type of staircase, is changeable between the 'up' type staircase, and the 'down' type stair case. This is defined in bit 0 of the (AB) byte. If the bit is 'off' the staircase goes upwards, and if the bit is 'on' the staircase goes downwards.


The Direction of the Staircase

A Staircase can face N/E/S/W,  and this is defined by bits 1-2 of the (AB) byte, which should be translated into a value from 0-3.

    0 = North
    1 = East
    2 = South
    3 = West


Additional Considerations

Although a staircase will appear the same regardless of it's direction set, it should be allocated the correct direction in order to ensure correct operation.

When leaving a floor by a staircase, the player is moved an additional space forward in the given direction. This therefore requires all maps to align staircases on each floor with one space between them in their operating direction.

As such, staircases are always surrounded by walls. If the space behind the staircase is not solid, it is possible to move backwards whilst standing on the staircase, and move into the unoccupied space. There is one occurrence of this in Bloodwych, on the staircase closest to the Chaos Tower entrance, within the Keep.


Location Occupancy

The value of C determines the current occupancy of this location, as previously defined in: Map-Location Data - (0) Spaces (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39944.html#msg39944)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:31:09 PM

Hacking : Map-Location Data - (5) Metal Doors

A Metal Door is identified within the map data, in the second byte within the location's map data word (AB CD), whereby the final digit (D) is equal to '5'.

To best understand the definition of the metal door, we can translate the two bytes (AB) and (CD) to binary, and consider which binary bits (right to left) contain defining information.


Open or Closed

Whether a door is currently open or closed, is defined in bit 0 of the (AB) byte. If the bit is 'off' the door is open, and if the bit is 'on' the door is closed.


The type of Metal Door

The type of Metal Door, is changeable between the ornate, decorated metal door and the portcullis style. This is defined in bit 1 of the (AB) byte. If the bit is 'off' the door is the decorated type, and if the bit is 'on' the door is of the Portcullis type.


The direction of the Metal Door

Whether a Metal Door is facing East/West or North/South is defined in bit 2 of the (AB) byte. If the bit is 'off' the door is facing North/South, and if the bit is 'on' the door is facing East/West.


Locked Doors

Metal Doors can be locked in a variety of ways. To lock a door in such a way that a Key or other unlocking method is required, it is required that bit 4 of the (CD) byte is switched to the 'on' position first.

Once a door is locked, the type of lock will be determined by bits 4-6 of the (AB) byte. These bits can be converted to a number, from 0-7, which will determine this as follows;

   0 = Magelock
   1 = Bronze lock
   2 = Iron lock
   3 = Serpent lock
   4 = Chaos lock
   5 = Dragon lock
   6 = Moon lock
   7 = Chromatic lock


'Void' Locked Doors

Metal Doors can also be locked in a special way, depicted as a 'black' lock, which is only released via a switch / trigger. By setting bit 3 of byte (AB) to 'on' the door will be locked in this way.

Special consideration should be given to the 'general' lock setting when using void locks. In order to ensure that the door is correctly unlocked after activation of a trigger, the normal lock settings - i.e. bit 4 of the (CD) byte, should be set to 'off' and bits 4-6 of (AB) cleared.

It may be possible by leaving these standard locking options in place, and additionally including a void lock option, that once the void lock is 'cleared' by a trap/trigger, the door is left as a standard locked door. However, this is untested.


Location Occupancy

The value of C determines the current occupancy of this location, as previously defined in: Map-Location Data - (0) Spaces (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39944.html#msg39944)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:31:41 PM

Hacking : Map-Location Data - (6) Pads, Triggers & Holes

A Pad / Floor Trap or Trigger is identified within the map data, in the second byte within the location's map data word (AB CD), whereby the final digit (D) is equal to '6'.

To best understand the definition of each floor location, it is best to translate the two bytes (AB) and (CD) to binary, and consider which binary bits (right to left) contain defining information.


The Type of Floor Tile

Bits 0-1 of the (AB) byte are used to allocate the floor tile a number from 0-3.
This number will define the type of floor tile in occurrence.
    0 = Spell Fizzle
    1 = Floor Hole / Pit
    2 = Green Trigger Pad
    3 = Invisible Trigger Pad


Ceiling Hole / Pit Above

All floor locations have the option of having a hole in the ceiling at the location.
This is defined by bit 2 of the (AB) byte. If the bit is 'on' the hole in the ceiling will appear.


Spell Fizzle Zone

Where a location has been designated a Spell Fizzle area, there is only one parameter available, the appearance of a pit in the ceiling, as mentioned above.

All other values are redundant.


Floor Hole / Pit

Where a location has been designated a Floor Hole / Pit, there is only one parameter available, the appearance of a pit in the ceiling, as mentioned above.

All other values are redundant.


Trigger Pad

Where bit 1 of the (AB) byte is set, it is automatically designated a 'Trigger' pad, used to trigger some other in-game event, such as the removal of another wall, there are three parameters available.

By setting bit 0 of the (AB) byte, it will determine whether this 'Trigger' pad is visible (green) or invisible. The 'on' postion designates the pad as invisible.

The appearance of a pit in the ceiling can also be determined, as mentioned above, by setting bit 2 of the (AB) byte.

The remaining bits 3-7 of (AB) assigns the 'trigger' to a pre-defined function.  These bits can be converted to a number, from 0-31, which will act as a reference to the action performed by the switch.


The action performed by a Trap / Trigger

The action performed by this reference number is defined in a separate data-block. For information on this see: Pad / Floor Traps & Triggers (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39952.html#msg39952)



Location Occupancy

The value of C determines the current occupancy of this location, as previously defined in: Map-Location Data - (0) Spaces (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39944.html#msg39944)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:32:05 PM

Hacking : Map-Location Data - (7) Magic Locations


Location Occupancy

The value of C determines the current occupancy of this location, as previously defined in: Map-Location Data - (0) Spaces (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39944.html#msg39944)


please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:35:20 PM

Hacking : Pad / Floor Traps & Triggers

When the reference number of a Pad / Trigger has been allocated in the map data (see Map-Location Data - (6) Pads, Triggers & Holes) the "action" of that reference number is defined within a 128 byte block for each tower.

Each definition is 4 bytes long, following the below AA BB CC DD structure.

In some cases, these are universally set to the same special-case throughout the game, such as with the Vivifcation Machines in BW  (ref 4 & ref 5) and spinners.

Pad / Trigger Functions (AA)

00 - NONE
02 - SPIN 180 **
04 - SPIN RANDOM **
06 - OPEN VOID-LOCK DOOR (X/Y) *
08 - VIVIFY MACHINE EXTERNAL PAD **
0A - VIVIFY MACHINE INTERNAL PAD **
0C - WOOD DOOR CLOSER #1 (SPECIAL CASE) **
0E - WOOD DOOR CLOSER #2 (SPECIAL CASE) **
10 - TRADER DOOR **
12 - TOWER ENTRANCE (SIDE PAD) (X/Y OF OPPOSITE PAD)
14 - TOWER ENTRANCE (CENTRAL PAD)
16 - REMOVE (X/Y) *
18 - CLOSE VOID-LOCK DOOR (X/Y) *
1A - TOGGLE PILLAR (X/Y) *
1C - CREATE SPINNER (OR OTHER) (X/Y) *
1E - OPEN/CREATE WALL WITH SWITCHES? (X/Y) *
20 - CREATE PAD (F/X/Y)
22 - MOVE PILLAR AT PLAYER X,Y TO PLAYER X-1,Y-1 (SPECIAL CASE) **
24 - CREATE PILLAR (X/Y) *
26 - KEEP ENTRANCE (SIDE PAD) (X/Y OF OPPOSITE PAD)
28 - KEEP ENTRANCE (CENTRAL PAD)
2A - FLASH TELEPORT (F/X/Y)
2C - ROTATE STONE WALL (X/Y) *
2E - TOGGLE WALL (X/Y) *
30 - SPINNER (UNKNOWN DIFFERENCE) (X/Y) *
32 - CLICK TELEPORT (F/X/Y)
34 - TOGGLE GREEN PAD (X/Y) *
36 - ROTATE WOOD WALL COUNTER-CLOCKWISE (X/Y) *
38 - TOGGLE HOLE (X/Y) *
3A - GAME COMPLETION PAD **
3C - REMOVE PILLAR / OTHER EVENT (X/Y) **


Pad / Trigger Parameter (BB)
Functions marked * or ** use no parameter here

For Those marked (F/X/Y);
BB is the floor on which the action is taken.


Pad / Trigger Parameter (CC DD)
Functions marked ** use no parameter here

For Those marked (X/Y);
CC is the X coordinate at which the action is taken.
DD is the Y coordinate at which the action is taken.


Special Cases

Data Locations: (Amiga - IPF: 102)
($70D0)  [$6D66] The Keep
($7140)  [$6DE6] Serpent Tower
($71D0)  [$6E66] Moon Tower
($7240)  [$6EE6] Dragon Tower
($72D0)  [$6F66] Chaos Tower
($7340)  [$6FE6] Zendik's Tower

Example Data:  The Keep
00000000 - none
02000000 - special case - spin 180
04000000 - special case - spin random
06000E06 - ref 03 / 1B - open black-locked metal door @ x0E y06
08000000 - ref 04 / 23 - special case - vivify machine external
0A000000 - ref 05 / 2A - special case - vivify machine internal
0C000000 - ref 06 / 32 - special case - bluish gemhole wood doors closer @ (hardcoded x,y)
0E000000 - ref 07 / 3A - special case - tan gemhole wood doors closer @ (hardcoded x,y)
06001403 - ref 08 / 42 - open black-locked metal door @ x04 y03
10000000 - ref 09 / 4B - special case - trader door (closes Northwards wood door in location to the left)
12020A01 - ref 10 / 52 - serpent tower entrance left
14040000 - ref 11 / 5A - serpent tower entrance middle
12030801 - ref 12 / 62 - serpent tower entrance right
12040A11 - ref 13 - 6A - moon tower entrance right
14080000 - ref 14 - 72 - moon tower entrance middle
12050811 - ref 15 - 7A - moon tower entrance left
1206110A - ref 16 - 82 - dragon tower entrance right
140C0000 - ref 17 - 8A - dragon tower entrance middle
12071108 - ref 18 - 92 - dragon tower entrance left
1208010A - ref 19 - 9A - chaos tower entrance right
14100000 - ref 20 - A2 - chaos tower entrance middle
12090108 - ref 21 - AA - chaos tower entrance left
120A0103 - ref 22 - B2 - zendik tower entrance right
14140000 - ref 23 - BA - zendik tower entrance middle
120B0101 - ref 24 - C2 - zendik tower entrance left
16000002 - ref 25 / CB - remove pillar @ x00 y02
16000202 - ref 26 / D3 - remove pillar @ x02 y02
00000000 - unused
00000000 - unused
00000000 - unused
00000000 - unused
00000000 - unused

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:37:37 PM

Hacking : Wall Switches

When the reference number of a switch has been allocated in the map data (see Map-Location Data - (1) Stone Walls (http://www.ultimateamiga.co.uk/index.php/topic,8908.msg39945.html#msg39945)) the "action" of that reference number is defined within a 64 byte block for each tower.

Each definition is 4 bytes long, following the below AA BB CC DD structure.

Switch Functions (AA)

02 - REMOVE
04 - TOGGLE STONE WALL
06 - OPEN VOID-LOCK DOOR
08 - ROTATE BRICK WALL
0A - TOGGLE PILLAR
0C - PLACE PILLAR
0E - ROTATE WOOD WALLS

Switch Parameter (BB)
Always unused

Switch Parameter (CC DD)

CC is the X coordinate at which the action is taken.
DD is the Y coordinate at which the action is taken.

Because the floor is never specified as a parameter for any of the switch actions, switch functions can be cleverly re-used on multiple floors of a dungeon to increase the variety of of puzzles.

Data Locations: (Amiga - IPF: 102)

[$5860] The Keep
[$58A0] Serpent Tower
[$58E0] Moon Tower
[$5920] Dragon Tower
[$5960] Chaos Tower
[$59A0] Zendick's Tower


Example Data:  The Keep
00000000 - ref 0 - no action
02000108 - ref 1 - remove pillar @ x01 y08
02001101 - ref 2 - remove pillar @ x11 y01
02000607 - ref 3 - remove pillar @ x06 y07
0200020C - ref 4 - remove wall @ x02 y0C
02000109 - ref 5 - remove wall @ x01 y09
04000901 - ref 6 - toggle wall @ x09 y01
00000000 - ref 7 - no action
00000000 - ref 8 - no action
0200151E - ref 9 - remove @ x15 y1E
02000B08 - ref 10 - remove @ x0B y08
02000E02 - ref 11 - remove @ x0E y02
02000C04 - ref 12 - remove @ x0C y04
0200110C - ref 13 - remove @ x11 y0C
02001117 - ref 14  - remove @ x11 y17
00000000 - ref 15 - no action

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:40:05 PM

Hacking : Teleportation Gems

Data Definition:

The locations for the Tan & Bluish Gem teleports are stored in two consecutive 24 byte blocks.

Each gem has two locations for each tower, stored as a single X / Y coordinate. As a result, teleport Gems are only used on one floor for each tower in the original games, although it would be possible to be used on more than one floor, they would need to be located at the same X / Y coordinates on each floor.

The X / Y locations referred to are the location at which the player is standing when using the Gem. Transfer of the Gem item to the correct Wall-Socket is handled automatically.


Data Locations: (Amiga - IPF: 102)

Tan Gem: ($5B4C) [$57E2]
Bluish Gem: ($5B64) [$57FA]


Example Data: Tan Gem

01 00 - The Keep - Location 1
05 00 - The Keep - Location 2
11 11 - Serpent Tower - Location 1
07 02 - Serpent Tower - Location 2
09 12 - Moon Tower - Location 1
12 00 - Moon Tower - Location 2
0E 0D - Dragon Tower - Location 1
0B 03 - Dragon Tower - Location 2
0A 03 - Chaos Tower - Location 1
08 0C - Chaos Tower - Location 2
04 11 - Zendik's Tower - Location 1
0B 09 - Zendik's Tower - Location 2


Example Data: Bluish Gem

0C 0C - The Keep - Location 1
0B 0A - The Keep - Location 2
0C 0E - Serpent Tower - Location 1
04 03 - Serpent Tower - Location 2
0B 12 - Moon Tower - Location 1
02 00 - Moon Tower - Location 2
0C 0D - Dragon Tower - Location 1
09 03 - Dragon Tower - Location 2
0C 02 - Chaos Tower - Location 1
0C 11 - Chaos Tower - Location 2
00 11 - Zendik's Tower - Location 1
08 02 - Zendik's Tower - Location 2

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:41:49 PM

Hacking : Tower & Dungeon Entrances and Exits

Tower Entrance Locations

Located at ($7564) [$71FA] : 0000 0000 0107 0307 0101 0301 0101 0103 0701 0703 0607 0609

- 00 00 | 00 00 - not used
- 01 07 | 03 07 - Serpent Tower door pads
- 01 01 | 03 01 - Moon Tower door pads
- 01 01 | 01 03 - Dragon Tower door pads
- 07 01 | 07 03 - Chaos Tower door pads
- 06 07 | 06 09 - Zendik Tower door pads


Keep Entrances / Tower Exits

Located at ($7446) [$70DC] : 00 04 04 04 04 05

00 - not used
04 - Returning Floor from Serpent Tower
04 - Returning Floor from Moon Tower
04 - Returning Floor from Dragon Tower
04 - Returning Floor from Chaos Tower
05 - Returning Floor from Zendik's Tower


Located at ($744C) [$70E2] : 0801 0A01 0811 0A11 1108 110A 0108 010A 0101 0103

- 08 01 | 0A 01 - Return Pad Locations from Serpent Tower into The Keep
- 08 11 | 0A 11 - Return Pad Locations from Moon Tower into The Keep
- 11 08 | 11 0A - Return Pad Locations from Dragon Tower into The Keep
- 01 08 | 01 0A - Return Pad Locations from Chaos Tower into The Keep
- 01 01 | 01 03 - Return Pad Locations from Zendik's Tower into The Keep

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:43:59 PM

Hacking : Wall Scrolls


please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:45:09 PM

Hacking : Object Data Structure

The data for the objects is stored according to its respective tower / dungeon, and is found at immediately following the map data, in a 1024 ($400) byte block. In the PC version, this is contained with the .ob files for each tower. There is an additional 2 bytes of data at the beginning to define the amount of object data used in the block.

These 1026 byte blocks, are found at the following locations;

[$0FC7C] The Keep
[$1107E] The Serpent Tower
[$12480] The Moon Tower
[$13882] The Dragon Tower
[$14C84] The Chaos Tower
[$16086] Zendik's Tower


The data for the objects is stored in such a way that there is no fixed length for each entry within the data table. This is to allow for only one entry when items are placed on top of one another in the same location.

The first two bytes of data represents the amount of data used for item-placements listed within the data table, and is then followed by the data itself.

In the case of the Keep [$FBBC] (PC: mod0.ob) this is a value of 03 3F.


This is then followed by a minimum of 5 bytes, with an additional 2 bytes added for each extra item in this location.


This can be represented as the following;

       AB CD EF GH IJ  ...  KL MN ... etc



A = The position of the items in the location (4 positions for a standard floor, and 2 positions for a shelf)

      This has one of four options;

00 - Position 1 - North West Space, North Facing Bottom Shelf,  West Facing Top Shelf
04 - Position 2 - North East Space, East Facing Bottom Shelf,  North Facing Top Shelf
08 - Position 3 - South West Space, West Facing Bottom Shelf,  South Facing Top Shelf
12 - Position 4 - South East Space, South Facing Bottom Shelf,  East Facing Top Shelf


BCD = The index number for the location.

       This is not a standard x,y,z coordinate reference, but a number which represents the location according to where it is within the entire map data of the tower / dungeon. This should be taken as an index number, as if the marker is found by "counting through" the map locations. This means that a value of 0 00 would represent the first floor location at coordinate 0,0 on the 0 (bottom) floor of a tower. Moving along to 0,1 would be represented by the index number 0 01 and so on.

EF = The number of items in the given location, minus 1.

       Where there is only one item stored in the location, this has a value of 00. Where there are two items, a value of 01 and so on. This is an important piece of information as with no "termination" byte, it is this which is used to tell us how many bytes of data will need to be read for the object data for this location.

GH - This is the object code for the first item in the location. This is a representation of the item, based on the object lookup table, which will need to be referenced in order to determine which items are in the location.

IJ - This is the number of item GH to be "stacked" at this point. Whilst this is commonly used for Coinage and Common Keys, which are usually place in multiple numbers, this can also be used to stack multiple numbers of any item, to a maximum number of 255.

KL - This is identical to GH, in those situations where EF is greater than zero. It gives the object code for the next item stored at a given location.

LM - Again, this is identical to IJ, in those situations where EF is greater than zero, and gives the number of the item represented bu KL to be stored at the location.



In order to aid the understanding of the object data structure, here is an example piece of code, from the first item stored for the Keep.

        C8 0E 00 07 01

This data would represent:
     1 item on the location (00 on EF.)
     1 (01 on IJ)  x Apple (07 on GH)  at index postion 8 0E (8 OE on B CD), in the C position (C on A.)


The next set of data in the list is:

         88 0E 00 07 01

This data would represent;
    1 item on the location.
    1 x Apple  at index position 8 0E, in the 8 position of the location.


And skipping through to the fourth piece of data we see the following;

         88 8E 02 50 01 30 01 02 05

Which represents;
    3 items on the location
    1 x Bronze Key , 1 x Dagger, 5 x Common Keys  at index position 8 8E in the 8 position of the location.

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:46:36 PM

Hacking : Bloodwych Object Lookup Table

Objects in Bloodwych are represented by the following codes, in bother the Character Inventory and in the Object Data Blocks for each Dungeon:

01   Coinage
02   Common Keys
03   Arrows
04   Elf Arrows
05   1/3 Apple
06   2/3 Apple
07   Apple
08   1/3 Biscuit
09   2/3 Biscuit
0A   Biscuit
0B   1/3 Chicken
0C   2/3 Chicken
0D   Chicken
0E   1/3 Mead
0F   2/3 Mead
10   Mead
11   1/3 Water
12   2/3 Water
13   Water
14   N'egg (Green)
15   N'egg (Blue)
16   N'egg (Red)
17   Serpent Slime
18   Brimstone Broth
19   Dragon Ale
1A   Moon Elixir
1B   Leather Armour
1C   Chain Mail
1D   Plate Mail
1E   Mithril Chain
1F   Mithril Plate
20   Adamant Chain
21   Adamant Plate
22   Crystal Chain
23   Crystal Plate
24   Leather Shield
25   Buckler
26   Rune Shield (Classic)
27   Large Shield
28   Moon Shield
29   Dragon Scale
2A   War Shield
2B   Chaos Gloves
2C   Battle Gloves
2D   Mithril Gloves
2E   Adamant Gloves
2F   Crystal Gloves
30   Dagger
31   Stealth Blade
32   Short Sword
33   Long Sword
34   Mithril Sword
35   Fleshbane
36   Demon Blade
37   Ace of Swords
38   Battle Axe
39   Mithril Axe
3A   Troll's Axe
3B   Brainbiter
3C   Deathbringer
3D   Staff
3E   Battle Staff
3F   Power Stadd
40   Blodwyn (RIP)
41   Murlock (RIP)
42   Eleanor (RIP)
43   Roseanne (RIP)
44   Astroth (RIP)
45   Zothen (RIP)
46   Baldrick (RIP)
47   Elfric (RIP)
48   Sir Edward (RIP)
49   Megrim (RIP)
4A   Sethra (RIP)
4B   Mr. Flay (RIP)
4C   Ulrich (RIP)
4D   Zastaph (RIP)
4E   Hengist (RIP)
4F   Thai-Chang (RIP)
50   Bronze Key
51   Iron Key
52   Serpent Key
53   Chaos Key
54   Dragon Key
55   Moon Key
56   Chromatic Key
57   Serpent Wand
58   Chaos Wand
59   Dragon Wand
5A   Moon Wand
5B   Heal Wand
5C   Long Bow
5D   Frost Bow
5E   Cross Bow
5F   permit
60   Serpent Crystal
61   Chaos Crystal
62   Dragon Crystal
63   Moon Crystal
64   Grey Gem
65   Bluish Gem
66   Brown Gem
67   Tan Gem
68   Grey Ring
69   Serpent Ring
6A   Chaos Ring
6B   Dragon Ring
6C   Moon Ring
6D   Book of Skulls

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:47:24 PM

Hacking : Bloodwych : Extended Levels Object Lookup Table

Objects in Bloodwych : Extended Levels are represented by the following codes, in bother the Character Inventory and in the Object Data Blocks for each Dungeon:

01   Coinage
02   Common Keys
03   Arrows
04   Elf Arrows
05   1/3 Apple
06   2/3 Apple
07   Apple
08   1/3 Biscuit
09   2/3 Biscuit
0A   Biscuit
0B   1/3 Chicken
0C   2/3 Chicken
0D   Chicken
0E   1/3 Mead
0F   2/3 Mead
10   Mead
11   1/3 Water
12   2/3 Water
13   Water
14   N'egg (Green)
15   N'egg (Blue)
16   N'egg (Red)
17   Serpent Slime
18   Brimstone Broth
19   Dragon Ale
1A   Moon Elixir
1B   Leather Armour
1C   Chain Mail
1D   Plate Mail
1E   Mithril Chain
1F   Mithril Plate
20   Adamant Chain
21   Adamant Plate
22   Crystal Chain
23   Crystal Plate
24   Rune Shield (Red)
25   Rune Shield (Green)
26   Rune Shield (Black)
27   War Shield
28   Demon Scale
29   Battle Soul
2A   Chromatic Plate
2B   Chaos Gloves
2C   Battle Gloves
2D   Mithril Gloves
2E   Adamant Gloves
2F   Crystal Gloves
30   Dagger
31   Stealth Blade
32   Adamant Sword
33   Fleshbane
34   Demon Blade
35   Rune Sword
36   Soul Sucker
37   Ace of Swords
38   Adamant Axe
39   Ogre's Axe
3A   Deathbringer
3B   Dragon Axe
3C   Grey Axe
3D   Staff
3E   Battle Staff
3F   Power Stadd
40   Blodwyn (RIP)
41   Murlock (RIP)
42   Eleanor (RIP)
43   Roseanne (RIP)
44   Astroth (RIP)
45   Zothen (RIP)
46   Baldrick (RIP)
47   Elfric (RIP)
48   Sir Edward (RIP)
49   Megrim (RIP)
4A   Sethra (RIP)
4B   Mr. Flay (RIP)
4C   Ulrich (RIP)
4D   Zastaph (RIP)
4E   Hengist (RIP)
4F   Thai-Chang (RIP)
50   Bronze Key
51   Iron Key
52   Serpent Key
53   Chaos Key
54   Dragon Key
55   Moon Key
56   Chromatic Key
57   Serpent Wand
58   Chaos Wand
59   Dragon Wand
5A   Moon Wand
5B   Heal Wand
5C   Long Bow
5D   Frost Bow
5E   Cross Bow
5F   Permit
60   Serpent Crystal
61   Chaos Crystal
62   Dragon Crystal
63   Moon Crystal
64   Grey Gem
65   Bluish Gem
66   Brown Gem
67   Tan Gem
68   Grey Ring
69   Serpent Ring
6A   Chaos Ring
6B   Dragon Ring
6C   Moon Ring
6D   Book of Skulls

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:48:25 PM

Hacking : Monster Data Structure


In the game binary, information about the monsters is stored in batch by tower, in a 'packed' form.

This is then unpacked to a larger memory space on entering each Tower/Game Start.

Monsters that have not been killed are then returned to the 'packed' form on exiting the tower. This has the effect of reseting some monster statistics (such as monster hit points)

There are 6 digits in BW which mark the number of monsters per tower at [$171F4]


As raw data these can be found as:

                00 48 00 4D 00 53 00 43 00 4F 00 4D


This is followed by 300 byte blocks, each containing the detailed information about the monsters, at the following locations;

                [$17200] The Keep
                [$17500] The Serpent Tower
                [$17800] The Moon Tower
                [$17B00] The Dragon Tower
                [$17E00] The Chaos Tower
                [$18100] Zendik's Tower


At these locations, you find the monster data stored in 6 byte blocks.

As an example. the following shows you the data for the first 8 monsters in The Keep.

                04 0B 0F 00 15 FF
                04 16 1A 00 16 FF
                05 02 00 04 15 FF
                04 0F 0F 00 2F FF
                14 03 09 00 11 FF
                04 06 00 01 14 FF
                04 06 01 00 14 FF
                04 06 03 01 14 FF


By breaking this down by byte we can begin to understand what this data represents;

                AB CD EF GH IJ KL


A = Type of Monster
   
     This can be one of three values;
     0 - Normal Fighting Monster
     1 - Spell-casting Monster
     3 - Arc Bolt Machine

B - The number of the tower floor on which the monster starts.

CD - The X-coordinate postiioning of the tower floor on which the monster starts.

However, if between two and four monsters are to start in the same location (teamed) this number is left void and given a value of FF on the second to fourth team-members.

EF - The Y-coordinate positioning of the tower floor on which the monster starts.

GH - The level of the monster. This determines the monsters strength, speed, available spells, and for non-humanoid monsters also the colour of the monster.

In the Extended Levels Vol.1 this also acts as a seed number to help generate the monster's name

IJ - This is the form / look of the monster. This number represents those given in the monster lookup table.

KL - This is the rather unusual "team-data" number. In the majority of cases this is left blank with the value of FF.
However, when two monsters are to begin the game "teamed" with the same starting postion, this value simple increases from 00 and beyond, for every teamed-monster.

For example, two monsters both placed at X04 Y06 would have the team-data values of 00 and 01 respectively, and this would continue with the next two teamed monsters in the list having the values of 02 and 03.



This picture shows the data represented in the beta version of the Amiga Bloodwych Editor:

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:48:57 PM

Hacking : Monster Lookup Table


please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:49:33 PM

Hacking : Bloodwych Champion Data Structure

The champion data block gives us lots of information regarding our live Champion information. There are 16 ($10) entries here, each of length $20.

The champions are listed in the following order:

- Blodwyn
- Murlock
- Eleanor
- Roseanne

- Astroth
- Zothen
- Baldrick
- Elfric

- Sir Edward
- Megrim
- Sethra
- Mr. Flay

- Ulrich
- Zastaph
- Hengist
- Thai Chang

Bloodwyn Stats - SPS102 addresses
File Location: [$E866] - Bloodwyn Stats
Memory Location: ($EB2A - tbc)
 
($EBD0  = tbc?)


Bloodwyn Stats - SPS439 addresses
File Location: [$E7A6] - Bloodwyn Stats
Memory Location: ($ - tbc)

Example Data:
01 23 11 0D 0D 23 23 1F 1F 06 09 05 80 00 00 00
C7 FF 00 00 00 00 07 09 02 00 03 00 00 00 00 00

Detail:
Each byte of data sets out differing information for the champion, defined as follows:

-   Byte 00 = Character Level
-   Byte 01 = Strength
-   Byte 02 = Agility
-   Byte 03 = Intelligence
-   Byte 04 = Charisma
-   Byte 05 = Current HP
-   Byte 06 = Max HP
-   Byte 07 = Current Vitality
-   Byte 08 = Max Vitality
-   Byte 09 = Current Spell Points
-   Byte 0A = Max Spell Points
-   Byte 0B = Armour Level
-   Byte 0C = Spells Page 1 (one bit per spell)
-   Byte 0D = Spells Page 2
-   Byte 0E = Spells Page 3
-   Byte 0F = Spells Page 4
-   Byte 10 = Food Level (max C7)
-   Byte 11 = Current Worn Spell (08 = Amour etc..)
-   Byte 12 = Current Worn Hand Amour
-   Byte 13 = Related to spell (Unsure how)
-   Byte 14 = Related to spell cost (Unsure how)
-   Byte 15 = Spell Cool Down Timer
-   Byte 16 = X position
-   Byte 17 = Y Position
-   Byte 18 = bits 4-5 (left) Floor position  |  bits 0-1 (right) direction faced
-   Byte 19 = Character speed
-   Byte 1A = Floor
-   Byte 1B = Attack cool down (counts down from 07 to 00, also used for attack sequence)
-   Byte 1C = Levelling Value (change to FF to level, 11 = level 1, 24 = level 2)
-   Byte 1D = XP to next level (Starts at 255 and then as you hit monsters this is reduced down to 00 and Byte 1C is changed to FF)
-   Byte 1E = Amount of spells to buy from the fairy
-   Byte 1F = ?

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:49:53 PM

Hacking : Bloodwych : Extended Levels Champion Data Structure

$F586 - Bloodwyn Stats - 4 lines in BEXT, followed by other 15 champions or recruited monster. (tbc)



please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:50:13 PM

Hacking : Bloodwych Pockets Data Structure

$ED2A - Blodwyn Pocket contents (tbc)



please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:50:43 PM

Hacking : Bloodwych : Extended Levels Pockets Data Structure


please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:51:16 PM

Hacking : Menu Layout


please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:51:48 PM

Hacking : Keyboard Controls


It is possible to modify some of the Keyboard functions of Bloodwych fairly easily.


Starting with the very basics, the following is the code for the player 1 and player 2 keyboard controls for movement;

5F 46 4E 4F 4D 4C      12 10 22 20 21 11

This can be found in BW at ($0656) [$02EC] - or can be searched for manually.


These hex numbers represent the keycodes for :

Help - Del - Cursor Right - Cursor Left - Cursor Down - Cursor Up - E - Q - D - A - S - W

and can be substituted for alternative keycodes if wanted, in order to change the in-game keys.



It is also possible to change the operation of the key-controls for the main menu, but this is discussed seperately in the Menu Layout section of this resource.

For reference, the Amiga keycodes are laid out as such;

(http://www.ultimateamiga.co.uk/HostedProjects/GamesCorner/TheCryptOfBloodwych/Images/Editor/KeyRaw.gif)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:53:07 PM

Hacking : Mouse and Joystick Controls


please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:53:38 PM

Hacking : Quickstart Defaults

please await post update or comment on this topic in: The Open Contribution Thread (http://www.ultimateamiga.co.uk/index.php/topic,8806.0.html)

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on January 23, 2011, 10:54:15 PM

Hacking : Keyboard Reading Routines

The keyboard routine starts at $5D6
The game reads the keyboard and stores the result at memory location $5D1 where it is read in later.

- it loads $bfe001 into reg a0
- it then does a move.b ($c00,a0),d0
- which basically does move.b $c00+$bfe001,d0
- This is equivalent to move.b $bfec01,d0
- which moves the raw keycode into d0

Code: [Select]

lea  $656,a0               ; Copy address into a0
moveq  #b,d1               ; For loop, checking 12 things
cmp.b  (a0)+,d0            ; check to see if the contents of mem location a0 are same as d0
                           ; and increment the address at a0 by 1 byte (first time a0 would change to $657)
beq  $063a                 ; If they match lets branch
dbf  d1,$630               ; decrease d1 by 1 and loop
rts                        ; return from routine

Title: Re: Hacking: A Guide to the Data-Structure of Bloodwych
Post by: Hungry Horace on June 28, 2015, 10:44:48 AM

Hacking : Graphics: Large Monsters

NOTE: ALL FILE OFFSETS ARE USING THE AMIGA BINARY FROM SPS436
ALL MEMORY LOCATIONS ARE HAVING LOADED THE AMIGA BINARY FROM SPS436


The intention of this section is to provide an understanding of how the larger non-humanoid monsters (crabs, dragons etc) are coloured within the game. This is defined by four particular items of data:


-The “Grade” Offset Value
-The “Grade” Limit
- The Master Monster Palette
- The "Grade" Colour Selections

Definition of "Grade"

The documentation will refer to a "grade" of each monster type - this is a unique colour for each monster type,  which changes with each higher level of the monster. This differs from a level because several levels (beyond the lower/upper bounds) will not result in a change of colour.


The Grade Offset Value

Each type of Monster has a unique value defined within the game code, to ensure the colour grades start at a particular level, and acting as a lower bound. E.g. if this value is set to "4"  then the first colour-grade occurs at Level 4, the second at level 5, the third as level 6. All values lower (1-3) will use the same first colour grade as a level 4 monster.

Default values are as follows;

Summon ($64/$65): TBC
Beholder ($66): TBC
Behemoth ($67): TBC
Crab ($68): TBC
Large Dragon ($69): TBC
Small Dragon ($6A): TBC


The “Grade” Limit

The grade 'limit' value is also contained directly within the game code, along with a 'maximum grade number' (equal to the limit value, minus 1) which the code re-sets the grade to.

These number determine the number of grades for *all* large monster types, as this is non-monster specific. By default, the game has 8 colour grades available for each monster, and a "reset" value of 7 is used. (Since 'zero' is classed as one of the 8 grades)

These value may be lowered without any problem, but if raised, will require the  "Grade" Colour Selections (see below) to be relocated, and changes made to the code which locates that data.

The locations of the necessary instructions containing this single-byte value are given below, and the + value should be added if you wish to edit the single byte containing the value only.

Memory Location:
CMPI.B Instruction located at ($9EA0) + 3    (limit value)
File Location: [$9B1F]

Memory Location:
MOVEQ Instruction located at ($9EA6) + 1   (limit value minus 1)   
File Location: [$9B23]


The Master Monster Palettes:

The main monster palette is a list of colour-sets available to us. Each set is comprised of 4 palette numbers as bytes. There are 13 normally available, although the final value appears to be unused. For each monster type, 8 of these are selected. With each level raised for the monster, the next colour set is used. It should be noted that each monster has an ‘offset’ value however, so grading may not be started until a particular level is reached.

The colour-set “-1” is used to define an illusion, but is has to be address-seeked separately.


Regular Large Monsters

Memory Location:
LEA @ ($9EAE)  + 2
File Location: [$9B2C]

Illusions

Memory Location:
LEA @ ($9CE6) + 2     
File Location: [$9962]



Set         Original Values     Description
-01:        00 00 07 08  … Illusions / Blue-Black
 00:        00 03 04 0E … Grey
 01:        00 08 04 0E  … Light Blue
 02:        00 05 06 0E … Light Green
 03:        00 09 0A 0B … Brownish Red
 04:        00 09 0C 0B … Red
 05:        00 0A 0B 0D  … Light Orange
 06:        00 0B 0D 0E  … Yellowy White
 07:        00 0C 0B 0D …. Golden Orange
 08:        00 02 03 04  … Darker grey
 09:        00 08 04 0D   …. Light blue /yellow
 0A:        00 05 06 0D  … Green/Yellow
 0B:        00 07 08 04  … Darker blue/grey
 0C:        00 07 08 0D …  Blue/Yellow ?? 


((BOS New palette Location: $5C438))



The "Grade" Colour Selections

A set of 8 bytes is kept for each monster, which selects the colour-set to be used for each grade.


((BOS selections Location: $5C3E4))


Summon 
Colour selection File location: [$9A34]
Colour selection Memory location: ($9Db8) 
LEA @ … ($9CF2) + 2
File Location:  [$9970]

Beholder
Colour selection File location: [$9E28]
Colour selection memory location: ($A1AC)
LEA @ … ($A18C) + 2
File Location: [$9E0A

Behemoth   
Colour selection File location: [$A1AA]
Colour selection memory location: ($A52E)
LEA @ … ($A512) + 2
File Location: [$A190]

Crab 
Colour selection File location: [$9B9C]
Colour selection memory location: ($9F20)
LEA @ … ($9F02) + 2
File Location: [$9B80]

Dragon 
Colour selection File location: [$A022]
Colour selection memory location: ($A3A6)
LEA @ … ($A37C) + 2
File Location: [$9FFA]