ModdingWiki - User contributions [en-gb]

King's Bounty Index Tables

2024-02-05T04:14:15Z

Treeswift: type (extra parenthesis)

As indicated in [[King's Bounty Saved game Format]], some of the values that define [[King's Bounty]]'s world and mission are hardcoded within the main executable (KB.EXE). Specifically, assuming

constexpr int kAlphabet = 26; // 'Z' - 'A' + 1
constexpr int kAlphaExt = kAlphabet + 1; // extra element at the end is the king's castle

the following index tables exist (sample locations provided):

{|class="wikitable"
!Offset 1990!!Data Type!!Description
|-
|0x183f8||[[BYTE]] x[kAlphaExt], y[kAlphaExt]||Castle gate locations (27 X values, then 27 Y values)
|-
|0x1867d||[[BYTE]] c[kAlphabet]||Continent of the castle (0-3).<ref>Used for Castle Gate and for castle entry detection.</ref> 26 values (the king's continent is always 0)
|-
|0x165cb||[[BYTE]] c[kAlphabet]||An identical copy of the above, with unclear purpose.<ref>Possibly a rudiment of an early design allowing town placement on a different continent from its castle?</ref>
|-
|0x169d6||[[BYTE]] c[kAlphabet]||A THIRD identical copy of the above, used e.g. for villain contracts.
|-
|0x18481||[[BYTE]] x[kAlphabet], y[kAlphabet]||Town square coordinates (26 X values, then 26 Y values), *in corresponding castle order*.<ref>The game treats castle-town pairs as, essentially, castle objects with town properties. All town data, except (obviously) for the Town Gate lookup table, are arranged in castle order, i.e. Riverton is #0 because of Azram, Underfoot is #1 because of Basefit, etc. Even the town name strings appear in the file in corresponding castle alphabetical order (Riverton, Underfoot...) instead of their own alphabetical order (Anomaly, Bayview...)</ref>
|-
|0x1852d||[[BYTE]] x[kAlphabet], y[kAlphabet]||Harbor coordinates (where the boat appears); 26 X values, then 26 Y values
|-
|0x18649||[[BYTE]] x[kAlphabet], y[kAlphabet]||"Airport" coordinates (where Town Gate lands the hero); 26 X values, then 26 Y values
|-
|0x18697||[[BYTE]] m[kAlphabet]||town letter -> castle letter mapping for Town Gate (26 indices). E.g. <tt>m[0]</tt> (town of A-Anomaly) is <tt>0x3</tt> (castle of D-Duvock).
|-
|}

== Notes ==
<references/>

Obviously, all of the offsets apply to the uncompressed file.

The Castle Gate spell always places the hero south of the actual castle gate (the Y coordinate is less by 1).

Stepping on a Castle Gate tile (<tt>0x85</tt>) that does not correspond to a recognized castle freezes the game.

Stepping on a Town tile (<tt>0x8a</tt>) that does not correspond to a recognized town immediately returns the hero one step back.

Stepping onto a registered map location (one that's present in the tables) that's not marked by a corresponding interactive tile (town walls or castle gate) on the map does not by itself result in an interaction. In other words, coordinate matching only occurs after tile code matching.

== Original geography ==

The offsets to index tables vary between released game builds. It is, however, possible to locate those tables in the game file by value by using the original castle and town coordinates to build canonical representations of the original index tables and then searching for representative byte sequences.

[https://github.com/treeswift/royalreward Modena] (the KB modding tool) uses the following castle/town coordinates (the first pair being the castle entry, the second the town square, the first directional vector offset to the "Rent Boat" harbor and the second offset to the Town Gate "airfield"):

{{30, 27}, {{29, 12}, se, ss}},
{{47, 6}, {{58, 4}, ne, ww}},
{{36, 49}, {{38, 50}, ee, ss}},
{{30, 18}, {{34, 23}, ss, ee}},
{{11, 46}, {{5, 50}, sw, ss}},
{{22, 49}, {{17, 44}, ee, ww}},
{{41, 36}, {{13, 60}, ee, ww}},
{{43, 27}, {{9, 39}, se, ss}},
{{11, 30}, {{14, 27}, ss, ww}},
{{41, 34}, {{58, 33}, ss, ww}},
{{57, 58}, {{51, 28}, ss, nn}},
{{52, 57}, {{57, 57}, se, ss}},
{{25, 39}, {{3, 37}, sw, ss}},
{{22, 24}, {{17, 21}, ee, ww}},
{{6, 57}, {{41, 58}, ss, ww}},
{{58, 23}, {{50, 13}, sw, nn}},
{{42, 56}, {{58, 60}, ee, ss}},
{{54, 6}, {{57, 5}, sw, ww}},
{{17, 39}, {{9, 60}, ee, ss}},
{{9, 18}, {{13, 7}, ww, nn}},
{{41, 12}, {{7, 3}, ee, ww}},
{{40, 5}, {{12, 3}, ww, nn}},
{{40, 41}, {{46, 35}, ne, ee}},
{{45, 6}, {{49, 8}, ne, ee}},
{{19, 19}, {{3, 8}, nw, nn}},
{{46, 43}, {{58, 48}, ee, ss}},
{{11, 7}, {}} // Washington, D.C.

...and the following castle/continent breakdown:

{|class="wikitable"
!C-index!!Continent!!Castles!!Villains|Castle initials (for Info)
|-
|0||Continentia||11||6|ACFIKNOPRVW
|-
|1||Forestria||6||4|BDJMQY
|-
|2||Archipelia||6||4|EGHLTX
|-
|3||Saharia||3||3|SUZ
|-
|=||(total)||26||17|
|-
|}

You can use the <tt>ham</tt> (name shortened from "Hamming") tool from the [https://github.com/treeswift/royalreward Royal Reward] project to analyze a binary file. Sample output:

conts: 0x165cb # (hamming=0 confidence=100.00%)
conts: 0x169d6 # (hamming=0 confidence=100.00%)
conts: 0x1867d # (hamming=0 confidence=100.00%)
forts[X]: 0x183f8 # (hamming=0 confidence=100.00%)
forts[Y]: 0x18413 # (hamming=0 confidence=100.00%)
ports[X]: 0x18481 # (hamming=0 confidence=100.00%)
ports[Y]: 0x1849b # (hamming=0 confidence=100.00%)
p_bay[X]: 0x1852d # (hamming=0 confidence=100.00%)
p_bay[Y]: 0x18547 # (hamming=0 confidence=100.00%)
p_air[X]: 0x18649 # (hamming=0 confidence=100.00%)
p_air[Y]: 0x18663 # (hamming=0 confidence=100.00%)
ptofs: 0x18697 # (hamming=0 confidence=100.00%)

The tool has been tested on three different versions of <tt>KB.EXE</tt> and successfully located all the 6 kinds of lookup tables (4 of them broken down by X and Y) in each.

By editing all the correlated tables simultaneously it is then possible to move the castles and towns both within and across continents. However, placement of a castle and its corresponding town on two different continents has not yet been achieved and is most probably impossible.

King's Bounty Index Tables

2024-02-02T14:30:45Z

Treeswift: a tool for adaptive index table patching has been added; a third index table found

As indicated in [[King's Bounty Saved game Format]], some of the values that define [[King's Bounty]]'s world and mission are hardcoded within the main executable (KB.EXE). Specifically, assuming

constexpr int kAlphabet = 26; // 'Z' - 'A' + 1
constexpr int kAlphaExt = kAlphabet + 1; // extra element at the end is the king's castle

the following index tables exist (sample locations provided):

{|class="wikitable"
!Offset 1990!!Data Type!!Description
|-
|0x183f8||[[BYTE]] x[kAlphaExt], y[kAlphaExt]||Castle gate locations (27 X values, then 27 Y values)
|-
|0x1867d||[[BYTE]] c[kAlphabet]||Continent of the castle (0-3).<ref>Used for Castle Gate and for castle entry detection.</ref> 26 values (the king's continent is always 0)
|-
|0x165cb||[[BYTE]] c[kAlphabet]||An identical copy of the above, with unclear purpose.<ref>Possibly a rudiment of an early design allowing town placement on a different continent from its castle?</ref>
|-
|0x169d6||[[BYTE]] c[kAlphabet]||A THIRD identical copy of the above, used e.g. for villain contracts.
|-
|0x18481||[[BYTE]] x[kAlphabet], y[kAlphabet]||Town square coordinates (26 X values, then 26 Y values), *in corresponding castle order*.<ref>The game treats castle-town pairs as, essentially, castle objects with town properties. All town data, except (obviously) for the Town Gate lookup table, are arranged in castle order, i.e. Riverton is #0 because of Azram, Underfoot is #1 because of Basefit, etc. Even the town name strings appear in the file in corresponding castle alphabetical order (Riverton, Underfoot...) instead of their own alphabetical order (Anomaly, Bayview...)</ref>
|-
|0x1852d||[[BYTE]] x[kAlphabet], y[kAlphabet]||Harbor coordinates (where the boat appears); 26 X values, then 26 Y values
|-
|0x18649||[[BYTE]] x[kAlphabet], y[kAlphabet]||"Airport" coordinates (where Town Gate lands the hero); 26 X values, then 26 Y values
|-
|0x18697||[[BYTE]] m[kAlphabet]||town letter -> castle letter mapping for Town Gate (26 indices). E.g. <tt>m[0]</tt> (town of A-Anomaly) is <tt>0x3</tt> (castle of D-Duvock).
|-
|}

== Notes ==
<references/>

Obviously, all of the offsets apply to the uncompressed file.

The Castle Gate spell always places the hero south of the actual castle gate (the Y coordinate is less by 1).

Stepping on a Castle Gate tile (<tt>0x85</tt>)) that does not correspond to a recognized castle freezes the game.

Stepping on a Town tile (<tt>0x8a</tt>) that does not correspond to a recognized town immediately returns the hero one step back.

Stepping onto a registered map location (one that's present in the tables) that's not marked by a corresponding interactive tile (town walls or castle gate) on the map does not by itself result in an interaction. In other words, coordinate matching only occurs after tile code matching.

== Original geography ==

The offsets to index tables vary between released game builds. It is, however, possible to locate those tables in the game file by value by using the original castle and town coordinates to build canonical representations of the original index tables and then searching for representative byte sequences.

[https://github.com/treeswift/royalreward Modena] (the KB modding tool) uses the following castle/town coordinates (the first pair being the castle entry, the second the town square, the first directional vector offset to the "Rent Boat" harbor and the second offset to the Town Gate "airfield"):

{{30, 27}, {{29, 12}, se, ss}},
{{47, 6}, {{58, 4}, ne, ww}},
{{36, 49}, {{38, 50}, ee, ss}},
{{30, 18}, {{34, 23}, ss, ee}},
{{11, 46}, {{5, 50}, sw, ss}},
{{22, 49}, {{17, 44}, ee, ww}},
{{41, 36}, {{13, 60}, ee, ww}},
{{43, 27}, {{9, 39}, se, ss}},
{{11, 30}, {{14, 27}, ss, ww}},
{{41, 34}, {{58, 33}, ss, ww}},
{{57, 58}, {{51, 28}, ss, nn}},
{{52, 57}, {{57, 57}, se, ss}},
{{25, 39}, {{3, 37}, sw, ss}},
{{22, 24}, {{17, 21}, ee, ww}},
{{6, 57}, {{41, 58}, ss, ww}},
{{58, 23}, {{50, 13}, sw, nn}},
{{42, 56}, {{58, 60}, ee, ss}},
{{54, 6}, {{57, 5}, sw, ww}},
{{17, 39}, {{9, 60}, ee, ss}},
{{9, 18}, {{13, 7}, ww, nn}},
{{41, 12}, {{7, 3}, ee, ww}},
{{40, 5}, {{12, 3}, ww, nn}},
{{40, 41}, {{46, 35}, ne, ee}},
{{45, 6}, {{49, 8}, ne, ee}},
{{19, 19}, {{3, 8}, nw, nn}},
{{46, 43}, {{58, 48}, ee, ss}},
{{11, 7}, {}} // Washington, D.C.

...and the following castle/continent breakdown:

{|class="wikitable"
!C-index!!Continent!!Castles!!Villains|Castle initials (for Info)
|-
|0||Continentia||11||6|ACFIKNOPRVW
|-
|1||Forestria||6||4|BDJMQY
|-
|2||Archipelia||6||4|EGHLTX
|-
|3||Saharia||3||3|SUZ
|-
|=||(total)||26||17|
|-
|}

You can use the <tt>ham</tt> (name shortened from "Hamming") tool from the [https://github.com/treeswift/royalreward Royal Reward] project to analyze a binary file. Sample output:

conts: 0x165cb # (hamming=0 confidence=100.00%)
conts: 0x169d6 # (hamming=0 confidence=100.00%)
conts: 0x1867d # (hamming=0 confidence=100.00%)
forts[X]: 0x183f8 # (hamming=0 confidence=100.00%)
forts[Y]: 0x18413 # (hamming=0 confidence=100.00%)
ports[X]: 0x18481 # (hamming=0 confidence=100.00%)
ports[Y]: 0x1849b # (hamming=0 confidence=100.00%)
p_bay[X]: 0x1852d # (hamming=0 confidence=100.00%)
p_bay[Y]: 0x18547 # (hamming=0 confidence=100.00%)
p_air[X]: 0x18649 # (hamming=0 confidence=100.00%)
p_air[Y]: 0x18663 # (hamming=0 confidence=100.00%)
ptofs: 0x18697 # (hamming=0 confidence=100.00%)

The tool has been tested on three different versions of <tt>KB.EXE</tt> and successfully located all the 6 kinds of lookup tables (4 of them broken down by X and Y) in each.

By editing all the correlated tables simultaneously it is then possible to move the castles and towns both within and across continents. However, placement of a castle and its corresponding town on two different continents has not yet been achieved and is most probably impossible.

King's Bounty Index Tables

2024-01-25T07:03:37Z

Treeswift: continent labeling

King's Bounty Index Tables

2024-01-25T07:02:24Z

Treeswift: ordering example, clarification

King's Bounty Map Format

2024-01-25T05:34:27Z

Treeswift: Modding hint (1990 version)

{{Map Infobox
| Type = 2D tile-based
| Games =
{{Game|King's Bounty}}
}}

This format is used to store the world map for [[King's Bounty]] in both it's initial state (<tt>LAND.ORG</tt> file) and in modified, randomized state (in the <tt>*.DAT</tt> save files at offset <tt>0xFC5</tt>). Consequently, there are minor format differences, described below.

== File format ==

The map always takes exactly 16384 bytes. As there are 4 continents 64 x 64 tiles each, and each tile takes 1 byte, all continents start at a convenient offset - 0x0000, 0x1000, 0x2000 or 0x3000.

{|class="wikitable"
!Data type!!Description
|-
|[[BYTE]] map[4][64][64]||Map data
|-
|}

=== Coordinates ===

The game is consistent with it's map coordinate system, which goes in the '''bottom-to-top''', left-to-right order. That means top left corner has coordinate X=0, Y=63.

=== Salting ===

When a new game is first created, the initial map data is read and then the following values are replaced:

<pre>
0xFF - continent start -> 0x20 - sea tile
0x8B - put something random here -> 0x8B - 0x93 , but not 0x90
0x8E - archmage's alcove -> 0x00 (for mages) / 0x8E (for rest)
</pre>

Note, that the <tt>0x8B</tt> index is used in both initial and salted data with different meanings - it stands for ''random object'' in <tt>LAND.ORG</tt>, and a ''treasure chest'' in the save files.

=== Tileset ===

The tileset is kept inside the <tt>tileseta.*</tt> and <tt>tilesetb.*</tt> graphic files. Each file contains 36 tiles, making 72 in total. ''Additionally, <tt>tilesalt.*</tt> contains replacements graphics for tiles <tt>0x11-0x13</tt> for continents 2-4''. Each level byte '''with it's most significant bit cleared''' maps directly into that range (<tt>0x00-0x47</tt>). The high bit signifies if the tile is interactive, and those high-bit versions are always used instead of the regular indexes:

<pre>
0x80 - magic barrier (blocks followers)
0x85 - castle gate
0x8A - town
0x8B - treasure chest
0x8C - plains dwelling
0x8D - forest dwelling
0x8E - cave dwelling (multiple purposes)
0x8F - dungeon dwelling
0x90 - sign
0x91 - follower
0x92 - artifact 1
0x93 - artifact 2
</pre>

=== Constant Locations ===

Those locations are hard-coded into the game and can not be changed from within the map:
<pre>
X=11 Y=7 - King's Castle
X=11 Y=6 - Retreat location
X=11 Y=5 - Starting Location
X=11 Y=3 - Continent 1 starting location
X=1 Y=37 - Continent 2 starting location
X=14 Y=62 - Continent 3 starting location
X=9 Y=1 - Continent 4 starting location
X=11 Y=19 - Archmage's Alcove
</pre>

The king's castle coordinates are the last extra element of the [[King's Bounty Index Tables|castle location table]].

== Constraints ==

Remember that while it's possible to place any combination of the tiles on the map, not all of those combinations will be consistent:

# Town square and castle gate locations need to be placed in the game's [[King's Bounty Index Tables|lookup tables]] to be interactive.
# If a desert tile is placed near the ocean tile, it's possible to pull the boat onto the beach and row it across the desert. Each step still takes a day. If this is not a desired effect, separate the desert from the sea with any other terrain (typically, road).
# Of terrain tiles, only the road tile (<tt>0x0</tt>) can "seamlessly neighbor" both its own and all other terrains. Other terrain types (sea, desert, mountains and woods) have a "solid" tile (<tt>0x20</tt> for the sea, <tt>0x2d</tt> for the woods, <tt>0x3a</tt> for the desert and <tt>0x47</tt> for the mountains) that can only neighbor its own terrain and 12 border tiles.

The following code example creates the tile code correction table for border tiles. The correction is added to the code of the respective solid tile:

constexpr int lb = 1, rb = 2, lt = 4, rt = 8;
cor_sea.resize(0x10, 0); // all 16 combinations, though only 13 are supported
cor_sea[lt | rt] = -1; // ▀
cor_sea[lb | rb] = -2; // ▄
cor_sea[rt | rb] = -3; // ▐
cor_sea[lt | lb] = -4; // ▌
cor_sea[rt | rb | lb] = -5; // ▟
cor_sea[lt | rt | rb] = -6; // ▜
cor_sea[rb | lb | lt] = -7; // ▙
cor_sea[rt | lt | lb] = -8; // ▛
cor_sea[lt] = -9; // ▘
cor_sea[lb] = -12; // ▖
cor_sea[rt] = -10; // ▝
cor_sea[rb] = -11; // ▗
cor_for = cor_sea; // sea tiles have a special ordering
cor_for[lb] = -10; // ▖
cor_for[rt] = -11; // ▝
cor_for[rb] = -12; // ▗
cor_snd = cor_mnt = cor_for; // sands, mountains, and forest follow a common order

Generally, every tile of a special terrain (sands, mountains, woods or sea) must be a part of at least one 2x2 patch of the same terrain — i.e., e.g., an isolated 1x1 patch of desert can't be displayed correctly. In addition, diagonal combinations (e.g. a sea tile that's neighboring a sea — i.e. is a part of a 2x2 sea square — to the northeast and southwest, but not to the northwest and southeast, *and has to be a part of both*<ref>Adjacent tiles of the same terrain can still be displayed as if they belonged to disconnected spans of it — look at the fractured desert between Nyre and Xoctan to see what I mean</ref>) can't be displayed correctly, either. E.g. consider the following screen:

sea1 sea1 land
sea1 sea* sea2
land sea2 sea2

The <tt>sea*</tt> tile can be a part of either the 2x2 <tt>sea1</tt> patch or the 2x2 <tt>sea2</tt> patch. If <tt>sea1</tt> is a part of a greater ocean, then <tt>sea1</tt> tiles can be displayed as its border tiles and <tt>sea*</tt> form a block with <tt>sea2</tt> (ditto if <tt>sea2</tt> is a larger sea). If the sea tiles on the screen show a complete lake, there is no way to take the central tile out of either part of the lake without breaking the 2x2 rule.

With narrow diagonal straits the limitation can be mitigated by displaying one of the corners cut off; it looks less crappy than displaying a solid tile (e.g. the <tt>sea*</tt> tile above can have either a northeast or a southwest land corner, but not both). With forest tiles, ignoring inconsistent bottom corners produces slightly better looks than ignoring the top ones. Ideally, however, your generator and/or map editor should not allow graphically inconsistent tiles to border each other.

Note that while original maps don't have narrow forest/mountain passages that only allow a diagonal move, such passages are possible. Followers know how to navigate them, and do.

There is no practical limit on treasure chests ("loot boxes"), since what's in them is determined at random when they are open. However, limited numbers of followers and dwellings are allowed per continent, and these limits are smaller than the nominal array dimensions in the [[King's Bounty Saved game Format|save file]].

<references/>

== Modding ==

Note that there is no <code>land.org</code> in the 1990 game edition -- to play on a custom map, you have to modify the [[King's Bounty Saved game Format|save file]] itself, possibly also modifying the [[King's Bounty Index Tables|lookup tables in KB.EXE]].

== Credits ==

Originally devised by the [http://sourceforge.net/p/openkb/wiki/Home/ openkb project], with best regards to the modding community. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

The constraints have been contributed by the [https://github.com/treeswift/royalreward Royal Reward] project.

File:King's Bounty Map Format.png

2024-01-25T05:30:10Z

Treeswift: Alternative Saharia. Own work (map generator), public domain.

== Summary ==
Alternative Saharia. Own work (map generator), public domain.

King's Bounty Map Format

2024-01-25T05:26:18Z

Treeswift: terrain type named incorrectly

{{Map Infobox
| Type = 2D tile-based
| Games =
{{Game|King's Bounty}}
}}

This format is used to store the world map for [[King's Bounty]] in both it's initial state (<tt>LAND.ORG</tt> file) and in modified, randomized state (in the <tt>*.DAT</tt> save files at offset <tt>0xFC5</tt>). Consequently, there are minor format differences, described below.

== File format ==

The map always takes exactly 16384 bytes. As there are 4 continents 64 x 64 tiles each, and each tile takes 1 byte, all continents start at a convenient offset - 0x0000, 0x1000, 0x2000 or 0x3000.

{|class="wikitable"
!Data type!!Description
|-
|[[BYTE]] map[4][64][64]||Map data
|-
|}

=== Coordinates ===

The game is consistent with it's map coordinate system, which goes in the '''bottom-to-top''', left-to-right order. That means top left corner has coordinate X=0, Y=63.

=== Salting ===

When a new game is first created, the initial map data is read and then the following values are replaced:

<pre>
0xFF - continent start -> 0x20 - sea tile
0x8B - put something random here -> 0x8B - 0x93 , but not 0x90
0x8E - archmage's alcove -> 0x00 (for mages) / 0x8E (for rest)
</pre>

Note, that the <tt>0x8B</tt> index is used in both initial and salted data with different meanings - it stands for ''random object'' in <tt>LAND.ORG</tt>, and a ''treasure chest'' in the save files.

=== Tileset ===

The tileset is kept inside the <tt>tileseta.*</tt> and <tt>tilesetb.*</tt> graphic files. Each file contains 36 tiles, making 72 in total. ''Additionally, <tt>tilesalt.*</tt> contains replacements graphics for tiles <tt>0x11-0x13</tt> for continents 2-4''. Each level byte '''with it's most significant bit cleared''' maps directly into that range (<tt>0x00-0x47</tt>). The high bit signifies if the tile is interactive, and those high-bit versions are always used instead of the regular indexes:

<pre>
0x80 - magic barrier (blocks followers)
0x85 - castle gate
0x8A - town
0x8B - treasure chest
0x8C - plains dwelling
0x8D - forest dwelling
0x8E - cave dwelling (multiple purposes)
0x8F - dungeon dwelling
0x90 - sign
0x91 - follower
0x92 - artifact 1
0x93 - artifact 2
</pre>

=== Constant Locations ===

Those locations are hard-coded into the game and can not be changed from within the map:
<pre>
X=11 Y=7 - King's Castle
X=11 Y=6 - Retreat location
X=11 Y=5 - Starting Location
X=11 Y=3 - Continent 1 starting location
X=1 Y=37 - Continent 2 starting location
X=14 Y=62 - Continent 3 starting location
X=9 Y=1 - Continent 4 starting location
X=11 Y=19 - Archmage's Alcove
</pre>

The king's castle coordinates are the last extra element of the [[King's Bounty Index Tables|castle location table]].

== Constraints ==

Remember that while it's possible to place any combination of the tiles on the map, not all of those combinations will be consistent:

# Town square and castle gate locations need to be placed in the game's [[King's Bounty Index Tables|lookup tables]] to be interactive.
# If a desert tile is placed near the ocean tile, it's possible to pull the boat onto the beach and row it across the desert. Each step still takes a day. If this is not a desired effect, separate the desert from the sea with any other terrain (typically, road).
# Of terrain tiles, only the road tile (<tt>0x0</tt>) can "seamlessly neighbor" both its own and all other terrains. Other terrain types (sea, desert, mountains and woods) have a "solid" tile (<tt>0x20</tt> for the sea, <tt>0x2d</tt> for the woods, <tt>0x3a</tt> for the desert and <tt>0x47</tt> for the mountains) that can only neighbor its own terrain and 12 border tiles.

The following code example creates the tile code correction table for border tiles. The correction is added to the code of the respective solid tile:

constexpr int lb = 1, rb = 2, lt = 4, rt = 8;
cor_sea.resize(0x10, 0); // all 16 combinations, though only 13 are supported
cor_sea[lt | rt] = -1; // ▀
cor_sea[lb | rb] = -2; // ▄
cor_sea[rt | rb] = -3; // ▐
cor_sea[lt | lb] = -4; // ▌
cor_sea[rt | rb | lb] = -5; // ▟
cor_sea[lt | rt | rb] = -6; // ▜
cor_sea[rb | lb | lt] = -7; // ▙
cor_sea[rt | lt | lb] = -8; // ▛
cor_sea[lt] = -9; // ▘
cor_sea[lb] = -12; // ▖
cor_sea[rt] = -10; // ▝
cor_sea[rb] = -11; // ▗
cor_for = cor_sea; // sea tiles have a special ordering
cor_for[lb] = -10; // ▖
cor_for[rt] = -11; // ▝
cor_for[rb] = -12; // ▗
cor_snd = cor_mnt = cor_for; // sands, mountains, and forest follow a common order

Generally, every tile of a special terrain (sands, mountains, woods or sea) must be a part of at least one 2x2 patch of the same terrain — i.e., e.g., an isolated 1x1 patch of desert can't be displayed correctly. In addition, diagonal combinations (e.g. a sea tile that's neighboring a sea — i.e. is a part of a 2x2 sea square — to the northeast and southwest, but not to the northwest and southeast, *and has to be a part of both*<ref>Adjacent tiles of the same terrain can still be displayed as if they belonged to disconnected spans of it — look at the fractured desert between Nyre and Xoctan to see what I mean</ref>) can't be displayed correctly, either. E.g. consider the following screen:

sea1 sea1 land
sea1 sea* sea2
land sea2 sea2

The <tt>sea*</tt> tile can be a part of either the 2x2 <tt>sea1</tt> patch or the 2x2 <tt>sea2</tt> patch. If <tt>sea1</tt> is a part of a greater ocean, then <tt>sea1</tt> tiles can be displayed as its border tiles and <tt>sea*</tt> form a block with <tt>sea2</tt> (ditto if <tt>sea2</tt> is a larger sea). If the sea tiles on the screen show a complete lake, there is no way to take the central tile out of either part of the lake without breaking the 2x2 rule.

With narrow diagonal straits the limitation can be mitigated by displaying one of the corners cut off; it looks less crappy than displaying a solid tile (e.g. the <tt>sea*</tt> tile above can have either a northeast or a southwest land corner, but not both). With forest tiles, ignoring inconsistent bottom corners produces slightly better looks than ignoring the top ones. Ideally, however, your generator and/or map editor should not allow graphically inconsistent tiles to border each other.

Note that while original maps don't have narrow forest/mountain passages that only allow a diagonal move, such passages are possible. Followers know how to navigate them, and do.

There is no practical limit on treasure chests ("loot boxes"), since what's in them is determined at random when they are open. However, limited numbers of followers and dwellings are allowed per continent, and these limits are smaller than the nominal array dimensions in the [[King's Bounty Saved game Format|save file]].

<references/>

== Credits ==

Originally devised by the [http://sourceforge.net/p/openkb/wiki/Home/ openkb project], with best regards to the modding community. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

King's Bounty Saved game Format

2024-01-25T03:48:53Z

Treeswift: Coordinate indices

{{Playerdata Infobox
| Savegame = Yes
| Elements = Many
| Games =
{{Game|King's Bounty}}
}}

This format is used to save the whole game state for [[King's Bounty]].

As the save files do not require re-insertion into group files, nor are compressed, yet maintain their own full copies of the game world, they provide good opportunity to distribute custom levels or maps.

== File format ==

A save always takes exactly 20421 bytes.

<pre>
0x000 - 0x00A | name
0x00B | class
0x00C | rank
0x00D | spell power
0x00E | max # of spells
0x00F - 0x01F | is villain N caught
0x020 - 0x027 | is artifact N found
0x028 - 0x02B | is continent N available
0x02C - 0x02F | is orb N found
0x030 - 0x03D | number of spells N
0x03E | knows magic
0x03F | siege weapons
0x040 | current contract
0x041 - 0x045 | hero army
0x046 | Option: Delay (0-9)
0x047 | difficulty
0x048 | Option: Sounds
0x049 | Option: Walk Beep
0x04A | Option: Animation
0x04B | Option: Show Army Size
0x04C | hero continent
0x04D | hero X
0x04E | hero Y
0x04F | last X
0x050 | last Y
0x051 | boat X
0x052 | boat Y
0x053 | boat continent (0xFF - no boat)
0x054 | mount mode (0x00 - boat, 0x04 - fly, 0x08 - horse)
0x055 | Option: CGA palette
0x056 - 0x069 | spell sold in town N
0x070 - 0x074 | contract cycle (5 villains)
0x075 | last contract (starts as 0x04 to flip to 0x00 on first run)
0x076 | max contract (starts as 0x05)
0x077 | steps left (until end of day; never becomes 0, always refills to 0x28=decimal 40)
0x078 | days left until the end of the week (never becomes 0, refills to 5 every new week)
0x079 - 0x092 | castle owned by... (0x7F = no one, 0xFF = you, LOW 5 bits = villain)
0x093 - 0x0AC | visited castle N
0x0AD - 0x0C6 | visited town N
0x0C7 | scepter continent ('encrypted')
0x0C8 | scepter X ('encrypted')
0x0C9 | scepter Y ('encrypted')
0x0CA - 0x8C9 | fog of war (1bpp)
0x8CA - 0x94B | garrison troops
0x94C - 0x973 | foeF coords (2 bytes each, 5 per continent)
0x974 - 0x979 | map chests coords (2 bytes each, 1 per continent)
0x97a - 0x981 | orb chests coords (2 bytes each, 1 per continent)
0x982 - 0x991 | teleporter coords (2 bytes each, 2 per continent)
0x992 - 0x9E9 | dwelling coords (2 bytes each, 11 per continent)
0x9EA - 0xB01 | foeH coords (2 bytes each, 35 per continent)
0xB02 - 0xCA5 | foeH troops (3 bytes each)
0xCA6 - 0xE49 | foeH numbers (3 bytes each)
0xE4A - 0xE75 | dwelling N troop
0xE76 - 0xEA1 | dwelling N population
0xEA2 | scepter key (to XOR scepter coords with)
0xEA3 - 0xEA4 | base leadership
0xEA5 - 0xEA6 | leadership
0xEA7 - 0xEA8 | commission
0xEA9 - 0xEAA | followers killed
0xEAB - 0xEB4 | hero army numbers
0xEB5 - 0xFB8 | garrison numbers
0xFB9 - 0xFBA | time stop ("free" steps left)
0xFBB - 0xFBC | days left
0xFBD - 0xFBE | score (never actually used)
0xFBF | ? // unknown1, always "00"
0xFC0 | ? // unknown2, always "00"
0xFC1 - 0xFC4 | gold
0xFC5 - END | map dump
</pre>

=== Notes ===



* Player name is padded with spaces
* There are 26 castles, 26 towns, 17 villains, 25 troops, 14 spells and 4 continents in the game.
* Coordinates always take 2 bytes and always go in X, Y order.
* Scepter coordinates are XORed with ''scepter key'' upon load/save.
* Troop and villain indexes are in production order (as seen in .CC files).
* Dwelling populations are kept in [[BYTE]]s, 250 being maximum possible value.
* Hero and castle army numbers are kept in [[UINT16LE]]s, 5 per army.
* Hostile foes only have 3 troops and their numbers are kept in [[BYTE]]s.
* The ''mount mode'' is also an offset into hero's sprite-sheet.
* The map is a complete dump in [[King's Bounty Map Format]].

=== Coordinates ===

The game is consistent with it's map coordinate system, which goes in the '''bottom-to-top''', left-to-right order. That means top left corner has coordinate X=0, Y=63.

=== Limitations ===

Dwellings and followers must be sorted in ascending <code><Y, then X></code> coordinate order to allow fast binary search. Breaking the order causes the game to "miss" some of them, handling them incorrectly. (Illegal dwellings cause the game to hang when entered, and illegal roaming gangs don't automatically follow the hero and don't display unit sizes when confronted.)

The numbers of followers and dwellings on each continent are limited independently. Filling the dwelling and follower tables up to their declared array dimensions causes the game to freeze when the hero tries to confront a follower or enter a dwelling that's located too far to the north (in the greater Y coordinate direction). At least the following values are safe:

{|class="wikitable"
!Continent!!Followers!!Dwellings
|-
|0=Continentia||35||11
|-
|1=Forestria||27||10
|-
|2=Archipelia||10||8
|-
|3=Saharia||15||7
|-
|}

Un-filled coordinate array positions have X=0, Y=0.

More (or fewer) sign poles can be placed on the map, but each continent's offset into the global "posted messages" table is fixed. For example, there are 22 sign poles in Continentia. If you place a 23rd one, they will be re-indexed (in the <code>Y, then X</code> order) when the saved file is read, and the north-northeastern-most one will display the same message as the south-southwestern-most one in Forestria. However, the number of sign poles in Continentia does not affect offsets to messages (and, therefore, messages themselves) displayed by the sign poles in Forestria.

== Credits ==

Originally devised by the [http://sourceforge.net/p/openkb/wiki/Home/ openkb project], with best regards to the modding community. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

King's Bounty Saved game Format

2024-01-25T03:47:44Z

Treeswift: Lookup table sizes and limitations on saved game files

{{Playerdata Infobox
| Savegame = Yes
| Elements = Many
| Games =
{{Game|King's Bounty}}
}}

This format is used to save the whole game state for [[King's Bounty]].

As the save files do not require re-insertion into group files, nor are compressed, yet maintain their own full copies of the game world, they provide good opportunity to distribute custom levels or maps.

== File format ==

A save always takes exactly 20421 bytes.

<pre>
0x000 - 0x00A | name
0x00B | class
0x00C | rank
0x00D | spell power
0x00E | max # of spells
0x00F - 0x01F | is villain N caught
0x020 - 0x027 | is artifact N found
0x028 - 0x02B | is continent N available
0x02C - 0x02F | is orb N found
0x030 - 0x03D | number of spells N
0x03E | knows magic
0x03F | siege weapons
0x040 | current contract
0x041 - 0x045 | hero army
0x046 | Option: Delay (0-9)
0x047 | difficulty
0x048 | Option: Sounds
0x049 | Option: Walk Beep
0x04A | Option: Animation
0x04B | Option: Show Army Size
0x04C | hero continent
0x04D | hero X
0x04E | hero Y
0x04F | last X
0x050 | last Y
0x051 | boat X
0x052 | boat Y
0x053 | boat continent (0xFF - no boat)
0x054 | mount mode (0x00 - boat, 0x04 - fly, 0x08 - horse)
0x055 | Option: CGA palette
0x056 - 0x069 | spell sold in town N
0x070 - 0x074 | contract cycle (5 villains)
0x075 | last contract (starts as 0x04 to flip to 0x00 on first run)
0x076 | max contract (starts as 0x05)
0x077 | steps left (until end of day; never becomes 0, always refills to 0x28=decimal 40)
0x078 | days left until the end of the week (never becomes 0, refills to 5 every new week)
0x079 - 0x092 | castle owned by... (0x7F = no one, 0xFF = you, LOW 5 bits = villain)
0x093 - 0x0AC | visited castle N
0x0AD - 0x0C6 | visited town N
0x0C7 | scepter continent ('encrypted')
0x0C8 | scepter X ('encrypted')
0x0C9 | scepter Y ('encrypted')
0x0CA - 0x8C9 | fog of war (1bpp)
0x8CA - 0x94B | garrison troops
0x94C - 0x973 | foeF coords (2 bytes each, 5 per continent)
0x974 - 0x979 | map chests coords (2 bytes each, 1 per continent)
0x97a - 0x981 | orb chests coords (2 bytes each, 1 per continent)
0x982 - 0x991 | teleporter coords (2 bytes each, 2 per continent)
0x992 - 0x9E9 | dwelling coords (2 bytes each, 11 per continent)
0x9EA - 0xB01 | foeH coords (2 bytes each, 35 per continent)
0xB02 - 0xCA5 | foeH troops (3 bytes each)
0xCA6 - 0xE49 | foeH numbers (3 bytes each)
0xE4A - 0xE75 | dwelling N troop
0xE76 - 0xEA1 | dwelling N population
0xEA2 | scepter key (to XOR scepter coords with)
0xEA3 - 0xEA4 | base leadership
0xEA5 - 0xEA6 | leadership
0xEA7 - 0xEA8 | commission
0xEA9 - 0xEAA | followers killed
0xEAB - 0xEB4 | hero army numbers
0xEB5 - 0xFB8 | garrison numbers
0xFB9 - 0xFBA | time stop ("free" steps left)
0xFBB - 0xFBC | days left
0xFBD - 0xFBE | score (never actually used)
0xFBF | ? // unknown1, always "00"
0xFC0 | ? // unknown2, always "00"
0xFC1 - 0xFC4 | gold
0xFC5 - END | map dump
</pre>

=== Notes ===



* Player name is padded with spaces
* There are 26 castles, 26 towns, 17 villains, 25 troops, 14 spells and 4 continents in the game.
* Coordinates always take 2 bytes and always go in X, Y order.
* Scepter coordinates are XORed with ''scepter key'' upon load/save.
* Troop and villain indexes are in production order (as seen in .CC files).
* Dwelling populations are kept in [[BYTE]]s, 250 being maximum possible value.
* Hero and castle army numbers are kept in [[UINT16LE]]s, 5 per army.
* Hostile foes only have 3 troops and their numbers are kept in [[BYTE]]s.
* The ''mount mode'' is also an offset into hero's sprite-sheet.
* The map is a complete dump in [[King's Bounty Map Format]].

=== Coordinates ===

The game is consistent with it's map coordinate system, which goes in the '''bottom-to-top''', left-to-right order. That means top left corner has coordinate X=0, Y=63.

=== Limitations ===

Dwellings and followers must be sorted in ascending <code><Y, then X></code> coordinate order to allow fast binary search. Breaking the order causes the game to "miss" some of them, handling them incorrectly. (Illegal dwellings cause the game to hang when entered, and illegal roaming gangs don't automatically follow the hero and don't display unit sizes when confronted.)

The numbers of followers and dwellings on each continent are limited independently. Filling the dwelling and follower tables up to their declared array dimensions causes the game to freeze when the hero tries to confront a follower or enter a dwelling that's located too far to the north (in the greater Y coordinate direction). At least the following values are safe:

{|class="wikitable"
!Continent!!Followers!!Dwellings
|-
|0=Continentia||35||11
|-
|0=Forestria||27||10
|-
|0=Archipelia||10||8
|-
|0=Saharia||15||7
|-
|}

Un-filled coordinate array positions have X=0, Y=0.

More (or fewer) sign poles can be placed on the map, but each continent's offset into the global "posted messages" table is fixed. For example, there are 22 sign poles in Continentia. If you place a 23rd one, they will be re-indexed (in the <code>Y, then X</code> order) when the saved file is read, and the north-northeastern-most one will display the same message as the south-southwestern-most one in Forestria. However, the number of sign poles in Continentia does not affect offsets to messages (and, therefore, messages themselves) displayed by the sign poles in Forestria.

== Credits ==

Originally devised by the [http://sourceforge.net/p/openkb/wiki/Home/ openkb project], with best regards to the modding community. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

King's Bounty Map Format

2024-01-25T03:34:08Z

Treeswift: Level map consistency constraints

{{Map Infobox
| Type = 2D tile-based
| Games =
{{Game|King's Bounty}}
}}

This format is used to store the world map for [[King's Bounty]] in both it's initial state (<tt>LAND.ORG</tt> file) and in modified, randomized state (in the <tt>*.DAT</tt> save files at offset <tt>0xFC5</tt>). Consequently, there are minor format differences, described below.

== File format ==

The map always takes exactly 16384 bytes. As there are 4 continents 64 x 64 tiles each, and each tile takes 1 byte, all continents start at a convenient offset - 0x0000, 0x1000, 0x2000 or 0x3000.

{|class="wikitable"
!Data type!!Description
|-
|[[BYTE]] map[4][64][64]||Map data
|-
|}

=== Coordinates ===

The game is consistent with it's map coordinate system, which goes in the '''bottom-to-top''', left-to-right order. That means top left corner has coordinate X=0, Y=63.

=== Salting ===

When a new game is first created, the initial map data is read and then the following values are replaced:

<pre>
0xFF - continent start -> 0x20 - sea tile
0x8B - put something random here -> 0x8B - 0x93 , but not 0x90
0x8E - archmage's alcove -> 0x00 (for mages) / 0x8E (for rest)
</pre>

Note, that the <tt>0x8B</tt> index is used in both initial and salted data with different meanings - it stands for ''random object'' in <tt>LAND.ORG</tt>, and a ''treasure chest'' in the save files.

=== Tileset ===

The tileset is kept inside the <tt>tileseta.*</tt> and <tt>tilesetb.*</tt> graphic files. Each file contains 36 tiles, making 72 in total. ''Additionally, <tt>tilesalt.*</tt> contains replacements graphics for tiles <tt>0x11-0x13</tt> for continents 2-4''. Each level byte '''with it's most significant bit cleared''' maps directly into that range (<tt>0x00-0x47</tt>). The high bit signifies if the tile is interactive, and those high-bit versions are always used instead of the regular indexes:

<pre>
0x80 - magic barrier (blocks followers)
0x85 - castle gate
0x8A - town
0x8B - treasure chest
0x8C - plains dwelling
0x8D - forest dwelling
0x8E - cave dwelling (multiple purposes)
0x8F - dungeon dwelling
0x90 - sign
0x91 - follower
0x92 - artifact 1
0x93 - artifact 2
</pre>

=== Constant Locations ===

Those locations are hard-coded into the game and can not be changed from within the map:
<pre>
X=11 Y=7 - King's Castle
X=11 Y=6 - Retreat location
X=11 Y=5 - Starting Location
X=11 Y=3 - Continent 1 starting location
X=1 Y=37 - Continent 2 starting location
X=14 Y=62 - Continent 3 starting location
X=9 Y=1 - Continent 4 starting location
X=11 Y=19 - Archmage's Alcove
</pre>

The king's castle coordinates are the last extra element of the [[King's Bounty Index Tables|castle location table]].

== Constraints ==

Remember that while it's possible to place any combination of the tiles on the map, not all of those combinations will be consistent:

# Town square and castle gate locations need to be placed in the game's [[King's Bounty Index Tables|lookup tables]] to be interactive.
# If a desert tile is placed near the ocean tile, it's possible to pull the boat onto the beach and row it across the desert. Each step still takes a day. If this is not a desired effect, separate the desert from the sea with any other terrain (typically, road).
# Of terrain tiles, only the road tile (<tt>0x0</tt>) can "seamlessly neighbor" both its own and all other terrains. Other terrain types (sea, desert, mountains and woods) have a "solid" tile (<tt>0x20</tt> for the sea, <tt>0x2d</tt> for the woods, <tt>0x3a</tt> for the desert and <tt>0x47</tt> for the mountains) that can only neighbor its own terrain and 12 border tiles.

The following code example creates the tile code correction table for border tiles. The correction is added to the code of the respective solid tile:

constexpr int lb = 1, rb = 2, lt = 4, rt = 8;
cor_sea.resize(0x10, 0); // all 16 combinations, though only 13 are supported
cor_sea[lt | rt] = -1; // ▀
cor_sea[lb | rb] = -2; // ▄
cor_sea[rt | rb] = -3; // ▐
cor_sea[lt | lb] = -4; // ▌
cor_sea[rt | rb | lb] = -5; // ▟
cor_sea[lt | rt | rb] = -6; // ▜
cor_sea[rb | lb | lt] = -7; // ▙
cor_sea[rt | lt | lb] = -8; // ▛
cor_sea[lt] = -9; // ▘
cor_sea[lb] = -12; // ▖
cor_sea[rt] = -10; // ▝
cor_sea[rb] = -11; // ▗
cor_for = cor_sea; // sea tiles have a special ordering
cor_for[lb] = -10; // ▖
cor_for[rt] = -11; // ▝
cor_for[rb] = -12; // ▗
cor_snd = cor_mnt = cor_for; // sands, mountains, and forest follow a common order

Generally, every tile of a special terrain (sands, mountains, woods and road) must be a part of at least one 2x2 patch of the same terrain — i.e., e.g., an isolated 1x1 patch of desert can't be displayed correctly. In addition, diagonal combinations (e.g. a sea tile that's neighboring a sea — i.e. is a part of a 2x2 sea square — to the northeast and southwest, but not to the northwest and southeast, *and has to be a part of both*<ref>Adjacent tiles of the same terrain can still be displayed as if they belonged to disconnected spans of it — look at the fractured desert between Nyre and Xoctan to see what I mean</ref>) can't be displayed correctly, either. E.g. consider the following screen:

sea1 sea1 land
sea1 sea* sea2
land sea2 sea2

The <tt>sea*</tt> tile can be a part of either the 2x2 <tt>sea1</tt> patch or the 2x2 <tt>sea2</tt> patch. If <tt>sea1</tt> is a part of a greater ocean, then <tt>sea1</tt> tiles can be displayed as its border tiles and <tt>sea*</tt> form a block with <tt>sea2</tt> (ditto if <tt>sea2</tt> is a larger sea). If the sea tiles on the screen show a complete lake, there is no way to take the central tile out of either part of the lake without breaking the 2x2 rule.

With narrow diagonal straits the limitation can be mitigated by displaying one of the corners cut off; it looks less crappy than displaying a solid tile (e.g. the <tt>sea*</tt> tile above can have either a northeast or a southwest land corner, but not both). With forest tiles, ignoring inconsistent bottom corners produces slightly better looks than ignoring the top ones. Ideally, however, your generator and/or map editor should not allow graphically inconsistent tiles to border each other.

Note that while original maps don't have narrow forest/mountain passages that only allow a diagonal move, such passages are possible. Followers know how to navigate them, and do.

There is no practical limit on treasure chests ("loot boxes"), since what's in them is determined at random when they are open. However, limited numbers of followers and dwellings are allowed per continent, and these limits are smaller than the nominal array dimensions in the [[King's Bounty Saved game Format|save file]].

<references/>

== Credits ==

Originally devised by the [http://sourceforge.net/p/openkb/wiki/Home/ openkb project], with best regards to the modding community. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)

King's Bounty

2024-01-25T02:49:04Z

Treeswift: Link to a modding toolset added (open source, public domain)

{{NeedMoreInfo}}
{{Game Infobox
| Levels = Some
| Tiles = No
| Sprites = No
| Fullscreen = No
| Sound = No
| Music = No
| Text = No
| Story = No
| Interface = No
}}

{{BeginGameFileList}}
{{GameFile
| Name = 416.cc 256.cc
| Format = [[CC Format]]
| KnownFormat = Yes
| Desc = Archive files
}}
{{GameFile
| Name = *.4 *.16 *.256
| Format = [[King's Bounty Graphics Format]]
| KnownFormat = Yes
| Desc = Graphics files
}}
{{GameFile
| Name = land.org
| Format = [[King's Bounty Map Format]]
| KnownFormat = Yes
| Desc = World map
}}
{{GameFile
| Name = *.dat
| Format = [[King's Bounty Saved game Format]]
| KnownFormat = Yes
| Desc = Saved games
}}
{{GameFile
| Name = kb.ch
| Format = Bitmap font, 8x8 1bpp
| KnownFormat = Yes
| Desc = Font
}}
{{GameFile
| Name = N/A
| Format = [[King's Bounty Music Format]]
| KnownFormat = Yes
| Desc = Music (stored inside in <tt>KB.EXE</tt>)
}}
{{GameFile
| Name = N/A
| Format = [[King's Bounty Index Tables]]
| KnownFormat = Yes
| Desc = Castle/town locations and mapping (inside <tt>KB.EXE</tt>)
}}
{{EndGameFileList}}

== EXE compression ==

The 1995 version of <tt>kb.exe</tt> contains no compression. The 1990 version is compressed twice: with
[[Microsoft EXEPACK]] in inner layer and [[Knowledge Dynamics LZW COMPRESSOR]] in outer layer.
To mod this version, both compressions should be removed. Telling two versions apart is easy - uncompressed
exe is 113718 bytes long, while compressed takes only 79839 bytes.

== External links ==
* [https://sourceforge.net/p/openkb/wiki/Home/ OpenKB] - open-source clone / digital preservation project.
* [https://github.com/treeswift/royalreward Royal Reward] - a research/modding toolset aiming at a public domain reimplementation

File:Mod-King's Bounty.png

2024-01-25T02:44:07Z

Treeswift: Playing on a custom autogenerated map. Own work, public domain.

== Summary ==
Playing on a custom autogenerated map. Own work, public domain.

User:Treeswift

2024-01-25T02:23:03Z

Treeswift: Link to modding project page

Class "C": church, cooking, cats, concepts, coding, castles, combat, command, conquest, pedantiCism and nitpiCking.

* Medium-term plans: researching and modding the original [[King's Bounty]]. (DoD: playing KB on a new, randomly generated map.)
* Long-term goals: a public domain implementation of the game mechanics. If you know your party's ext... sorry. If you know exactly how attack and retaliation damage are calculated, it would be great if you leave a comment or drop me a message.

External link: [https://github.com/treeswift/royalreward Royal Reward (a KB map generator and modding toolset, early but already playable)]

King's Bounty

2024-01-25T02:16:59Z

Treeswift: Linked to castles and towns metadata page

{{NeedMoreInfo}}
{{Game Infobox
| Levels = No
| Tiles = No
| Sprites = No
| Fullscreen = No
| Sound = No
| Music = No
| Text = No
| Story = No
| Interface = No
}}

{{BeginGameFileList}}
{{GameFile
| Name = 416.cc 256.cc
| Format = [[CC Format]]
| KnownFormat = Yes
| Desc = Archive files
}}
{{GameFile
| Name = *.4 *.16 *.256
| Format = [[King's Bounty Graphics Format]]
| KnownFormat = Yes
| Desc = Graphics files
}}
{{GameFile
| Name = land.org
| Format = [[King's Bounty Map Format]]
| KnownFormat = Yes
| Desc = World map
}}
{{GameFile
| Name = *.dat
| Format = [[King's Bounty Saved game Format]]
| KnownFormat = Yes
| Desc = Saved games
}}
{{GameFile
| Name = kb.ch
| Format = Bitmap font, 8x8 1bpp
| KnownFormat = Yes
| Desc = Font
}}
{{GameFile
| Name = N/A
| Format = [[King's Bounty Music Format]]
| KnownFormat = Yes
| Desc = Music (stored inside in <tt>KB.EXE</tt>)
}}
{{GameFile
| Name = N/A
| Format = [[King's Bounty Index Tables]]
| KnownFormat = Yes
| Desc = Castle/town locations and mapping (inside <tt>KB.EXE</tt>)
}}
{{EndGameFileList}}

== EXE compression ==

The 1995 version of <tt>kb.exe</tt> contains no compression. The 1990 version is compressed twice: with
[[Microsoft EXEPACK]] in inner layer and [[Knowledge Dynamics LZW COMPRESSOR]] in outer layer.
To mod this version, both compressions should be removed. Telling two versions apart is easy - uncompressed
exe is 113718 bytes long, while compressed takes only 79839 bytes.

== External links ==
* [https://sourceforge.net/p/openkb/wiki/Home/ OpenKB] - open-source clone / digital preservation project.

King's Bounty Index Tables

2024-01-25T02:12:18Z

Treeswift: mal-formatted TODO

King's Bounty Index Tables

2024-01-25T02:10:46Z

Treeswift: Lookup tables defining correspondences between castle locations, town locations, castle and town names, and continents.

User:Treeswift

2024-01-19T08:56:56Z

Treeswift: link to the game page

User:Treeswift

2024-01-19T08:55:05Z

Treeswift: Clarification of longer-term plans.

Class "C": church, cooking, cats, concepts, coding, castles, combat, command, conquest, pedantiCism and nitpiCking.

* Medium-term plans: researching and modding the original King's Bounty. (DoD: playing KB on a new, randomly generated map.)
* Long-term goals: a public domain implementation of the game mechanics. If you know your party's ext... sorry. If you know exactly how attack and retaliation damage are calculated, it would be great if you leave a comment or drop me a message.

King's Bounty Saved game Format

2024-01-19T08:41:41Z

Treeswift: clarified the meaning of fields at offsets 0x77 and 0x78

{{Playerdata Infobox
| Savegame = Yes
| Elements = Many
| Games =
{{Game|King's Bounty}}
}}

This format is used to save the whole game state for [[King's Bounty]].

As the save files do not require re-insertion into group files, nor are compressed, yet maintain their own full copies of the game world, they provide good opportunity to distribute custom levels or maps.

== File format ==

A save always takes exactly 20421 bytes.

<pre>
0x000 - 0x00A | name
0x00B | class
0x00C | rank
0x00D | spell power
0x00E | max # of spells
0x00F - 0x01F | is villain N caught
0x020 - 0x027 | is artifact N found
0x028 - 0x02B | is continent N available
0x02C - 0x02F | is orb N found
0x030 - 0x03D | number of spells N
0x03E | knows magic
0x03F | siege weapons
0x040 | current contract
0x041 - 0x045 | hero army
0x046 | Option: Delay (0-9)
0x047 | difficulty
0x048 | Option: Sounds
0x049 | Option: Walk Beep
0x04A | Option: Animation
0x04B | Option: Show Army Size
0x04C | hero continent
0x04D | hero X
0x04E | hero Y
0x04F | last X
0x050 | last Y
0x051 | boat X
0x052 | boat Y
0x053 | boat continent (0xFF - no boat)
0x054 | mount mode (0x00 - boat, 0x04 - fly, 0x08 - horse)
0x055 | Option: CGA palette
0x056 - 0x069 | spell sold in town N
0x070 - 0x074 | contract cycle (5 villains)
0x075 | last contract (starts as 0x04 to flip to 0x00 on first run)
0x076 | max contract (starts as 0x05)
0x077 | steps left (until end of day; never becomes 0, always refills to 0x28=decimal 40)
0x078 | days left until the end of the week (never becomes 0, refills to 5 every new week)
0x079 - 0x092 | castle owned by... (0x7F = no one, 0xFF = you, LOW 5 bits = villain)
0x093 - 0x0AC | visited castle N
0x0AD - 0x0C6 | visited town N
0x0C7 | scepter continent ('encrypted')
0x0C8 | scepter X ('encrypted')
0x0C9 | scepter Y ('encrypted')
0x0CA - 0x8C9 | fog of war (1bpp)
0x8CA - 0x94B | garrison troops
0x94C - 0x973 | foeF coords (2 bytes each, 5 per continent)
0x974 - 0x979 | map chests coords (2 bytes each, 1 per continent)
0x97a - 0x981 | orb chests coords (2 bytes each, 1 per continent)
0x982 - 0x991 | teleporter coords (2 bytes each, 2 per continent)
0x992 - 0x9E9 | dwelling coords (2 bytes each, 11 per continent)
0x9EA - 0xB01 | foeH coords (2 bytes each, 35 per continent)
0xB02 - 0xCA5 | foeH troops (3 bytes each)
0xCA6 - 0xE49 | foeH numbers (3 bytes each)
0xE4A - 0xE75 | dwelling N troop
0xE76 - 0xEA1 | dwelling N population
0xEA2 | scepter key (to XOR scepter coords with)
0xEA3 - 0xEA4 | base leadership
0xEA5 - 0xEA6 | leadership
0xEA7 - 0xEA8 | commission
0xEA9 - 0xEAA | followers killed
0xEAB - 0xEB4 | hero army numbers
0xEB5 - 0xFB8 | garrison numbers
0xFB9 - 0xFBA | time stop ("free" steps left)
0xFBB - 0xFBC | days left
0xFBD - 0xFBE | score (never actually used)
0xFBF | ? // unknown1, always "00"
0xFC0 | ? // unknown2, always "00"
0xFC1 - 0xFC4 | gold
0xFC5 - END | map dump
</pre>

=== Notes ===



* Player name is padded with spaces
* There are 26 castles, 26 towns, 17 villains, 25 troops, 14 spells and 4 continents in the game.
* Coordinates always take 2 bytes and always go in X, Y order.
* Scepter coordinates are XORed with ''scepter key'' upon load/save.
* Troop and villain indexes are in production order (as seen in .CC files).
* Dwelling populations are kept in [[BYTE]]s, 250 being maximum possible value.
* Hero and castle army numbers are kept in [[UINT16LE]]s, 5 per army.
* Hostile foes only have 3 troops and their numbers are kept in [[BYTE]]s.
* The ''mount mode'' is also an offset into hero's sprite-sheet.
* The map is a complete dump in [[King's Bounty Map Format]].

=== Coordinates ===

The game is consistent with it's map coordinate system, which goes in the '''bottom-to-top''', left-to-right order. That means top left corner has coordinate X=0, Y=63.

== Credits ==

Originally devised by the [http://sourceforge.net/p/openkb/wiki/Home/ openkb project], with best regards to the modding community. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)