Basecamp

Recommended reading

Basecamps leverage many existing aspects of JSON data such as recipes and mapgen. It’s recommended to be familiar with those:

• JSON info has information on common fields for recipes
• mapgen, see section 3 about update_mapgen

Adding alternate basecamp upgrade paths

A basecamp upgrade path is a series of basecamp upgrade missions that upgrade the camp. Upgrade missions are generally performed sequentially, but there is an option to have them branch. Branched missions optionally can have further missions that require missions from other branches.

Basecamp upgrade paths are defined by several related files:

• The recipe JSONs that define what the material, tool, and skill requirements to perform an upgrade mission and the blueprint mapgen, blueprint requirements, blueprint provides, and blueprint resources associated with each upgrade mission.
• The mapgen update JSONs that define how the map will change when the upgrade mission is complete. These may include shared instances of nested mapgen, such a standard room or tent.
• The recipe_group JSONs that define what recipes can be crafted after completing the upgrade mission and what camps and expansions are available.

recipe JSONs

The recipe JSONs are standard recipe JSONs, with the addition of a few fields.

New field	Description
"construction_blueprint"	string, the "update_mapgen_id" of the mapgen update JSON that will be performed when the upgrade mission is complete.
"construction_name"	string, a short description/name of the upgrade mission that is displayed in the base camp mission selector. The recipe’s "description" field has the extended description that explains why a player might want to have an NPC perform this upgrade mission.
"blueprint_provides"	array of objects, with each object having an "id" string and an optional "amount" integer. These are the camp features that are available when the upgrade mission is complete. Every upgrade mission provides its recipe "result" with an amount of 1 automatically and that string does not need to be listed in "blueprint_provides".
"blueprint_requires"	array of objects, with each object having an "id" string and an optional "amount" integer. These are the camp features that are required before the upgrade mission can be attempted.
"blueprint_excludes"	array of objects, with each object having an "id" string and an optional "amount" integer. These are the camp features that prevent the upgrade mission from being attempted if they exist.
"blueprint_resources"	array of "itype_id"s. Items with those ids will be added to the camp inventory after the upgrade mission is completed and can be used for crafting or additional upgrade missions.
"blueprint_parameter_names"	defines human-readable names for any parameter values for this recipe, when used with parametric mapgen.
"blueprint_needs"	object which defines the requirements to build this blueprint. If not given, the game will attempt to autocalculate the needs based on the associated mapgen definition, so usually you need not specify "blueprint_needs".

blueprint requires, provides, and excludes

blueprint requires, blueprint provides, and blueprint excludes are abstract concepts or flags that an upgrade mission requires to start, or that are provided by a previous upgrade mission to satisfy the blueprint requirements of a current upgrade mission, or that prevent an upgrade mission from being available. Each one has an "id" and an "amount". Multiple requires, provides, or excludes with the same "id" sum their "amount" if they’re on the same basecamp expansion.

Every upgrade mission has its recipe "result" as a blueprint_provides and a blueprint_excludes, so upgrade missions will automatically prevent themselves from being repeatable.

These are arbitrary strings and can be used to control the branching of the upgrade paths. However, some strings have meaning within the basecamp code:

Provides "id"	Meaning
"bed"	every 2 "amount"’ of "bed" allows another expansion in the camp, to a maximum of 8, not include the camp center.
"tool_storage"	after this upgrade mission is complete, the Store Tools mission will be available.
"radio"	after this upgrade mission is complete, two way radios communicating to the camp have extended range.
"pantry"	after this upgrade mission is complete, the Distribute Food mission is more efficient when dealing with short term spoilage items.
"gathering"	after this upgrade mission is complete, the Gather Materials, Distribute Food, and Reset Sort Points basecamp missions will be available.
"firewood"	after this upgrade mission is complete, the Gather Firewood basecamp mission will be available.
"sorting"	after this upgrade mission is complete, the Menial Labor basecamp mission will be available.
"logging"	after this upgrade mission is complete, the Cut Logs and Clear a Forest basecamp missions will be available.
"relaying"	after this upgrade mission is complete, the Setup Hide Site and Relay Hide Site basecamp missions will be available.
"foraging"	after this upgrade mission is complete, the Forage for Plants basecamp mission will be available.
"trapping"	after this upgrade mission is complete, the Trap Small Game basecamp mission will be available.
"hunting"	after this upgrade mission is complete, the Hunt Large Animals basecamp mission will be available.
"walls"	after this upgrade mission is complete, the Construct Map Fortifications basecamp mission will be available.
"recruiting"	after this upgrade mission is complete, the Recruit Companions basecamp mission will be available.
"scouting"	after this upgrade mission is complete, the Scout Mission basecamp mission will be available.
"patrolling"	after this upgrade mission is complete, the Combat Patrol basecamp mission will be available.
"dismantling"	after this upgrade mission is complete, the Chop Shop basecamp mission will be available.
"farming"	after this upgrade mission is complete, the Plow Fields, Plant Fields, Fertilize Fields, and Harvest Fields basecamp missions will be available.
"reseeding"	after this upgrade mission is complete, recipe groups with "building_type": "FARM" will become visible.
"kitchen"	after this upgrade mission is complete, recipe groups with "building_type": "COOK" will become visible.
"blacksmith"	after this upgrade mission is complete, recipe groups with "building_type": "SMITH" will become visible.
"water_well"	after this upgrade mission is complete, the camp will have a permanent water source. This enables your followers at or near the camp to automatically drink from its well when they are thirsty.

blueprint_provides can also be used to name objects from recipe_group.json. The recipes will be craftable by NPCs at that expansion, allowing the creation of custom recipes that can be performed exclusively at faction camps.

Sample recipe JSON

  {
    "type": "recipe",
    "result": "faction_base_camp_8",
    "description": "We need to expand our base to include basic dining facilities.",
    "category": "CC_BUILDING",
    "subcategory": "CSC_BUILDING_BASES",
    "skill_used": "fabrication",
    "difficulty": 5,
    "autolearn": false,
    "never_learn": true,
    "comment": "2hrs*4wall + .5 hr*2tables + .5hr*4benches+ 1hrs pits = 12 hrs (12hrs on/off) 1 days total",
    "time": "1440 m",
    "construction_blueprint": "faction_base_field_camp_8",
    "blueprint_name": "basic central kitchen",
    "blueprint_resources": [ "fake_stove" ],
    "blueprint_provides": [ { "id": "trapping", "amount": 1 }, { "id": "hunting", "amount": 1 }, { "id": "walls", "amount": 1 }, { "id": "recruiting", "amount": 1 } ],
    "blueprint_requires": [ { "id": "faction_base_camp_6", "amount": 1 } ],
    "qualities": [ [ { "id": "DIG", "level": 1 } ], [ { "id": "SAW_M", "level": 1 } ], [ { "id": "HAMMER", "level": 2 } ] ],
    "components": [ [ [ "2x4", 28 ] ], [ [ "log", 16 ] ], [ [ "nail", 56 ] ], [ [ "stick", 24 ] ], [ [ "metal_tank", 1 ] ], [ [ "pipe", 1 ] ] ]
  },

The "faction_base_camp_8" upgrade mission can be performed after "faction_base_camp_6" and enables the trapping, hunting, fortification, and recruiting basecamp missions. It adds a camp stove to the camp’s inventory to represent the iron stove.

"blueprint_autocalc": true could be used instead of components to let the cost be calculated automatically from the mapgen_update data.

mapgen update JSON

These are standard mapgen update JSON; see the MAPGEN docs for more details. Each one should change a localized portion of the camp map and should, as much as possible, be independent of any other pieces of mapgen update for the basecamp upgrade path. Obviously, some bits are going to expand other bits, in which case their "blueprint_requires" should include the "blueprint_provides" of the previous upgrade missions.

Sample mapgen update JSON

  {
    "type": "mapgen",
    "update_mapgen_id": "faction_base_field_camp_7",
    "method": "json",
    "object": { "place_nested": [ { "chunks": [ "basecamp_large_tent_east" ], "x": 2, "y": 10 } ] }
  },
  {
    "type": "mapgen",
    "method": "json",
    "nested_mapgen_id": "basecamp_large_tent_east",
    "object": {
      "mapgensize": [ 5, 5 ],
      "rows": [
        "WWWWW",
        "Wbb$W",
        "Wr;;D",
        "Wbb$W",
        "WWWWW"
      ],
      "palettes": [ "acidia_camp_palette" ]
    }
  },

This mapgen update places a large tent in the west central portion of the camp. The "place_nested" references a standard map used in the primitive field camp.

Parametric mapgen

It is common to have many similar versions of upgrades which differ only in some details. For example, building the same structure with different materials.

In this situation, you can define multiple upgrade options with a single recipe and a single mapgen update. This works as follows.

Put one or more mapgen parameters in the mapgen update. Mapgen parameters are documented in the MAPGEN docs. Each parameter should be at OMT scope and have a set of options defined e.g. via "distribution", but the weights of the different options do not matter; the player will choose between them rather than a random choice.

For the player to make this choice we also need human-readable (and translatable) descriptions of the parameter options. Those go in the recipe.

For example, suppose this was your mapgen definition:

