模块 · Modules

Modules are the top level hierarchy names for a valid CD2 JSON. The following is an alphabetized list of the current modules.

Control for the maximum number of enemies in the map, with the following fields:

When the number of enemies in the map reach their cap, new enemies will be prevented from spawning and some existing enemies will despawn. The exact mechanics behind this behaviour are not completely understood.

The Darkness module offers controls related to lighting and illumination both in the Space Rig and during a mission. It has the following fields (descriptions provided by @noskill):

A short explanation of the difficulty.

Main controls for enemy resistance, swarm and wave intervals and enemy counts.

The descriptions here are very summarized, please check A Quick and Dirty Guide to Custom Difficulty for Deep Rock Galactic, a CD1 guide explaining most of the fields inside this module foe details.

To see the values of these fields for the vanilla Hazards and some others, please check the DRG Hazard Scaling file.

Offers some controls related to the players.

See the Enemies/EnemiesNoSync section.

Controls for the Drilldozer in Escort missions.

A field accepting an int specifying the maximum number of players allowed in the lobby.

A module that allows CD2 to send messages to chat in response to events happening during the mission. It has The following fields:

Examples:

The following snippet sends a message on chat when the next resupply is available.

The following snippet sends a message on chat when a player dies.

The name of the difficulty. This field is necessary to be able to save the file in the in-game CD2 dropdown. Example:

NextDifficulty allows CD2 to automatically pick another difficulty at two specific moments:

There are many different uses for this field but a typical application is, using the RandomChoice mutator, choosing a difficulty at random when launching a mission:

Where it is understood that all the names in the Choices field are other difficulties existing in your CD2 list. The same snippet can be used to change the difficulty at random in deep dive stages.

If you don't want the difficulty to change when launching a mission from the Space Rig, the IfOnSpaceRig mutator can be used as follows:

This is a common application of NextDifficulty allowing to mimic the increasing difficulty of the vanilla Deep Dive with whatever set of three difficulties you choose. The way to set it up is as follows: let's say that we want to play Hazard 5x2 on Stage 1, Hazard 6x2 on Stage 2 and ND on Stage 3. We will need the three files saved in Custom Difficulty, and then we would add the following to each:

The ND file, being the one played in stage 3, doesn't need any modifications. In addition to editing the files for stage 1 and 2, you will need a "starter" file:

This Dive Starter will be the file you will select while on the Space Rig before starting the dive, and it should point to the difficulty you want to play on the first stage.

A special module that accepts a float and controls the amount of nitra generated in the map. It has a default of 1. The following snippet would generate twice the amount of nitra in a certain mission:

Pools is where enemies can be added or removed from the different pools in the game. For more information, this document is a detailed explanation about the pools system and how are they used when deciding which enemies are present in a mission. The accepted fields in Pools are:

The fields marked with * accept the Add (list), Remove (list) and Clear (bool) fields for adding and removing enemies at will. The EnemyPool can be freely manipulated with mutators during the mission, opening the possibility of adding and removing enemies based on gameplay conditions. It is not recommended to mutate the other pools.

A special module offering customization options for Salvage missions. It contains three submodules: MiniMules, Uplink and Refuel with the following fields:

Example: a salvage where each mule spawns 20 legs and requires 15 to be repaired, and the area of the uplink bubble is 1.5x the normal.

Another example: the number of legs is randomized every mission.

Please see the BySalvagePhase mutator for values that need to change during different phases of the mission.

Some of the fields in the table above are marked as Usable. These affect how the E key interactions work in some instances such as mule repairing. They accept the following fields:

Some examples of use. The following snippet makes the uplink repair faster than normal when more than 1 player is interacting:

The following snippet changes the duration of the mule repair based on how many players are interacting, and buffs the speed boost of multiple players:

A module that allows CD2 to play a sound in response to events happening during the mission. It has two fields: a boolean Play which accepts mutators and a Cue which accepts the path to the sound you want to play. As an example, the following snippet plays a laughing sound when a player dies:

The game has a lot of available sounds, but to play them outside the game you will need the game files and either Unreal Engine 4.27 or FModel.

This module controls the chance of some random events such as the Korlok, Bet-C, etc. Please note that this module is not 100% functional as some of the encounters depend on the seasons system which CD2 cannot control for now. Each SpecialEncounter accepts the following fields:

The vanilla SpecialEncounters would look like:

Example: set all special encounters to zero.

SpecialEncounters can accept any enemy descriptor in its Enemy field and it can be used to make sure there's exactly 1 such enemy for the whole mission. As an example, some difficulties have exactly 1 Vartok Scalebramble per mission:

This module contains information about the resupply cost. It accepts a single float field Cost that can be mutated.

Example: a fixed resupply cost of 40 nitra.

The StartingNitra field from CD1 does not exist in CD2: the same functionality is done with mutators. Example: the first resupply is free, 40 nitra for all others:

While both snippets do the same thing, ByResuppliesCalled is usually more compact when specifying a different cost for the first few supplies.

Example: the cost is 45, but after the 6th resupply it drops to 40.

A module to store global variables, which allow communication between modules. Vars is structured as a dictionary of names and values with the following fields:

A variable defined in Vars can be later used in any place which accepts a value of the same type by using {"Var": "MyVariable"}. Variables are all updated at once so they will always be consistent across modules, but the implementation can cause up to 500 ms of delay between the variable state and the true game state.

The following snippet allows the user to have a toggle for adding or removing stingtails in a difficulty:

The following snippet allows the user to select an easy or a hard version of the difficulty by using a variable for the EnemyCountModifier and the Select mutator:

The Warnings module can be used to ban mission anomalies. It accepts a single Banned field which is one or more from the table below. Please note that banning anomalies that affect resource generation such as Mineral Mania or Gold Rush will cause clients without CD2 to have mineral desync and they will not be able to get nitra.

Example: ban Swarmageddon and Low O2 from a difficulty.

See the WaveSpawners section.