If you are playing the newest entry, MK1, there is a specific quirk regarding Intel 13th and 14th Gen Processors.
There have been reports of instability on high-end Intel CPUs due to voltage issues (often called the "Intel Instability" issue). While this usually causes crashes during gameplay, it can sometimes prevent the core engine from initializing correctly at startup. null coreerrorsopen failed mortal kombat new
If you see an error like null coreerrorsopen failed when launching or running Mortal Kombat (or a similarly named "Mortal Kombat New" build/mod), try the steps below in order. These are concise, practical fixes that address common causes. If you are playing the newest entry, MK1,
If absolutely nothing works, create a minimal CoreErrors.ini manually. If you see an error like null coreerrorsopen
[CoreErrors]
bEnableLogging=True
bShowMessageBoxes=True
ErrorPath=../Saved/Logs
This tricks the engine into seeing a non-null core. This is a last-resort hack; it may cause log spam but kills the fatal error.
In plain English:
Together, the error means Mortal Kombat crashed before it could even log why it crashed. This usually happens during launch or when loading a fight.