Civilization-related JSON files

Beliefs.json

link to original

This file contains the beliefs that can be chosen for religions in your mod.

Each belief has the following structure:

Buildings.json

link to original

This file contains all the buildings and wonders you want to use in your mod.

Each building has the following structure:

Nations.json

Link to original

This file contains all the nations and city states, including Barbarians and Spectator.

Each nation has the following structure:

Personalities.json

Link to original

This file contains all Personalities for computer players.

Each personality has the following structure:

The object maps policy branches to priority values for the major civilization using the policy branches name and integers. Any branches not listed have a default value of 0

The code below is an example of a valid "priorities" definition.

"priorities": {
    "Tradition": 30,
    "Liberty": 20,
    "Honor": 10
}

Personality Behaviours

Personality Behaviours are not fully implemented yet and their names may change. Using them before they are ready might make the mod unplayable. The following is WIP - read on at you own peril!

There are 7 defining behaviours that influence an AI Civilization's behaviour. A higher value means they will behave more like the attribute.

• Military: Determines how much does the civilization prioritizes building a military, but not necessarily using it. A higher value means more focus on military, a lower value means it is likely more peaceful.
• Agressive: Determines how the civilization uses its units while at war and which buildings they prioritise. A higher value means the civilization is more aggressive, a lower value means it is more defensive.
• War: Determines how likely the civilization is to declare war. A 0 means the civ won't declare war at all.
• Commerce: Determines how open the civilization is to trade, value open borders, and liberate city-states. A higher value means more trading frequency even with civilizations they don't like.
• Diplomacy: Determines how likely the civilization is to declare friendship, a defensive pact, peace treaty, or other diplomatic actions.
• Loyal: Determines how much the civilization values a long-lasting alliance, how willing they are to join wars with them, and how much they despise other unreliable civilizations.
• Expansion: Determines how focused the civilization is on founding or capturing new cities. A lower value means they might focus on culture more.
• DenounceWillingness: Determines how eager the civilization is to denounce other civs.

CityStateTypes.json

Link to original

This optional file is used for defining the types of city states. These types determine the benefits major civilizations get when they befriend or ally the city state with influence. For base ruleset Mods, if the file is ommitted or contains an empty list, all types from the Vanilla ruleset are automatically added: Cultured, Maritime, Mercantile, Militaristic, Religious.

Each city state type has the following structure:

Policies.json

Link to original

This file contains all the available social policies that can be "bought" with culture.

They are organized in 'branches', each branch has an 'opener', one or more 'member' policies, and a 'finisher'. Therefore this file is organized using two levels - branch and member policy.

The properties of the 'opener' are defined with the branch level, while the 'finisher' is an entry on the member level which must be named as branch name + " Complete", case sensitive. For example, the finisher of a policy branch "Tradition" will have the name "Tradition Complete".

Branch structure

Each policy branch has the following structure:

Member policy structure

Branch finisher structure

Branch priorities

The "priorities" object defines the priority major civilizations' AI give to a policy branch. The AI chooses the policy branch with the highest sum of the peferred victory type listed here and the number flisted in the personality's priority. If two or more candidate branches have the same priority, the AI chooses a random branch among the candidates.

The object maps victory types to priority values for the major civilization using strings and integers. If the preferred victory type is not specified, the default priority value is set to 0.

The code below is an example of a valid "priorities" definition.

"priorities": {
"Neutral": 0,
"Cultural": 10,
"Diplomatic": 0,
"Domination": 0,
"Scientific": 10
}

Quests.json

Link to original

This file contains the quests that may be given to major civilizations by city states.

Each quest has the following structure:

Quest name

The name of the quest defines the criteria for the quest. If they are not defined in the predefined enum, they will have no behavior. In the description, square brackets [] in the description of the quest is replaced with extra information (except for Invest). The list of predefined quest names are as follows:

Quest weight

The "weightForCityStateType" object determines the quest's weight multiplier. When a city state initiates a quest, the initial weight is 1, and it is multiplied by values based on city state type and personality (Friendly, Neutral, Hostile, Irrational). The AI then randomly selects a quest based on the final weighted values.

The object maps city state type and personality to the weight multipliers for the city state using strings to floats. If the preferred victory type is not found, the default multiplier is 1.

The code below is an example of a valid "weightForCityStateType" definition. In this case, a friendly militaristic city state will be 0.4 (0.2 × 2) times as likely to pick this quest than a quest with weight 1.

"weightForCityStateType": {
"Hostile": 2,
"Friendly": 0.2,
"Militaristic": 2
}

Religions.json

Link to original

This is just a list of Strings specifying all predefined religion names. Corresponding icons must exist, that's all to it. After all, they're just containers for beliefs.

Specialists.json

Link to original

This file should contain a list of all possible specialists that citizens can be assigned to.

Each specialist has the following structure:

Techs.json

Link to original

This file contains all the technologies that can be researched with science. It is organized into an outer list of 'columns', which in turn contains one or more tech each.

Column structure

Each tech column has the following structure:

Tech structure