{
  "type": "mapgen",
  "method": "json",
  "nested_mapgen_id": "fbmh_2_generic_room_1_1",
  "object": {
    "parameters": {
      "fbmh_2_generic_palette": {
        "type": "palette_id",
        "scope": "omt",
        "default": { "distribution": [ "fbmh_2_log_palette", "fbmh_2_migo_resin_palette" ] }
      }
    },
    "mapgensize": [ 6, 6 ],
    "rows": [
      "  wwww",
      "  ...w",
      "    .w",
      "      ",
      "      ",
      "      "
    ],
    "palettes": [ { "param": "fbmh_2_generic_palette" } ]
  }
}

That defines one parameter with two options.

Then in the recipe definition provide human-readable names for the parameters via "blueprint_parameter_names". This is a JSON object whose keys are the parameter names. Each value is itself a JSON object whose keys are the options for that parameter, and values are the human-readable descriptions of what that parameter means. These descriptions will appear in the basecamp upgrade menu. For example:

{
  "type": "recipe",
  "activity_level": "MODERATE_EXERCISE",
  "result": "fbmh_2_generic_room_1_1",
  "description": "We need some shelter, so build half of a shack with a roof on the northeast side of the camp",
  "category": "CC_BUILDING",
  "subcategory": "CSC_BUILDING_BASES",
  "autolearn": false,
  "never_learn": true,
  "construction_blueprint": "fbmh_2_generic_room_NE_1",
  "blueprint_name": "northeast shack",
  "blueprint_parameter_names": {
    "fbmh_2_generic_palette": {
      "fbmh_2_log_palette": "Log walls and wooden roof",
      "fbmh_2_migo_resin_palette": "Mi-go resin walls and roof"
    }
  },
  "blueprint_requires": [ { "id": "fbmh_2" } ],
  "blueprint_provides": [ { "id": "fbmh_2_room_NE" } ],
  "blueprint_excludes": [ { "id": "fbmh_2_room_NE" } ]
}

Since each different choice of parameters would naturally lead to different requirements, you cannot provide "blueprint_needs" to a parametric recipe; the needs must be autocalculated.

Recipe groups

Recipe groups serve two purposes: they indicate what recipes can produced by the camp after an upgrade mission is completed, and they indicate what upgrade paths are available and where camps can be placed.

There are two special recipe groups, "all_faction_base_types" and "all_faction_base_expansions". They both look like this:

  {
    "type": "recipe_group",
    "name": "all_faction_base_expansions",
    "building_type": "NONE",
    "recipes": [
      { "id": "faction_base_farm_0", "description": "Farm", "om_terrains": [ "field" ] },
      { "id": "faction_base_garage_0", "description": "Garage", "om_terrains": [ "field" ] },
      { "id": "faction_base_kitchen_0", "description": "Kitchen", "om_terrains": [ "field" ] },
      { "id": "faction_base_blacksmith_0", "description": "Blacksmith Shop", "om_terrains": [ "field" ] }
    ]
  },

Upgrade Paths and Expansions

All recipes that start an upgrade path or expansion should have a blueprint requirement that can never be met, such as "not_an_upgrade", to prevent them from showing up as available upgrades. Additionally, if you want to add an expansion, you must create an OMT with the same id as the expansion’s id. If the player attempts to start a basecamp on an overmap terrain that has two or more valid basecamp expansion paths, they will allowed to choose which path to start.

Each entry in the "recipes" array must be a dictionary with the "id", "description", and "om_terrains" fields.

—- Field —-	——————————————————————————————————— Description —————————————————————————————————————————————————————————————————————————
"id"	Id of the recipe that starts that basecamp or basecamp expansion upgrade path, and has to conform to the pattern "faction_base_X_0", where X distinguishes the entry from the others, with the prefix and suffix required by the code.
"description"	The name shown in-game for the basecamp or basecamp expansion.
"om_terrains"	An array of overmap terrain ids which can be used as the basis for the basecamp or basecamp expansion. Individual entries can either be a string or an object containing "om_terrain" for the overmap terrain id, along with at least one of "parameters" and "om_terrain_match_type" (see JSON_INFO.md)

Examples

Camp that can be made anywhere

    {
        "id": "faction_base_barebones_0",
        "description": "Barebones Camp",
        "om_terrains": [ "ANY" ]
    },

Camp that can be placed on any overmap terrain starting farmland_ or hayfield_ or that match "farmland" or "hayfield" exactly

    {
        "id": "faction_base_farmer_0",
        "description": "Farmer Camp",
        "om_terrains": [
        { "om_terrain": "farmland", "om_terrain_match_type": "PREFIX" },
        { "om_terrain": "hayfield", "om_terrain_match_type": "PREFIX" }
        ]
    },

