-
Notifications
You must be signed in to change notification settings - Fork 6
Description
I am trying to get the Rider plugin to work on Linux.
The first issue is that it does not contain the native Linux Doorstop libraries, so I added those. See my fork. I have already updated Rimworld-Doorstop to support Rimworld 1.6 so I at least know what versions of things are needed. The other OS resources have files that Rimworld-Doorstop doesn't use, so I have no idea about those.
After adding the resources I still get this error in Rider.

As you can see from my fork I added some additional logging to std-out because I have no idea on how to debug a Rider plugin. All I have been able to figure out so far is that the resource copy is working correctly but something is going wrong with the command.
Coping Doorstop files
Coping /UnityDoorstop/Linux//.doorstop_version to /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/.doorstop_version
Coping /UnityDoorstop/Linux//doorstop_config.ini to /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/doorstop_config.ini
Coping /UnityDoorstop/Linux//Doorstop/libdoorstop.so to /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/Doorstop/libdoorstop.so
Coping /UnityDoorstop/Linux//Doorstop/0Harmony.dll to /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/Doorstop/0Harmony.dll
Coping /UnityDoorstop/Linux//Doorstop/Mono.Cecil.dll to /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/Doorstop/Mono.Cecil.dll
Coping /UnityDoorstop/Linux//Doorstop/Mono.CompilerServices.SymbolWriter.dll to /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/Doorstop/Mono.CompilerServices.SymbolWriter.dll
2025-07-05 17:49:37,864 [ 18600] WARN - #c.j.r.d.DebuggerWorkerProcessHandler - Debugger.Worker process was terminated before the debug session was initialized. Exit code: 0. Output:
/snap/rider/603/lib/ReSharperHost/linux-x64/JetBrains.Debugger.Worker --runtimeconfig /snap/rider/603/lib/ReSharperHost/JetBrains.Debugger.Worker.runtimeconfig.json --mode=client --frontend-port=38493 --plugins=/snap/rider/603/plugins/rider-godot/dotnetDebuggerWorker;/snap/rider/603/plugins/rider-unity/dotnetDebuggerWorker
Handler Output:
Process finished with exit code 0
Removing Doorstop files
Removing /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/.doorstop_version
Removing /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/doorstop_config.ini
Removing /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/Doorstop/libdoorstop.so
Removing /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/Doorstop/0Harmony.dll
Removing /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/Doorstop/Mono.Cecil.dll
Removing /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/Doorstop/Mono.CompilerServices.SymbolWriter.dll
Removing /home/caleb/.steam/debian-installation/steamapps/common/RimWorld/Doorstop
I also attempted to call RunState directly but it is pretty integrated into the Rider dependencies which makes that pretty difficult.
Any advice on how to debug the Rimworld Run State would be appreciated.