---
name: "getMissionConfig"
type: command
status: ok
groups: ["Config", "Mission Information"]
arma3_since: "1.56"
locality: {"argument": null, "effect": null, "server_exec": false}
source: https://community.bistudio.com/wiki/getMissionConfig
revid: 341696
updated: 2023-06-18T12:18:00Z
---

# getMissionConfig

*Command · Config, Mission Information · Arma 3 v1.56*

## Description

Returns [Config](../topics/Config.md) entry for the given scenario attribute from the 1st tier. The attribute can be config class or config property. If it is defined in multiple places, the command checks them in the following order:
1. External *[Description.ext](../topics/Description.ext.md)* file
1. Eden Editor scenario attribute
So if attribute exists in both places, attribute from [description.ext](../topics/Description.ext.md) is used. Previously, scenario attributes were extracted from *Description.ext* using [missionConfigFile](../commands/missionConfigFile.md). That still works, but it ignores attributes set directly in the editor and it should not be used anymore.

## Syntax

```sqf
getMissionConfig attribute
```

**Parameters:**

- `attribute`: [String](../topics/String.md) - attribute name

**Returns:** [Config](../topics/Config.md)

## Examples

### Example 1

```sqf
_header = getMissionConfig "Header";
```

Returns scenario header config. Replaces the previous approach which would scan only the external *Description.ext* file, but ignore the value set in the Eden Editor:

```sqf
_header = missionConfigFile >> "Header"; // Old approach
```

## See also

[getMissionConfigValue](../commands/getMissionConfigValue.md) · [missionConfigFile](../commands/missionConfigFile.md) · [BIS_fnc_getParamValue](../functions/BIS_fnc_getParamValue.md) · Mission Parameters

<sub>Source: [BI Community Wiki — getMissionConfig](https://community.bistudio.com/wiki/getMissionConfig) (revision 341696).</sub>