Terry, the guide: Total War: Warhammer III's terrain editor, from your first battle map to campaign terrain

What Terry is, and what it does in the public kit§

Terry (Terrain Metadata Editor) is Creative Assembly's (CA) 3D terrain editor, shipped with the Total War: Warhammer III Assembly Kit. It is where a terrain is made: relief, textures, vegetation, props, logical zones, lighting and sounds. It is not a separate program: it is a mode of Tweak, the kit's editor.

Terry does not write the files the game reads, but sources, in the kit's raw_data folder. BOB, the kit's builder, builds them into working_data; RPFM puts them into a pack. Terry starts BOB itself: File → Process with BOB.

• In the public kit, Terry makes battle tiles and battle maps, with their logic (deployment, playable area, capture points), and prefabs.
• The kit ships no campaign terrain: in the Warhammer III kit, raw_data/terrain/ only holds battles/ and tiles/battle/.
• No command drives Terry: you can only open it; the rest happens in its window.

The journey of a battle map, from Terry to the game:

1. Terry

   You paint the tile (relief, textures, props, logical zones) and place it in a tile map.

   .terry, .layer, .tif, tile_map.png in raw_data

2. BOB

   It builds the tile map, then the tile, into game files.

   working_data/terrain/…

3. RPFM

   The pack: the built files, a battles_tables row, a text, an image.

   my_map.pack

4. In game

   The map appears in custom battle.

This guide follows that journey, then gathers what is known about campaign map terrain.

Terry's vocabulary§

A few words come up everywhere. Here is the meaning this guide gives them.

Opening Terry§

Since Terry is a mode of Tweak, there are three ways in, all leading to the same window.

• From the kit's launcher

  In Steam (Library → Tools), start the Warhammer III Assembly Kit, then pick Play Battle Map Editor: Terry.

  According to the tw-modding wiki's Custom Campaign Settlement Skins page (Warhammer III part, ChaosRobie).

• From Tweak

  Open binaries/tweak.modder.x64.exe in the kit folder, then the Plugins → Terry menu.

  According to the same page.

• From the command line

  From the kit's binaries folder: tweak.modder.x64.exe /standalone TerrainMetadataEditor.

  It is the command the launcher option runs; the only known one for Terry.

How to check. The window is titled TWeak - Terry. It takes a while to come up: about 25 seconds for us. On start-up, the Project Wizard appears.

The Project Wizard§

The Project Wizard appears on start-up (Show on startup box) and reopens with File → Project Wizard…: it offers recent projects and the New tab, which it opens on (tw-modding).

In Warhammer III it shows three icons. The right-hand one, a dotted box, creates a prefab, battle or campaign (tw-modding, Custom Campaign Settlement Skins). The kit only knows three project types: tile, tile_map and prefab, each on a battle or campaign tile database (file working_data/Terry/entity_configuration.xml). So the other two icons are probably the tile and the tile map (see the “What we have not seen on screen” box).

Terry's window§

Terry's window is made of panels that can be detached and docked: the layout is adjustable, and yours may differ. The figure shows a common layout, with numbered markers: menus and toolbars at the top, scene hierarchy on the left, properties at the bottom and on the right, 3D view in the centre, BOB's messages at the bottom right.

A project's files§

• <project>.terry: an XML file describing the project type, its rasters and its scene.
• One .tif per saved raster (<project>.height.<id>.tif, <project>.blend.<id>.tif…): the relief, the texture blend… The kit's example tile declares eight rasters but saves only two.
• The .layer files: one per File Layer, with its entities.
• <project>.terry.user: the preview settings.

In these XML files, a property carries the name it shows in Terry, in lower case, with spaces turned into underscores: Lighting File is written lighting_file. Handy for finding in a file what you set in the window.

Coordinates§

• The Y axis is altitude, pointing up.
• In battle, three extents: the Usable Area, a 2,048 m square centred on the battlefield, where physics and unit pathfinding apply; the tile map, drawn out to 8 km from the centre; the Playable Area (see “Terry's vocabulary”). An 8 × 8 tile is 2,048 m across (read off the kit's example tile): placed in the centre of the tile map, it covers exactly the Usable Area.
• On a campaign map, the axes are those of hex space: see campaign terrain, below.

Getting around: camera and shortcuts§

These shortcuts come from CA's documentation. The keyboard ones are in Terry's shortcut file (working_data/Terry/local/keyboard.xml): a local file, which Terry rewrites and which keeps your own settings; we quote its default keys. The mouse ones come from CA's pages and the kit's status tooltips (working_data/Terry/status_tooltips.xml). Ctrl+S and Ctrl+Shift+S are missing: the file lists “save as” with no key, and “save” not at all.

Two commands have no default key: CopyCamera and PasteCamera. They copy and paste the viewpoint through the clipboard, in the form camv3;eye x;y;z;target x;y;z: a way to compare two states of a terrain from the same angle. To give them one, the ConfigureKeyset command is probably the shortcut settings (its menu label is still to be checked); keys are stored in keyboard.xml.

The painting and creation modes§

Terry works in modes: pick a mode, a tool, then paint or place. The four painting modes are on the Basic toolbar; the creation modes on the Entity Creation toolbar and in the Tools menu.

Relief: Terrain Height Painting§

• Three panels. Maps: the rasters and their layers (Add Layer on right-click), which blend in order. Operations. Brushes: New Round creates a round brush, with Scale, Hardness, Size Jitter…
• Warhammer III operations: Add, Subtract, Absolute, Smooth, Erase.
• To see slopes steeper than 45° in red: Settings → View 3D → Overlay → Land No Gos.

Textures: Terrain Texture Painting§

• Each channel is one of the project's textures (grass01, mud01…).
• A low flow blends textures into one another.
• Operations: Normal, Smooth, Erase, Replace.

Forests: Terrain Forest Painting§

You don't place trees one by one: you paint the forest texture, and forest grows wherever that texture exceeds 60%.

Logical ground: Terrain Painting (Other)§

This mode paints logical ground types: what the game knows about the ground, regardless of the texture you see.

On a campaign map: other rasters, other operations§

A campaign project paints other rasters than a battle tile, and each has its own operations. Terry keeps them in working_data/Terry/local/tool_state.xml (read on 25.09.2026, kit 9.0); the neutral values are those of the Immortal Empires project (read on 21.09.2026).

Placed vegetation (Vegetation) and the Procedural Exclusion Zone are battle-only (entity_configuration.xml): on a campaign map, trees come from the CampaignTree raster.

• CampaignTree's palette is the campaign_tree_ids table (one colour = one tree family); BOB builds the map's tree list from it. BOB only knows the ids in db.pack: for new trees, paint a family the database knows, then rename after BOB.
• A BlendCampaign number is a ground group: a new group only exists for the game if it is declared in a variation catalogue (warscape_asset_variation_db/*.assetdb); otherwise it takes the array's last texture (grey ground). For us, a catalogue of our own, under a name of our own, holding only our keys (the game reads every .assetdb in the folder); never a copy of CA's terrain_textures_campaign.assetdb, which would overwrite another map mod's.

Objects: Entity Creation (Visual)§

• Entities: Prefab, Building, Prop, Decal, VFX, Polygon Mesh, Terrain Hole, Vegetation (Place or Paint), Procedural Exclusion Zone, and lights.
• While placing, [ and ] set the scale; Shift + mouse, the rotation.
• A lake is a water_plane prop, Surface Oriented unticked, placed in a hollow of the relief. Water shallower than 0.5 m stays passable, with a penalty; deeper water is impassable (CA).

Logic: Entity Creation (Logical)§

• Entities: AI Hint, No-Go / Go Region, Deployment Zone, Deployment Zone Region, Playable Area, and, in Warhammer III, capture points.
• The kit keeps these entities for battle projects (entity_configuration.xml). A campaign project has its own: CampaignSettlement and CameraConstraintVolume; lighting zones (EnvironmentVolume) are allowed, as in any tile map.

Advanced tools: Advanced and Other§

A ruler to measure; Snap BBox and Snap Verts to align; the grid and snapping; a perspective or orthographic camera; Sound Marker to place sounds; Camera Bounds, which limits the editor's camera only, not the game's.

Several variants of one map§

A layer can carry an export type (catchment_01…). The catchment_name column of the battles table then picks the variant the game loads. That is how one terrain gives both a domination map and a classic battle.

Your first battle map, step by step§

This walkthrough follows the tw-modding wiki's Warhammer III tutorial, completed with CA's documentation. Two pieces of advice first. Save often: CA warns that Terry sometimes crashes. And set the autosave in Settings (on our install, it was set to 15 minutes). Terry keeps its autosaves in working_data/Terry/local/autosave/ and logs its errors in working_data/Terry/local/terry_error_log.txt, in the kit folder.

An autosave is a numbered folder (001, 002…) holding a full copy of the project, its files renamed autosave.* (autosave.terry, its .tif and .layer files); settings.xml allows 100 of them and warns 15 seconds before each one (settings of our install). We have not yet restored a project from an autosave: before any attempt, copy its folder elsewhere, and keep your project's original.

A first try: the kit's example map§

Before making your own map, you can see the Terry → BOB journey on the example map the kit ships. What we checked in the files: its tile is raw_data/terrain/tiles/battle/test_tiles/assembly_kit_example_tile/ (8x8, a single File Layer, textures grass01, grass02, mud01, mud02, forest01); its tile map is raw_data/terrain/battles/assembly_kit_example_tile_map/, which already places the tile in its centre (no vista, no explicit_tiles to set); their built files ship in working_data, dated the day the kit was installed. It has no row in the battles table: it does not show up in game on its own.

1. Keep a copy of the example map's two folders, outside the kit, before touching them.
2. Open the tile (File → Open…, Ctrl+O), raise a hill with Terrain Height Painting, then save (File).
3. Build: Process with BOB on the tile map, then on the tile.
4. Check: binaries/bob.log ends with Exit code: 0, and the tile's outputs in working_data/terrain/tiles/battle/test_tiles/assembly_kit_example_tile/ carry today's date.

This try applies the rules of the walkthrough below; we have not done it as such, nor taken it into the game. To see a map in game, you have to declare it as in the RPFM section, further down; the walkthrough makes a map of your own, on the same model.

Your map, step by step§

A battle map is two Terry projects. The tile is the ground where the fighting happens, which you paint in detail; the tile map is the scenery around it, drawn out to 8 km (CA), which you borrow from a vista. Only a 2,048 m square in the centre, the Usable Area, has physics and unit pathfinding (CA). The figure shows both projects one above the other, with their files, BOB's two runs and the battles_tables row that links it all to the game.

1. Create the project. In the Project Wizard, on the New tab, choose a battle tile. The exact label of that choice is not confirmed in Warhammer III.
2. Save it straight away (File → Save As…): the dialog asks for the map name, in lower case (a folder name, not the name shown in game); the tile set, a folder name of your own, in lower case (the tutorial, which makes a domination map, calls it domination); the size, 8x8, to stay compatible with Warhammer II's tile maps; the climate (which drives, among other things, grass and trees). Leave the bottom box ticked, as the tutorial says (its label is not confirmed here). Check: going by the kit's example map, the tile is stored in raw_data/terrain/tiles/battle/<tile set>/<map>/. The Show in Explorer button opens the folder: a .terry, at least one .layer, some .tif files.
3. Paint the relief, textures and forests, then place the props. To make the map lighter, the tutorial places a Procedural Exclusion Zone between the playable area and the tile's edge: no more grass outside play, but no more trees in that band's forests either; it repaints them by hand. Check in World View (G key), the game-like preview, and with H, the coloured relief.
4. Place the logic, with Tools → Entity Creation (Logical). A Playable Area: 2x2 to 3x3, the tutorial advises, without giving the unit; without one, the game sets it between 800 and 1,300 m depending on the number of units, or fits it to the deployment zones, whichever is larger (CA). Two Deployment Zones, each with its additive Deployment Zone Region: Alliance ID 0 for the attacker, 1 for the defender, Zone ID at 0. In Warhammer III's Terry, alliance 0 shows in blue and 1 in dark red (CA's 2016 documentation had it the other way round): trust the number. For a domination map, capture points: type domination 1/2/3, importance score, from 80 × 80 to 180 × 180; the tutorial adds a second region to each deployment zone, of type guerilla exclusion additive, for vanguard deployment (the opposite alliance cannot deploy in it), and makes sure no player can vanguard-deploy onto a capture point. And reinforcement lines: an attacker or defender teleport reinforcement line AI Hint, a short two-point line; about 20 units long is enough, the tutorial says. Check: the zones show in the 3D view, and the Project Errors panel reports nothing.
5. Create the tile map with Tools → Create battle for tile…: Terry creates its project in raw_data/terrain/battles/<map>/. Once is enough, the tutorial says; after that you work in the files it created. Check: the folder holds a .terry, tile_map.png, climate_map.png and explicit_tiles.
6. Place your tile in the tile map. In that folder, replace tile_map.png and climate_map.png with those of an existing vista, a ready-made tile map that will serve as scenery. Then, in explicit_tiles, change the first two numbers of the line x,y,tile path,0 (see right after the list): x,y is your tile's top-left corner in tile_map.png, in pixels. An 8 × 8 tile in the centre of a 64 × 64 tile map goes at 28,28; the kit's example map has its own in the same place.
7. Build the tile map: open it in Terry, run File → Process with BOB (Ctrl+P, or the globe on the Basic toolbar), then reload it. Check: your tile is in its place.
8. Build the tile. Reopen it. In Map Properties, untick legacy vegetation generation (in the .terry, the use_legacy_procedural_vegetation property). Then Process with BOB. The tile map always comes before the tile; after that, when you touch up the tile, only the tile needs re-exporting.
9. Declare the map to the game with RPFM: see the next section.
10. Test it in a custom battle, with the pack enabled in the launcher.

By default, the tutorial says, explicit_tiles holds something like this:

3,3,terrain/tiles/battle/lzd_hills_infield/chaqua_pit,0

Change only the first two numbers. x,y are read in pixels of tile_map.png, x from the left, y from the top: open the image in your drawing program and point at the top-left corner of the vista's black square, that is 28,28 in a 64 × 64 tile map (tutorial). Check that the path is your tile's, from terrain/, with forward slashes; keep the final 0.

The kit's example map places its tile differently: its tile (raw_data/terrain/tiles/battle/test_tiles/assembly_kit_example_tile/) declares the colour (0, 255, 127) in its .terry, and its tile map's tile_map.png, 64 × 64 pixels, carries a block of it from 28,28 to 35,35, without explicit_tiles.

Declaring it to the game with RPFM, and testing it§

BOB has produced the game files. What remains is to put them in a pack and tell the game the map exists: that is the job of a battles_tables row, a text and an image. RPFM does all of it; its basic moves are in the RPFM guide.

1. Create a pack and add the working_data/terrain folder to it, as the tutorial does, then remove everything that is not yours: the kit's example map (assembly_kit_example_tile_map, assembly_kit_example_tile, _tile_database/TILES/test_tiles_assembly_kit_example_tile.*) and any game file you may have extracted there. Check in RPFM that only your folders remain: the tile map, the tile and its _tile_database/TILES/<tile set>_<map>.* entry.
2. Add a row to battles_tables: right-click the pack → Create… → Create DB → battles_tables, a file named after you (never data__, which would replace the game's table); copy a classic row from the game, Paste as New Row, and change the key first (the RPFM guide). That way you keep every column; fill them in from the table below.
3. Add the text battles_localised_name_<key>: it is the name the player will see.
4. Add the image at the path given by screenshot_path: three times as wide as it is tall (tutorial). The space in frontend ui is intended.
5. Save the pack, then PackFile → Install in RPFM, which copies it into the game's data folder. A square image with the same name as the pack serves as its thumbnail (the tutorial plans it for the Workshop). Then enable the pack in the launcher.
6. Test with a custom battle. A domination map is tested in multiplayer, or with a community mod (see the tw-modding tutorial).

Campaign map terrain: what we know§

For a campaign map, the kit ships nothing: no Terry project, no raw terrain data. That is true of the Warhammer III kit, and of the Warhammer I kit. Yet Terry can open a campaign project: to Terry it is a tile map (QTU::ProjectTileMap) on the campaign tile database, with terrain_setup="terrain/campaigns/<map>/"; ChaosRobie calls it a “campaign-type Terry project”. ChaosRobie, the author of Immortal Empires Expanded, proved it: he rebuilt the Immortal Empires map as a Terry project, and shared that project with the community. Here it is, dissected: it is the blueprint to follow.

Remember that the project is tied to the map's list of regions: one more region means one more File Layer, that is an ECFileLayer entity in the .terry and its <map>.<id>.layer file. The logical half (regions, ground, roads, towns) is made in CAIME (Campaign AI Map Editor), the Campaign Map Toolkit's editor: the CAIME guide.

The project's settings§

The .terry's first block, QTU::ProjectTileMap, carries these four settings among others, read in both projects (September 2026):

Raster sizes follow from the number of hexes§

Every resolution is proportional to the map's number of hexes, the CAIME one (read from ChaosRobie's project and applied to our map). The last column gives the example of our map, 400 × 440 hexes.

The arithmetic: 400 × 8 = 3200 pixels wide, 440 × 8 + 4 = 3524 high. For the patches, the tile map is 800 × 881: p = ceiling(881 / 128) = 7, and you count whole patches (800 / 7 gives 114, 881 / 7 gives 125).

In the folder, each raster has its file <map>.<name>.<id>.tif, where the name is not the type's (read off both projects):

Campaign terrain: conventions, BOB's order and limits§

Conventions§

They were established by reading ChaosRobie's project and trying them on our own (September 2026); CA does not document them.

• Rasters run north to south; heights are in world units, water at 0. Each compiled file has its own direction: full_height_map.dds runs south to north, lf_normal.dds and camera_heightmap.png north to south; check it by correlating with the heights before making one.
• x points east, z north, and the world is hex space. Rasters have square pixels, but campaign world space is deeper: Terry stretches them by 2/√3 along z. A world point (x, z) therefore maps to raster position z × √3/2 (in world units, not pixels). For us: 338.9 units of world depth for 293.5 units of raster.
• The sea is declared in tile_map.png (sea tile, colour 83, 141, 213), not by height. The sea floor (HeightSea) must stay below 0 wherever there is sea: if it rises above the water meshes, it hides them. There is no seabed tile under land, so its value there makes no difference (ChaosRobie, 26 September 2026).
• The sea surface is made of large water planes placed as objects: Polygon Mesh entities (ECPolygonMesh) with the map's water material, at height 0; Immortal Empires has 997 of them. Without them, no water on the sea, even with the floor below 0 (seen on 23.09.2026). Their pivot must be inside the map, or BOB drops them (“Failed to find valid quadtree node”). Draw each water plane whole, then cut it exactly: tiles drawn separately leave a waterless slit a quarter of a hex wide at the cuts.
• The tile-map coast: export tile_map.png from CAIME (Tools → Export → Baseline Tilemap), without painting or retouching it. With CAIME 1.1.0 or later, the image comes out north-up; up to 1.0.1, it comes out upside down (south at the top): flip it vertically, and only that (check: its coast lies over the PNG export of the Ground Types layer). For Warhammer III, the export gives coastal land cliff_gen (253, 3, 1), beach transitions cliff_gen_ends (84, 230, 84), and beaches without roads sea_coast (255, 255, 0). Our old pixel-level retouching caused 148 “Failed to find tile” warnings; shape the visual shore in Terry and judge it in game.
• Cliff ends: CAIME puts two cliff_gen_ends around every beach, whereas CA's Immortal Empires map has only 36 for 412 beaches, most beaches joining the cliff directly. An end can be laid two ways; bound to the beach, it leaves a tile hole on the cliff side (at CA, all 36 are bound to the cliff, no hole). “Exported without retouching” stays the general rule; on our Saison Expanded map, these ends are repainted as cliff_gen, a departure we own. No cliff or beach on row 0, the last row or the last column of the grid, and no one-hex isthmus where two cliffs cross: no coast tile exists there.
• A river mouth is marked Beach AND River in CAIME: on export, every coastal land hex that is not a beach becomes a cliff, rivers included; without it, the river ends on a cliff and never reaches the sea.
• Roads: CAIME exports a solid 2 × 2 pixel roads block (93, 66, 24) per road hex after sea and coastal cliffs take priority. A road on a beach takes priority over the beach.

The tile_map.png legend is in the campaign tile database, terrain/tiles/campaign/_tile_database/_settings.bin, a binary file. The colours we read in it (21.09.2026, patch 8.1):

A colour in the legend is not enough: only the families present in working_data/terrain/tiles/campaign/ have tiles, and the database has a single river tile.

• Rivers: Warhammer III has almost no river tiles left. Its rivers are meshes placed as objects, or sea channels lined with coast.
• Starting from CAIME: the CAIME guide has CAIME export tile_map.png (Tools → Export → Baseline Tilemap) for the Terry project. In Warhammer III, ordinary rivers use generic and river mouths (hexes marked Beach and River) use sea_coast: no river tile is requested (BaselineTilemapExporter.cs). Count the “Failed to find tile” warnings after the first run.
• What the kit lacks (the campaign tile database, terrain/tiles/campaign/_tile_database, with the legend of tile_map.png's colours; the lighting; the sea materials) is extracted from the game's packs with RPFM.

The order of runs§

The tw-modding tutorial on campaign maps gives this order, run by run in BOB's window; the details, which are the reference, are in the BOB guide. From Terry, a single Process with BOB selects all the terrain's actions at once (12 in a full successful run; 15 on 21.09.2026, when Generate Camera Height Map was requested, and it crashes BOB):

1. The relief first: the next steps depend on it and read it from your pack. Put it in your pack (the tutorial says “your pack”; for us, BOB mounts the packs in <game>\data and in assembly_kit\working_data), then close and reopen BOB.
2. The tile map: into the pack again, then close and reopen BOB.
3. The global tile map (roads and cliffs).
4. global_props.bin, the placed objects: redo it whenever a region is added or removed (BOB then reads CAIME's map.hex); up to ten minutes on a large map, the tutorial says.

From Terry, each Process with BOB starts a new BOB. After each run, read bob_warnings.log, in assembly_kit/binaries/, and count the “Failed to find tile”: each one is a hole in the terrain. Check bob.log too: its first line states how many actions were selected (N action(s) were selected for execution.), and each finished action has its (STATUS: Finished) line; how many to expect: see the limits, below. Aim for zero “Failed to find tile”, except on the last row of a campaign's battle terrain, outside the grid and harmless (1 for us on the Season, 3 on Expanded). Finally, look in working_data/terrain/campaigns/<map>/: the built relief (full_height_map.dds), tile_list.bin and global_props.bin.

Known limits§

• Six actions out of twelve. A full successful run on a campaign terrain has 12 actions (our successful runs of September, kit 9.0, and October, kit 9.0.2; 15 if Generate Camera Height Map is requested, and that action crashes BOB). Durations we recorded (patch 8.1): on 21.09.2026, the first full build took about 26 minutes, about 25 of them compressing the relief; that same evening, under a minute, relief included according to our notes; on 22.09.2026, 53 to 64 seconds. For a map that the game's database (the one in CA's packs) does not know, BOB runs only 6 of them, without a message: the placed objects (global_props.bin, global_props_sound.bin) and five masks, with no relief, tiles, textures, logic map or shroud (the objects alone take 11 to 24 seconds for us). According to our investigation of 21.09.2026 (kit 8.1), BOB looks up the terrain folder's name in the campaign_map_playable_areas table of that database, the one in db.pack; adding the map to the kit's database or to a mod pack changes nothing. As a result, a project that modifies a CA map, in a folder named after that map (such as wh3_main_combi_map_1 for Immortal Empires Expanded), should get all its actions (deduced from BOB's DLL, not tried); a new map does not. We know of no official way to lift this limit: make a control case, then ask the community. A control case is a known-good project copied under another name: if it also stops at 6 actions, your project is not the cause (ChaosRobie's project, copied under another name, stops there). Our new maps got their 12 actions through a tool of ours, outside the official routes, owned as such: BOB run under a debugger (the BOB guide).
• “Generate Camera Height Map”: our finding (21.09.2026, kit 8.1) is that this action crashes BOB; the tutorial, for its part, writes that Terry should be able to produce this map but crashes when you try. The camera height map (camera_heightmap.png) is approximated by the tutorial from the relief, scaled, setting a tEXt block of the PNG to the right value; the corruption mask is painted by hand or by script.
• As long as no built terrain exists, Terry crashes when opening the project in 3D (seen on patch 8.1, not rechecked since): untick 3D View in the opening dialog (Open…).
• A campaign has two terrains: its own, and a battle terrain declared by its campaign playable area (terrain_folder column, terrain/battles/<folder>/). Without it, the game crashes at the first land battle, even between two AIs, so often at the very first end of turn. It is a battle tile map, which BOB builds as such; CA's also carries battle locations and catchment maps.

The full story of a port, walls included: the porting tutorial.

Terry's pitfalls§

First, the working_data lock, in four cases:

• An open Terry locks working_data, including the packs placed there. Before running BOB from its own window, or saving a pack into working_data, close Terry and the game; Process with BOB, started from Terry, is not affected.
• Tweak and Terry closed during CAIME's exports: during CAIME's Map Data and Dynamic Resources exports, Tweak and Terry must be closed (Terry is a mode of Tweak). Don't rely on CAIME's warning: it looks for a program named Tweak.AssemblyKit, whereas the Warhammer III kit's one is called tweak.modder.x64.exe.
• The preview is not the game: every culture variant shows at once; decals are white spheres; campaign tree-map forests only show if the matching preview option is on (show_campaign_tree_map, in the Settings; off on our install), and only for tree families the kit's database knows; map-specific textures are ignored; water is rendered differently. All of that is judged in game.
• Create battle for tile…: once per map is enough. What a second run would do to a folder you have edited is not documented: don't rerun it on a tile map you have changed.
• Without .terry.user, a campaign preview has neither water nor trees: that small file, next to the .terry, holds the preview settings.
• CA's documentation dates from the first Warhammer. Its Export Map has become Process with BOB, followed by RPFM; and the deployment zone colours have swapped (see step 4 of the walkthrough): trust the Alliance ID, never the colour.
• The Defensive Hill AI Hint must be a closed polygon, or a crash is likely.
• BOB rewrites its outputs on every run: a manual touch-up in working_data disappears on the next run.
• Snow since 9.0: the Immortal Empires snow material (combi_campaign_snow.xml.material) no longer cites a mask; the game binds the campaign's own snow_mask.dds by itself. Don't copy a snow material for each map.

For an AI reading this page§

If you are an AI helping someone use Terry, here are the essentials, checked on a real project. These facts were gathered on the game's patch 8.1 (September 2026), then reviewed for update 9.0 (for us, the kit update rewrote the raw_data\db tables, some working_data files (including Terry/entity_configuration.xml and the Terry/new_battle_tile_template/ tile template) and BOB's DLLs; our projects in raw_data/terrain were untouched). Update 9.0.2 replaced BOB and Terry again and rewrote raw_data\db; a terrain run was rechecked there on 04.10.2026 (12 actions, code 0). Any update can do it again: count your rows, then make a control run, and check these facts again.

• Ask the human before launching the game, driving the screen or publishing; delete nothing: tidy away, only the human deletes.
• Reading and documenting a file format, as RPFM and CAIME do: yes. Altering CA's programs or working around their limits: no, with one exception the workshop owns, stated plainly in the BOB guide: BOB run under a debugger for a new map's terrain. When a tool gets stuck, a control case, then the community (CAIME's Discord, tw-modding).
• Terry is a mode of Tweak. Assembly Kit Steam launcher: Battle Map Editor: Terry = tweak.modder.x64.exe /standalone TerrainMetadataEditor, from binaries (window TWeak - Terry, about 25 s); Exporter: BOB = bob.modder.x64.exe -no_console; Database Editor: Dave (Dave, which CA spells DaVE). No command drives Terry; no guessed options.
• BOB opens from the Assembly Kit's Steam launcher (Exporter: BOB), from its executable bob.modder.x64.exe, or from Terry (Process with BOB, Ctrl+P), which hands it the work. BOB has no command-line help; two official command lines are known, those of its launchers: -no_console (Steam launcher) and the one Terry passes to it (see the tools guide).
• Public kit: battle tiles only. Tile: raw_data/terrain/tiles/battle/<tile set>/<map>/; tile map: raw_data/terrain/battles/<map>/, created by Create battle for tile… (once is enough); BOB on the tile map, then on the tile.
• explicit_tiles: the x,y,path,0 line already exists (tutorial): change its x,y, in pixels of tile_map.png, x from the left, y from the top (the tile's top-left corner); path from terrain/, with forward slashes. 8 × 8 tile in the centre of a 64 × 64 tile map: 28,28, as in the kit's example map.
• Alliance ID 0 = attacker, shown in blue in Warhammer III's Terry; 1 = defender, in dark red (CA's 2016 documentation says the opposite). Trust the number, never the colour.
• battles_tables: copy a game row, Paste as New Row, change the key first; table file never named data__. specification = terrain/battles/<map>/; battle_environment = an .environment_group from weather/battle/; screenshot_path image in 3:1 format; text battles_localised_name_<key>.
• Terry's logs: working_data/Terry/local/terry_error_log.txt; autosaves in working_data/Terry/local/autosave/ (every 15 minutes on our install, set in settings.xml).
• Campaign: project to create in raw_data/terrain/campaigns/<map>/; to Terry, a tile map (QTU::ProjectTileMap) on the campaign tile database (.terry version 27, one File Layer per region, named after its key; other File Layers are allowed). The rules.bob recipe is in the parent folder, raw_data/terrain/campaigns/rules.bob; the one in the map folder only copies ([Copy]). world_width = for us the maxx of the campaign playable area; the game does not read the .terry's water_plane_material (sea material: terrain_textures_campaign.assetdb).
• Rasters: 8 px per hex (+ 4 rows), HeightShroud 4 (+ 2), trees, corruption, snow and tile_map.png 2 (+ 1). PatchVisibilityMask: one cell per patch of p tile-map pixels, p = ceiling(longest side / 128), i.e. (width // p) × (height // p) cells.
• Sea declared in tile_map.png (sea, 83, 141, 213), floor below 0 at sea (irrelevant under land), surface as Polygon Mesh entities with the water material at 0, each plane drawn whole then cut. Export tile_map.png from CAIME without manual retouching (north-up since CAIME 1.1.0; up to 1.0.1, flip it vertically, and only that): coasts and transitions, roads as 2 × 2 blocks, rivers as generic, river mouths marked Beach and River. CAIME puts two cliff_gen_ends around every beach (CA: 36 for 412 beaches); an end bound to the beach leaves a hole on the cliff side. No coast on row 0, the last row or the last column, nor a one-hex isthmus between two cliffs. Smooth coast: for a coast without coast tiles (generic), slope the bank over about one unit, with no one-pixel step or cliff on the shoreline (ChaosRobie and our project); with CAIME's coast tiles, relief continuous and smooth under the sea, shoreline in the tiles and the floor only, no channel dug into the relief (as CA).
• Props: mountains and cliffs as props with CA's materials (68, 86 or 97); the tiles' material 49 is the named cause of our rendering crash (9.0.2, a lead, not a proof). Trees: CampaignTree palette = campaign_tree_ids, db.pack ids only; no tree beyond z = world_width × 2/√3. Ground: a new group is declared in a .assetdb catalogue of your own. Direction: full_height_map.dds south to north, lf_normal.dds and camera_heightmap.png north to south.
• Order of campaign runs: the relief, put it in the pack (BOB mounts the packs in data and working_data), close and reopen BOB; the tile map, into the pack, close and reopen BOB; the global tile map; global_props.bin, to redo whenever a region is added or removed (it reads the map.hex). The tutorial says restart: you close BOB and reopen it, you don't just “rerun” it.
• A full successful run on a campaign terrain has 12 actions (15 if Generate Camera Height Map is requested, and it crashes BOB). For a map that the game's database (the one in CA's packs) does not know, BOB runs only 6, without a message; adding the map to the kit's database or to a mod pack changes nothing (seen on 21.09.2026: BOB looks up the terrain folder's name in campaign_map_playable_areas of db.pack; a CA map modified under its own name should get all its actions, not tried). No known official way: a control case, then the community; our route, outside the official ones, is BOB under a debugger (the BOB guide). Never promise 12 actions for a new map through the official routes.
• Before running BOB from its own window, or saving a pack into working_data, close Terry and the game; Tweak and Terry closed during CAIME's Map Data and Dynamic Resources exports. Read binaries/bob.log and binaries/bob_warnings.log. Judge in game, not in the preview.
• Details: BOB, RPFM, CAIME, the modder's tools, modding with an AI.

Sources and links§

• Creative Assembly wiki, pages written for the first Total War: WARHAMMER's kit (some labels have changed since): Terry introduction, Terry contents, interface, shortcuts, quick start, including zones, navigating the viewport, painting and saving, and Rules.bob.
• tw-modding wiki: Map Making for WH3 (WakaWaka300), Campaign Map Making for Warhammer III, Custom Campaign Settlement Skins (Warhammer III part, ChaosRobie), RPFM For Dummies, and, for Warhammer II, Land Battle Maps and Custom Vistas.
• The Warhammer III Assembly Kit's files, read only: Terry's settings, tools and shortcuts (settings.xml, tool_state.xml, keyboard.xml, status_tooltips.xml, entity_configuration.xml), the kit's rules.bob files, the example map, the battles table (battles.xml, on patch 9.0).
• The Immortal Empires Expanded campaign Terry project, shared by ChaosRobie, and our own project.
• Our other guides: BOB, RPFM, CAIME, the modder's tools, modding with an AI; and the modders' workshop.

Frequently asked questions