part 41
Tribes: a copy that can be measured
Tribes copy the map, dealing, rules and opponent of the original Dice Wars from a description of its code, and are a full game of Kastgard. What differs from the Principalities and what is not verified.
The game Audamir has Tribes (Slovak "Kmene"): a game that is meant to behave like the original Dice Wars, not only to look like it. Tribes were created on 2 November 2026 as a preset (version 0.86.0), and on the same day they became a full game of Kastgard: a tile, the scoring, the record (versions 0.88 to 0.90). They exist only in the development version of the game (the state of 3 November: 0.97.1); I do not claim anything about a release for other players.
The article says what differs from the Principalities (from 2 November 2026 they also carry this name in their ids, keys and file names), why the Principalities did not change and what is not verified yet. The answer is not "it is known": the copy is checked against the description of the original and by measurements, not against its run. The map, the dealing and the origin of the description are in the article about the source code, the opponent in the article about the opponent.
What Tribes are and what they are not
The Principalities have, since 29 October, a map called "field": a rectangle of small hexagons that the territories fill unevenly. The field was drawn by eye from pictures of the original, so that it looks like it. Tribes are something else: a copy of the process according to the code. One is an imitation of a shape, the other an imitation of a procedure.
| Tribes | Principalities (unchanged) | |
|---|---|---|
| map | grid 28 × 32 = 896 cells; territories grow one at a time from a core of 8 cells and a ring, at most 31; single-cell seas are filled, territories of 5 cells and fewer are dissolved; no repetition and no check of connectedness | field: a rectangle in which the territories take what they take; number of territories by the number of players (32 with 2 and 4, 42 with 7, 48 with 8) |
| dealing | territories in the order of creation, circularly over the players; dice 1 + 2 × N, each on a random territory of a player with fewer than 8 dice; dealing ends when the player whose turn it is has no suitable territory | random division of territories, dice by the average |
| order of players | the order of the original, starting with the player in first place; seats are renumbered (see below) | a start from a random seat |
| rules | the same as in the Principalities (a tie belongs to the defender, after a win all dice but one move over, a reserve of 64, the largest group, random placing, the loss of the human ends the game), but without the offer to end on points | with the offer after four quiet rounds |
| opponent | one level: the opponent of the original | levels 1 to 3 and personalities (the AI opponents) |
| players | 2 to 8, 7 by default | 2 to 8, 4 by default |
| entrance | a tile right after the Principalities; a screen that shows the map that Play starts, and the number of players | a tile with a configurator |
| what is counted | score, experience, Golden Dice, history, ranking, general achievements and the Tribes' own achievements (four chains, eight steps); not the daily challenge and not the chains of the Principalities | everything |
| around the game | saving of an unfinished game, the record and its playback, the AI that finishes a game, Watch the game, analysis, picture and music; no editor | the same, also with the editor |
The entrance to Tribes is a tile right after the Principalities in the hub of Kastgard; it is revealed by the first finished game. It opens a screen that shows the map: next to the column with the number of players (2 to 8, 7 at the start), the rules and the Play button there is a small map with a line of facts and a New map button (from 820 px of width next to the column, on a narrower window above it). It is really the map that Play starts: the game gets the same seed, so its first deal is the picture. Changing the number of players gives the same land again; the territories do not move, the owners and dice change. The number of players is the only choice.
An unfinished game is saved, and the record is played back as in the Principalities; the AI that finishes a game plays for the human at the chosen level 1 to 3, and the other seats remain the opponent of the original. The window "Rules of this game" has its own page for Tribes, without an opponent level. Tribes have no editor, no daily challenge and no lessons (DESIGN §133.8 and §133.10).
Map in numbers
The two maps were measured with the tool map-shape.js (150 maps, 7 players, TUNING §44.3). The third column is the island of the free game, for comparison.
| Tribes | Principalities (field) | free game: island | |
|---|---|---|---|
| territories | 30.1 | 42.0 | 42.0 |
| cells in a territory | 20.6 | 13.0 | 7.0 |
| neighbours of a territory | 3.74 | 4.19 | 4.79 |
| dead ends (share of territories) | 0.184 | 0.128 | 0.055 |
| joints (share of territories) | 0.065 | 0.043 | 0.004 |
| weak touches (share of borders) | 0.096 | 0.222 | 0.274 |
| length of the border (edges) | 6.56 | 5.42 | 3.31 |
| aspect ratio | 1.03 | 1.44 | 1.23 |
| fullness (land / its rectangle) | 0.68 | 0.81 | 0.66 |
| holes: per map; size (cells) | 4.0; 9.1 | 10.7; 4.0 | 0.1; 0.1 |
| a stack of 4 / 8 dice does not fit (share of territories) | 0.019 / 0.055 | 0.198 / 0.407 | 0.334 / 0.647 |
A dead end is a territory with at most two neighbours, a joint a territory whose removal would split the map, a weak touch a border one or two edges long; a stack of dice "does not fit" if its rectangle is not entirely inside the territory (the sizes of the stack follow the drawing of the game Audamir). The size of the holes, 9.1, is the mean of 150 maps and came out high (on 1,500 maps of the game it is 7.4 ± 0.2; the explanation is in the article about the source code).
The territories of the original are therefore fewer and larger (30.1 of 20.6 cells against 42.0 of 13.0), have fewer neighbours and longer borders, slightly more dead ends and joints, and dice fit into them: a stack of four dice does not fit into 1.9% of the territories and a stack of eight into 5.5%, while in the field of the Principalities the figures are 19.8% and 40.7%. The drawing of the dice of the original was not measured; the number shows only that the territory is big enough for a stack of the size the game Audamir draws.
Rules of the fight, the turn and the reinforcement: what is the same as in the Principalities
The rules of the fight are what the article Twenty years described from the reviews, and the code confirms them:
- Attack is possible from one's own territory with more than one die onto a neighbouring foreign territory; the number of dice of the target does not limit it. (The description still has a guess that with an asymmetric matrix of neighbours the human checks the direction target → source and the computer source → target; the effect will be small.)
- Fight: each side throws as many dice as its territory has (at most 8, each die 1 to 6), and the sums are compared. The attacker wins only with a strictly higher sum; a tie belongs to the defender.
- After a win the target passes to the attacker with the number of dice of the source minus one, and the source keeps one. After a loss the source keeps one die and the defender does not change.
- Reinforcement: new dice are as many as the largest connected group of territories of the player; they are added to the reserve (at most 64) and placed one by one on random territories of the player with fewer than 8 dice. Unused reserve stays for the next round.
- End of the game: after each fight it is first checked whether the human still has a territory. If not, the game ends at once with a defeat, even in the middle of the computer's turn. Then it is checked whether only one player with territories is left: that is a win.
The players are 2 to 8, 7 by default, and the number of players is the only thing that can be set on the title screen.
Why the Principalities did not change
The map in the game Audamir is a pure function of the seed (Tiles): a saved game carries only the owner and the number of dice of each territory, and the geometry is generated again when it is restored. That is why the generator must not change, since players already have saved games, records, links to the map and backups from it. Changing the Principalities to the map of the original would break all of them. Moreover, the tables of scores, the bands of experience and the achievements are measured on the maps of the Principalities; if the map changed, the measurements would have to be repeated.
That is why Tribes have their own value of the map setting, tribes, which is valid, but never offered: it is not in the editor nor in "Surprise me". No new setting was added (their list still has 29 keys); the type of map carries the dealing and the opponent with it. Most changes are therefore added, not rewritten. There are five invasive places, and they are listed in the documentation so that they can be passed one after another:
- Map generator. The function that makes the outlines of territories and their neighbours received a branch for the new type of map (not a copy of the function); the code of the other types was not touched.
- Settings. The value
tribesmust be valid (a preset, a record and a saved game carry it) and must not be offered: a new hook and a third argument of one function serve this. - Generation of the game. One branch according to the type of map: the dealing of territories and dice and the order of players.
- Opponent. A new value of the level
original, which no setting can produce; levels 1 to 3 and the personalities stayed as they were in the code. - Table of modes. The mode
tribesat first stood without a tile, without an unfinished game, without a record and with an empty list of what is counted. Today it is a row like the other games of Kastgard (tile, unfinished game, record, counting), and the points have their own table.
The full game added interventions beyond the preset (revealing tiles, proofs against the old code, the calibration tool; TRIBES.md §9). According to the documentation of the game, the Principalities, the field, the free game, the daily challenge and the campaign remained bit for bit the same; GEN_VERSION and RULES_VERSION did not change.
Along the way, statements "as in the original" that were not true were corrected: the comment about the preset of the Principalities in the code (then still CLASSIC), a table in the documentation (the original does not shuffle territories, it deals them in the order of creation) and a sentence in DESIGN §67.3 ("the process of the original is not known"). Only the text was corrected; the behaviour of the Principalities stayed. Similar sentences in the blog are handled by adding to the articles Twenty years and Tiles (the section Update).
Proof that nothing moved
The method: produce the data with the old code and read it with the new one. The numbers in the list are from the state of the preset, before the full game; the documentation of the game says that they were repeated at the end of the work, and new numbers are not given here.
- Base of the AI (
baseline.js): 188 of 188 fingerprints the same; 8 more fingerprints of Tribes are added (196 in all). - Golden records (
replay.js --golden, 12) and golden maps (--golden-maps, 3): files the same byte by byte. - Calibration (
calibrate.js --verify): 18 of 18 identical (43,200 games). - Proof with the old code (
classic-maps-migration.js, today the tool is calledprincipalities-maps-migration.js; the old tree fromgit archive): the production of games, records, saved states, scores, codes, profile and backup is the same on 127,013 bytes; 14 records are played again, 7 saved states are restored and the backup of the old storage (11,001 bytes) is restored the same; 14 games of today's draw are fields and their records are played again. - The tests of the Principalities and
field.test.jsare unchanged.GEN_VERSIONandRULES_VERSIONdo not change, because nothing that exists is generated differently. - The whole check (
verify.js) passed on a clean tree: 3,874 tests, of which 45 new, none lost.
With the preset only the tests were changed that lock the whole structure: the table of modes, the list of presets, the number of fingerprints of the base (196) and the layout of the tests (features 92). No test of the Principalities.
What is not verified
What is decided
The answers to ten questions (B1 to B10) of 2 November 2026 made the preset a full game. Decided: Tribes are counted (except the daily challenge); they have their own tile, on which only the number of players is set, and the screen shows the map that Play starts; an unfinished game is saved and the record is played back; the opponent is one, the opponent of the original; the hexagons are regular and the land can be in several pieces, as in the original; the name Tribes / Kmene stays (whether it is free was not searched). Tribes have their own small section of achievements: four chains over the record profile.tribes, eight steps in all. The rewards are 0.75 times the rewards of the Principalities rounded to fives, 445 Golden Dice in all against 580 for four twins. The chains of the Principalities are not counted for Tribes and the other way round. A player who has already played Tribes gets the steps that his record reaches, once, at the first start of the new version; the proof is with data of the old code (123 real games of Tribes). The daily challenge is still not counted for Tribes.
The factor of experience for a win is 0.75: a win pays three quarters of its score in experience. Games won in versions 0.88 to 0.90 are not paid again; they count with factor 1, new ones with 0.75. The pace and its comparison with the field of the Principalities is in the article about the opponent.
Sources and notes
- Numbers:
docs/TUNING.md§44 and §45 in the repository of the game. §44.2 and §44.4:node tools/realms/kastgard/games/stacks/original-map.js --maps 5000 --seed BIG(7 players). §44.3:map-shape.js --maps 150 --players 7 --specs tribes,field,island/0. §44.5 and §44.6:tribes.js --strengthand--compare. §45.2:tribes.js --points. §45.3:node tools/core/xp.js. §45.4:analysis.js --validate --tribes. The numbers are taken from TUNING without recalculation and without other rounding. - Description of the original: the article about the source code and the opponent; the source is the official HTML5 version by GAMEDESIGN, read on 2 November 2026. The code of the original was not copied anywhere; the game and the tools are based on the description in our own words.
- State of the game: development version 0.97.1 (3 November 2026); list of changes of the game: versions 0.87 to 0.92. A release of this version for other players is not claimed here.
- Related articles: Twenty years (year of the release and the authorship), Archaeology of one's own project, Why the starter wins 93%, What a setting costs (AI levels), Tiles (the seed as a contract).