---
name: "BIS_fnc_EXP_camp_manager_setState"
type: function
status: ok
groups: ["CampaignManager"]
arma3_since: "1.62"
locality: {"argument": null, "effect": null, "server_exec": true}
source: https://community.bistudio.com/wiki/BIS_fnc_EXP_camp_manager_setState
revid: 379566
updated: 2026-10-31T13:55:37Z
---

# BIS_fnc_EXP_camp_manager_setState

*Function · CampaignManager · Arma 3 v1.62*

Locality: **server execution only**

## Description

Sets the mission state of an Apex campaign mission. The state is stored in the public [missionNamespace](../commands/missionNamespace.md) variable `"BIS_coop_campaign_ss_state"` (broadcast to all machines) and the state's event is fired on the server with [BIS_fnc_EXP_camp_manager_triggerEvent](../functions/BIS_fnc_EXP_camp_manager_triggerEvent.md). Clients running [BIS_fnc_EXP_camp_manager](../functions/BIS_fnc_EXP_camp_manager.md) fire the event when they receive the new value.
Called on a client, the function shows an error and does nothing.

Valid states are `"Waiting"`, `"Intro"`, `"Loadout"` and `"Started"`. The function is meant for internal use: it is called by [BIS_fnc_EXP_camp_manager](../functions/BIS_fnc_EXP_camp_manager.md) on the server.

## Syntax

```sqf
[state] call BIS_fnc_EXP_camp_manager_setState
```

**Parameters:**

- `state`: [String](../topics/String.md) - (Optional, default "Waiting") the new mission state: "Waiting", "Intro", "Loadout" or "Started"

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

## Examples

### Example 1

```sqf
// on the server
["Started"] call BIS_fnc_EXP_camp_manager_setState;
```

## See also

[BIS_fnc_EXP_camp_manager](../functions/BIS_fnc_EXP_camp_manager.md) · [BIS_fnc_EXP_camp_manager_getState](../functions/BIS_fnc_EXP_camp_manager_getState.md) · [BIS_fnc_EXP_camp_manager_triggerEvent](../functions/BIS_fnc_EXP_camp_manager_triggerEvent.md)

<sub>Source: [BI Community Wiki — BIS fnc EXP camp manager setState](https://community.bistudio.com/wiki/BIS_fnc_EXP_camp_manager_setState) (revision 379566).</sub>
