The implementation of MCM into your mod is really easy. In 2.0 however you require first to set up your .uplugin to have a dependency on MCM. To do this, go to your SDK folder, Stalker2/Mods/YourMod. And find the .uplugin. With the Zone Kit closed, open this .uplugin file with a text editor. Then add this at the bottom:
"Plugins": [
{
"Name": "ModConfigurationMenu",
"Enabled": true
}
]
So that it looks like this:

If it does not look like that, you may need to, before adding the plugins bit, select your mod in the Zone Kit first, if your mod was made before 2.0. You can also go to Edit>Plugins. Search for your mod there, click on Edit, and at the bottom where it says Dependencies, add MCM there.


Now your mod has a dependency on MCM. While it WILL look for MCM existing in the game, it will not crash the game if MCM is not installed. This means MCM is a soft requirement/dependency.
Open your mod’s main Blueprint, or wherever you want to add the settings, you can add to multiple blueprints of one mod if you wish. Then, click on Class Settings on the top. After that, in the Details panel, scroll down to Interfaces, and on Implemented Interfaces, click on Add. There, you will search for BPI_MCM_SettingsProvider (This is why you require the modder ModConfigurationMenu version in your Zone Kit). Click on it to implement this BPI.

If you did it correctly, this should show up now:

Let us continue then with registering our first setting: 3. Registering our first Setting