Great that you got through the guide! I hope it was easy for you to follow. I want to show a few things on how to do different things with MCM to make your mod making easier, and how I set up keybinds to use with MCM.
We spoke a bit about keybinds and how they are strings. This is because the way I set up keybinds is through the “Any Key” node. Get Key Display Name, and then compare that display name with an equals exactly. If true, I do whatever. This is basically the set up as it shows in BP_MCM_ModExample1:

By the way remember to turn off Consume Input and Override Parent Binding settings in Any Key. Or users may encounter problems. What this graph above does is: We pressed a key, if that key is what we have set as a variable string, then we play a sound. Key Press Example 1 is this string value that you’d set in your keybind setting.

These settings use this set up, which I suggest you check: https://www.nexusmods.com/hogwartslegacy/articles/133
So you need to set your keybind text correctly for the default value.
The way this works is that after you set the key in MCM, that key’s name is sent to this variable.
By the way you can also set this string variable as Config Variable:

What this does is that you can later on type in Engine.ini for editing the keybind manually. It is okay to give this setting for if another user isn’t using MCM and they still may want to change the keybind. It would be something like:
[/CraftingMod/CraftingActor.CraftingActor_C] OpenCraftMenu = B
You may have noticed how we have used three out of four available events. The last one is called Event On MCM Button Pressed. Double click on it so it shows up on the graph. You an see how it outputs a Mod ID and Setting ID. You can use these to compare them to your own Mod ID and your Setting ID. The idea is: Your mod blueprint recieves this event, something calls it (MCM calls it). Your blueprint goes: “Okay, is the Mod ID ‘My Nice Mod’? Yes, now is the Mod ID ‘My Button’? Yes, then we will do this”. It is why you set something like this:

Event is recieved, and compares if the mod ID is our mod ID. Then, we compare with an AND bool node if the Setting ID also matches the Setting ID we put on our buttons when we registered them. Then if so, through a branch, we do whatever we wanted to do with a button. You can plug another function here, a custom event, etc. You can also do this comparing stuff through a Switch on String node. On the first, if what our mod recieves is from Button Test, then it will play a sound, if not, it will check if it is Button Test 2 that sent this, and if so, it will execute a console command: add 10 Breads to our inventory. You can probably see how this is also super useful for debug purposes on mods. You basically have all buttons you want without needing to create custom UIs or having to test things some weird way.
So when it comes to combo boxes/dropdowns, you will want to do something like this to get the value chosen: