C++ modding is the holy grail of Satisfactory modding. As opposed to the visual programming style of the Blueprints system, text-based C++ code can be compiled into far more efficient code. Additionally, with C++ mods, you have access to modify nearly every aspect of the game, whereas there are still many features not exposed to Blueprints.
That being said, Blueprint scripting is still very useful for quick stuff, or for things that don’t need to be high performance (like UI).
Well, since this is a very advanced topic, we recommend you to learn C++ and C++ for Unreal Engine first.
We have compiled a list of some helpful learning resources here, but you will probably want to search out some more on your own.
Here is a list of some concepts you should learn before going further:
C++ concepts which are used but are implemented differently in Unreal Engine:
std::set (And the differences between it and std::vector)
The Unreal Engine synonyms for the aforementioned concepts (the UE implementation of them):
std::string → FString
std::vector → TArray
std::set → TSet
std::(unordered_)set<T> → TSet<T>
std::(unordered_)map<K, V> → TMap<K, V>
Unreal Smart Pointers
Other stuff added only by UE or general programming concepts:
What a UObject/UProperty/UFunction (reflection system) is
What an AActor is
What garbage collection means, how it works, and how to make use of it
If you have a good understanding of most these concepts, then you have a very solid foundation from which to start modding. If so, this is likely not your first time working on a project or mod like this, and you’ll be able to judge what content you can skip over and learn when needed.
We can not understate the value of learning through doing. Especially if just starting out with these concepts, we suggest that instead of immediately beginning working on a mod, taking the time to make a separate Unreal C++ project for testing and practice. Try out working with the concepts mentioned above before trying to make use of them in a mod.
The following resources may be helpful for you in the creation of your C++ mods:
CSS has been kind enough to provide us with the Satisfactory C++ headers. You can find them in the
CommunityResourcesfolder of your install.
You can find the
.pdbfiles for the game in your install’s Binaries folder.
When you compile your C++ code into the final binaries (stuff that actually is used by the game) you will get a Dynamic Link Library (
When you distribute your mod, you will have to make sure it includes this file. You will need to add it also to your
data.json as an
sml_mod object. More info on the upload process can be found on the Uploading to SMR page.
This file comes with a companion, the Program Database (
This file holds additional information about the original source code and allows you to debug your code more easily in runtime.
You can ship this file with your mod, but don’t need to.
If you do decide to ship it, it doesn’t needed to be added to the
We won’t go into detail about the general technical stuff aspects of C++ in this documentation. If you want to learn more about that, there are plenty of good resources available elsewhere on the Internet. In order to write C++ mods, you will require both general C++ knowledge, and knowledge about how C++ applies to Unreal Engine systems. You can find a quick guide to the Unreal portion in the Unreal Documentation.
Due to technical limitations, there are some functions/features of Satisfactory and Unreal Engine 4 that we are not able to access or need to use a work around to call correctly. This is the world we live in right now, and we can’t do much about it.
If you experience a crash or some undefined behavior while using a function from UE4 or Satisfactory, you should read the javadoc comment that has been added to the function. Sometimes the comment will tell you that it doesn’t work and suggest you use the workaround written in the comment.
If it still doesn’t work, and you are absolutely sure that you are using it correctly, contact the SML devs on the Discord for further advice.
You can also open the bootstrapper log found under
<SF installation directory>/pre-launch-debug.log.
This log will contain information about the special linkage the bootstrapper performs.
If your mod requires calling a Satisfactory function that is not compiled into their binaries,
f.e. when the function is marked as
inline, then it will create a log entry starting with
[FATAL] Executable missing symbol with mangled name.
This will you also tell you the mangled symbol name it was not able to find.
You can still run the game, but when your mod tries to call this function, the game will crash.
The crash will not cause the crash reporter to open, which is a signal that you should then checkout
the pre-launch-debug.log since it will tell you which symbol got called.
This information will be very useful in fixing the bug, so keep it on hand if you plan to ask for help with your mod on the Discord.