I was trying to make this debugger work with the game "Sapiens".
When launched, node.js indicates the childprocess immediately exited with code 0 even though the game is still running.
So I thought it was probably running under an other process which exited but let its child live.
So I tried a couple of things like turning off "shell" or "detached" but they result in a ENOENT instead of launching.
I'm 100% sure of the path. I copied it directly from the .exe
I tried changing the cwd as well and still the same ENOENT
I experimented some more and I don't think there's anything you can do. It seems the game is nested in a "launcher" process. I'll try to write a middleman for it.
I was trying to make this debugger work with the game "Sapiens". When launched, node.js indicates the childprocess immediately exited with code 0 even though the game is still running. So I thought it was probably running under an other process which exited but let its child live.
So I tried a couple of things like turning off "shell" or "detached" but they result in a ENOENT instead of launching. I'm 100% sure of the path. I copied it directly from the .exe I tried changing the cwd as well and still the same ENOENT
If you know what to do, please let me know