Wiki menu

What mods can change

A map of modding in Global Protocol: what a mod can change, three ways to work, where mods live, and what they mean for saves and multiplayer.

Last updated for v0.5.35
On this page

A mod is a folder of files that the game reads on top of its own data. It can be as small as one event with two buttons, or as large as a different century with its own countries, units and research. This page is the map: what a mod can touch, how you can work, where the files go, and what a mod does to your saves, achievements and multiplayer games.

What a mod is

A mod is one folder with a file called mod.json at its top. That file is the manifest: it gives the mod its id, its name and its version. Everything else in the folder is optional, and a mod only lists what it changes. A mod that re-prices one building contains that one building and nothing else.

A game with no mod enabled is the base game. The save list calls it “Vanilla”.

What a mod can change

AreaWhat you can doWhere it lives in the mod folder
ScenarioSet the start date, add or remove countries, set each country’s starting economy, politics and military, hand provinces to other owners, place starting armies, fleets and air wings, and start the world with alliances, treaties and wars already in place. A scenario can also bring its own national goals and its own endings.scenario/
Buildings, units, resourcesChange, add or disable buildings and unit types. Rename, re-price, re-categorise or disable resources (a mod cannot add a resource).Content/buildings.json, Content/units.json, Content/resources.json
Balance numbersChange the game’s balance values, section by section.overrides/game_settings.json
ResearchRetune doctrines and add branches or tiers to the Knowledge Network, add research tracks of your own, and add named specialists that countries can hire.overrides/doctrines.json, Content/research_tracks.json, Content/specialists.json
PoliticsChange or add laws, and retune the interest groups.overrides/laws.json, overrides/interest_groups.json
EventsAdd event popups with conditions, options, effects and follow-up events.Content/events/*.json
InterfaceAdd toolbar buttons and extra rows in the province and country panels, recolour and resize the HUD, replace or hide parts of the HUD, and add up to three gauges to the top bar.Content/ui/
TextAdd or replace any text, in each of the game’s 13 languages.Content/localization/<language>.csv
ArtReplace icons of buildings, units, resources and doctrines, add event pictures, and change the markers units use on the map.icons/, images/events/, overrides/military_markers.json
Money displayShow money in national currencies. This changes the display only; the simulation keeps one money unit.Content/currencies.json
ScriptsRun your own logic when things happen in the game: a WebAssembly module, or compiled C# code.entrypoints.wasm in mod.json, or Mods/*.dll

Two limits are worth knowing before you plan a mod:

  • A mod event cannot replace an event of the base game or of another mod. An event whose id is already taken is skipped. Add yours under a new id.
  • Some abilities need a permission: adding to the interface, and a script that changes the treasury, fires events, writes flags, reads the wider world state or acts in diplomacy. A mod lists its permissions in mod.json, and the game shows them as badges on the mod’s row, so players see them before they enable it. Without the permission, the game refuses the action.

Three ways to work

You can mix all three in one mod. They write the same files.

The Mod Builder

The Mod Builder is an editor inside the game. It creates the folder for you, edits most of the files in the table above through forms, shows the scenario on the real map, checks the mod for mistakes and uploads it to the Steam Workshop. It only rewrites the files you edit in it, so anything else you put in the folder is left as it is. Start here if you have never made a mod. See The Mod Builder.

Editing the files by hand

Every file is plain JSON or CSV, so a text editor is enough. This suits large mods, mods kept in version control, and anything you want to generate with a tool of your own. The file formats are described in the reference pages listed at the bottom, and the main files have JSON schemas that a text editor can use to check a file as you type. Your first mod builds a small mod this way.

Scripting

Data files cover most mods. A script is for logic that data cannot express: reacting to a war, counting something over a campaign, deciding when to fire an event. A script is either a WebAssembly module or a compiled C# assembly. On macOS a mod that ships a WebAssembly script still loads its data, but the script does not run, and the game says so on the Mods screen. See Scripting with WebAssembly and C#.

Where mods live on disk

On Windows the game looks for mods in three folders of your own, and in the Steam Workshop folder that Steam manages.

FolderNotes
%USERPROFILE%\AppData\LocalLow\Dorlion Interactive\Global Protocol\Mods\The first choice. The Mod Builder puts a mod it creates here unless you pick another location.
%LOCALAPPDATA%\NewWorldOrder\Mods\Also holds loadout.json, the list of mods you enabled.
Documents\GlobalProtocol\Mods\
The game’s Steam Workshop folderMods you subscribed to. Steam owns this folder and overwrites it when a mod updates, so do not edit files there.

If a folder does not exist yet, create it. Put each mod in its own subfolder, named after the mod’s id.

How the game finds a mod

  • The game searches those folders, and every folder below them, for files named mod.json. A folder whose mod.json can be read and has an id is a mod.
  • One mod per folder. A mod.json inside another mod’s folder is ignored, and the Mods screen lists it as a warning.
  • If two folders in the same mods folder use the same id, the one nearest the top loads and the screen warns about the other.
  • Your own folders are read before the Workshop folder. A local copy of a mod therefore wins over the Workshop copy with the same id.
  • If mod.json is not valid JSON, or has no id, the mod does not appear in the list at all.

The Mod Builder shows a mod’s full path on its Mod info page, with an OPEN FOLDER button next to it.

Enabling a mod

  1. Open the loadout. On the main menu, click MODS. The MOD LOADOUT panel lists every mod the game found. The game looks again each time you open the panel, so a folder you copied in a moment ago shows up without a restart.

  2. Read the row. Each row shows the mod’s name, version, id and description, and a line of badges: LOCAL or WORKSHOP for where it comes from, SCENARIO if it carries a scenario, SCRIPTED if it ships a script, and one badge per permission it asks for (or NO PERMISSIONS).

  3. Click the row to switch the mod on or off. Enabled mods move to the top and show their load position as [1], [2] and so on.

  4. Start a new game. The MODS button on the main menu gains an asterisk while your change is waiting. Click NEW GAME: the game reloads itself with the new set of mods and then opens country selection.

A mod can ask to start enabled, with enabledByDefault in its mod.json. That applies only until you first save a selection in this panel. From then on your selection decides.

The load order comes from the mods themselves, not from the panel: a mod loads after the mods it depends on, then by the loadOrderHint in its mod.json, then by id. Where two mods change the same thing, the one that loads later wins.

The demo. Mods and the Steam Workshop are part of the full game. The demo cannot load them.

Choosing a scenario

The game runs one scenario at a time, and the loadout decides which: the scenario is the one carried by the single enabled mod that has one. Enable one such mod and the line at the top of the panel changes from No active scenario to Active scenario: followed by the mod’s name. Mods without a scenario (extra events, a balance change, a theme) can be enabled next to it.

The panel has no scenario picker. With two scenario mods enabled, no scenario loads, so keep one enabled at a time. With no scenario mod enabled, a game you start is the base game’s 2026 start with your other mods applied.

Saves, achievements and multiplayer

Saves

A save remembers which mods were enabled and which scenario was running. The save list shows them on a Mods: line, which reads “Vanilla” for a game without mods.

  • To load a save you need the same set of mods enabled as when it was made. Otherwise the save list marks it “This save requires the same enabled mods as when it was created” and will not load it. The main menu’s CONTINUE button is switched off when your latest save is one of these.
  • A scenario must also match, by id and by version.
  • A newer version of the same mod is accepted. Whether the save still makes sense is then up to the mod: events are stored by id, so an event that was renamed or removed loses its place in a running chain.

Saves you made without mods are waiting for you when you switch the mods off again.

Achievements

Achievements are not earned while any mod or scenario is active. They are also not earned in multiplayer or while spectating. Disable your mods and start a new game when you want to earn them.

Multiplayer

Every player in a lobby must load the same mods: the same ids, the same versions, the same files and the same scenario. Where a mod comes from counts too, so a local copy and the Workshop copy of one mod do not match each other.

  • The lobby marks a player whose mods differ with a MOD MISMATCH badge and says what differs, for example a missing mod or a different version.
  • The host cannot start until every player matches.
  • Translations are the exception: a mod whose text files differ still plays together, and the lobby only notes it.
  • The Mod Builder’s live tools (applying changes to a running game, firing an event) work in single player only.

Publishing to the Steam Workshop

The Mod Builder publishes for you. On its Publish page you give the mod a Workshop title, a description and a preview image (PNG or JPG under 1 MB), choose who can see it (Private, Friends only or Public; Private is selected at first), and press PUBLISH TO WORKSHOP. The game checks the mod first: an error stops the upload, and warnings ask you to confirm once. What Steam receives is a clean copy of the folder without build output, backups or version-control folders. After the first upload the mod’s mod.json holds its Workshop item id and the button reads UPDATE WORKSHOP ITEM. Players browse and subscribe to Workshop mods under MODS › BROWSE WORKSHOP. The full procedure is on The Mod Builder.

Where to go next

Start here:

A complete mod, taken apart. Old World Order is a public mod that moves the game to the year 1450, with its own countries, units, research, events and interface. Its files are on GitHub, and these pages walk through them:

Reference, file by file:

If you only want to play other people’s mods, see Mods and scenarios.

Play Global Protocol: New World Order

Out now in Early Access on Steam, with online multiplayer for 2–8 players.