# Mod instruction

The **mod instruction** is designed to control the inclusion or exclusion of blocks of descriptions and settings based on the global mode of operation. This feature is especially useful in cases where different game modes require different configurations.

## **Global modes in the Men of War II game**

<table><thead><tr><th width="211">Mode </th><th>Description</th></tr></thead><tbody><tr><td><strong>Multiplayer (mp)</strong></td><td>This mode activates configurations that are specifically tailored for multiplayer gameplay.</td></tr><tr><td><strong>Everything else</strong></td><td><p></p><p>This includes single-player missions and the game editor mode</p><p></p></td></tr></tbody></table>

## Template for a mod instruction

> **Template for the mod instruction**
>
> ```
> (mod mode_name {code})
> ```
>
> mode\_name specifies the mode for which the enclosed code block `{code}` should be active

<details>

<summary>Example</summary>

```
(mod mp {code})
```

If the game sets the `mp` modifier (indicating that the player has launched multiplayer mode), then the `{code}` block is inserted into the SDL.

</details>

For instance, if the mode is set to mp, the code block will only be executed in multiplayer mode.

The **mod instruction** can also be used in a prohibitive format, which means you can specify that certain code blocks should only be excluded in certain modes rather than included. This is useful for disabling specific features or settings in a particular mode without having to explicitly include them in all other modes.

<details>

<summary>Example</summary>

```
(mod not_mp {code})
```

</details>

This structured approach using the mod instruction allows developers to neatly organize their code and ensure that the correct settings and features are active based on the game mode, enhancing both maintainability and gameplay experience.

{% hint style="info" %}
If you have difficulties understanding the terminology and the essence of the instruction description, please refer to the article [**Basic knowledge about configuration files**](https://bestway-1.gitbook.io/documentation/foundational-knowledge/basic-knowledge-about-configuration-files).
{% endhint %}

Additionally, you can explore other types of instructions.

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Include instruction</td><td><a href="/pages/QT9HhUeonOLpUowc8Vb0">/pages/QT9HhUeonOLpUowc8Vb0</a></td><td><a href="/files/ueYOF7YCEEu954WYabzW">/files/ueYOF7YCEEu954WYabzW</a></td></tr><tr><td>Define  instruction</td><td><a href="/pages/L4iihm76TBtBBWKRRoac">/pages/L4iihm76TBtBBWKRRoac</a></td><td><a href="/files/ueYOF7YCEEu954WYabzW">/files/ueYOF7YCEEu954WYabzW</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bestway.com.ua/foundational-knowledge/basic-knowledge-about-configuration-files/mod-instruction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.