Camp that can only be placed on "omt_that_varies_in_shape" if the parameter "shape" is set to either "circle" or "circle_alt" (but not say "rectangle" that would want different map updates)

    {
        "id": "faction_base_circle_0",
        "description": "Farmer Camp",
        "om_terrains": [
        { "om_terrain": "omt_that_varies_in_shape", "parameters": { "shape": [ "circle", "circle_alt" ] }
        ]
    },

Sample basecamp upgrade path

The primitive field camp has the following upgrade path:

1. "faction_base_camp_0" - the initial camp survey and the bulletin board.
2. "faction_base_camp_1" - setting up the northeast tent
3. "faction_base_camp_2" - digging the fire pit and constructing a bed
4. "faction_base_camp_3" - adding the bookshelves to store stuff
5. "faction_base_camp_4" - adding the second bed to the tent
6. any of: "faction_base_camp_5", "faction_base_camp_7", "faction_base_camp_9", "faction_base_camp_15", "faction_base_camp_18" - add additional tents with beds in any order. or "faction_base_camp_6" - build the central kitchen. "faction_base_camp_8", "faction_base_camp_10", "faction_base_camp_11", "faction_base_camp_16" must be built in that sequence afterwards, though interleaved with the other optional upgrade missions after "faction_base_camp_4". or "faction_base_camp_12" - the central camp well. or "faction_base_camp_13" - building the camp’s outer wall, which can be followed by "faction_base_camp_14" to complete the wall. or "faction_base_camp_19" - building the camp’s radio tower, which can be followed by "faction_base_camp_20" to build the radio tower console and make it operational.
7. "faction_base_camp_17" - adding better doors to camp wall and the central building must be built after "faction_base_camp_14" and "faction_base_camp_16".

After setting up the first tent, the player has a lot of options: they can build additional tents to enable expansions, they can build the well for water, they can build as much or as little of the central kitchen as they desire, or add the wall to give the camp defenses, or the radio tower to improve the range of their two-way radios.

Modular Basecamp conventions

The modular basecamp is a structure for designing basecamp upgrade paths. You don’t have to use it, but elements of the design might get more code support in the future.

Layout

A modular camp is laid out on a 24x24 overmap tile. The outer 3 map squares on each side are reserved for fortifications and movement corridors, and the inner 18x18 map squares are divided into a 3x3 grid of 6x6 areas.

Area	upper left position	lower right position
northwest	3, 3	8, 8
north	9, 3	14, 8
northeast	15, 3	20, 8
west	3, 9	8, 14
center	9, 9	14, 14
east	15, 9,	20, 14
southwest	3, 15	8, 20
south	9, 15	14, 20
southeast	15, 15	20, 20

Ideally, nested mapgen chunks should fit entirely into a 6x6 area.

Naming scheme

Modular bases use the following naming scheme for recipes. Each element is separated by an _

• "faction_base" <– encouraged for all basecamp recipes, and
• "modular" <– indicates a modular construction, and
• overmap terrain id <– the base terrain that this modular base is built upon, and
• DESCRIPTOR <– arbitrary string that describes what is being built. For buildings, “room” is used to mean a construction that is intended to be part of a larger building and might share walls with other parts of the building in adjacent areas; “shack” means a free standing building. Numbers indicate stages of construction, with 4 usually meaning a complete structure, with walls and roof, and
• MATERIAL <– the type of material used in construction, such as metal, wood, brick, or wad (short for wattle-and-daub), and
• AREA <– the area in the 3x3 grid of the modular camp layout.

blueprint keywords follow a similar scheme, but "faction_base_modular" is collapsed into "fbm" and the overmap terrain id is collapsed into a short identifier. I.e., "fbmf" is the keyword identifier for elements of the modular field base.

Adding basecamp expansions

Basecamp expansion upgrade paths are defined by the corresponding set of files to the basecamps themselves, with two additions (at the end of the list):

• The recipe JSONs that define what the material, tool, and skill requirements to perform an upgrade mission and the blueprint mapgen, blueprint requirements, blueprint provides, and blueprint resources associated with each upgrade mission.
• The mapgen update JSONs that define how the map will change when the upgrade mission is complete. These may include shared instances of nested mapgen, such a standard room or tent.
• The recipe_group JSONs that define what recipes can be crafted after completing the upgrade mission and what camps and expansions are available.
• data/json/overmap/overmap_terrain/overmap_terrain_faction_base.json has to be updated to provide an overmap identifier for each new expansion.
• data/json/mapgen/faction_buildings.json also has to be updated to introduce an entry for the new expansion.