MCM requires settings to be registered for them to show up in the menu. That is basically why we need to do this. In short, how it works is that you as a mod author register the default setting and the normal setting. The default setting will never be seen by the player, they will only see the normal setting. But the default setting must be registered aswell so things can be reset to default. MCM will read every mod setting that is registered and compare it to the ones it has, along the saved settings, and will load up the saved settings to set your own mod’s. I know it may sound like a lot, but let us take it slow.

First, we will double click on “Register MCMDefault Settings”. We will register our first Default setting.

image.png

Then, this node will show up:

image.png

What this node does is to grab the API from MCM and use it as the target. So that when MCM registers or searches, it will be through this that will connect to your own blueprint/s. Open BP_MCM_ModExample1. To the very top, you will see four empty nodes. Select the four, and copy them with Ctrl+C.

image.png

Now go to your mod BP and paste the four of them. Why are we pasting them? Can’t we just right click and search for them? You can try. But most likely the correct one won’t show up. You need the one with the icon of a little message on the top right (and name as what it is and then “(Message)”), or you MAY run into issues. I found that I could only copy and paste them by hand rather than search.

Now we will fill the information of the Default setting by using this node:

image.png

You will connect this node this way to the event:

image.png

Now every other default setting you wish to expose to the player, needs to be connected with the Exec pin of the previous mod setting, or in a sequence, or however you wish to put them, but the target must ALWAYS be BPI MCM API.

We can now fill the settings, I will explain here what each does:

GENERAL SETTINGS: