Crash breakdown: why it matters which launcher starts your game
TOR crashed when opening the inventory. Three hours of logs showed the game was started through Launcher.Native.exe — where many mods are untested.
In short
- There are two launchers in the game folder; Launcher.Native.exe runs the game on .NET Core, where almost nobody tests mods
- Start through Steam, TaleWorlds.MountAndBlade.Launcher.exe or RickLauncher
- Do not send the report to TaleWorlds — sending deletes the crash files
- This case helped us find two bugs in Crash Doctor itself
Someone wrote in Discord: TOR crashes. We started digging — three hours of logs and reports later we found the problem. A short explainer follows.
A player on Bannerlord 1.3.15 with The Old Realms reported that the game crashed as soon as they opened the inventory or the loot screen after a battle. It crashed without Crash Doctor too — they installed the mod to find the cause.
What the logs showed
- the game version was right, the load order was right, TOR and the libraries (Harmony, ButterLib, UIExtenderEx, MCM) were built for 1.3.15;
- but the game was started through
Launcher.Native.exe.
Two launchers in the game folder
TaleWorlds.MountAndBlade.Launcher.exe— the regular one;Launcher.Native.exe— the “native” one.
The native one runs the game on a different .NET runtime (.NET Core instead of .NET Framework). That is a supported mode for the game itself, but almost nobody tests mods on it. Some code that works fine in the regular mode crashes there.
The player started the game through the regular launcher — the crashes were gone.
✅ Recommendations
- Start the game through Steam or through
bin\Win64_Shipping_Client\TaleWorlds.MountAndBlade.Launcher.exe. Even better — through RickLauncher! If your shortcut points atLauncher.Native.exe, replace it. - If the game crashes in unexpected places (inventory, trade, the post-battle screen) while mod versions and order are fine — first check what you start it with.
- When the game offers to send a report to TaleWorlds, close the window without sending: sending deletes the crash files. The report we need: Crash Doctor → Crash Diagnostics → pick the crash → Export.
- If Crash Doctor caught the crash, send
Modules\CrashDoctor\crashdoctor.logtogether withreport.txt— that is how this case was untangled.
This player helped us find and fix two bugs in Crash Doctor itself that only showed up on .NET Core. Thanks for the patience and the logs 🙏 The fixes are in Crash Doctor 2.2.0.4.