Morrighan
Morrighan copied to clipboard
exectails
Morrighan.exe refuses to give logfile access to the fake Client.exe
I'm trying to get Morrighan to work through the Steam special launcher, but every time it should receive the hash the fake Client.exe errors about failing to make a log file due to another instance of Morrighan already running, and halts execution at that point so it never captures the hash like it should.
After some investigating, I've found that the real Morrighan.exe is refusing to give log file access to the Client.exe one when the launcher calls Client.exe. I'm trying to figure out a way to make it work, but no luck so far.
I've had the Steam launcher execute the fake Client.exe after forcing the real Morrighan.exe to close through task manager. Without Morri tying up the log file, the fake Client.exe doesn't error out and correctly captures & logs the login hash, but ofc it can't communicate back to Morrighan and nothing happens except a ton of Morrighan instances being executed simultaneously.
Basically everything works except both Morrighan.exe and Client.exe want to use the same log file and both refuse to share.
There are also 119 Morrighan.TFormAlissa###.log files in my folder now, too.
Hi, could you tell me more about your setup and how Steam starts Mabinogi? I've actually never used Mabi through Steam and I can't even download it from Germany without jumping through hoops. It sounds like either your approach is incorrect or Steam works differently from the Nexon Launcher that Morrighan was designed for.
Steam installs Mabinogi in "C:\Program Files (x86)\Steam\steamapps\common\Mabinogi", which is where client.exe sits. When you launch through Steam it runs a special launcher called 'nxsteam.exe', and as mentioned above it's just a special NX launcher that automatically uses your Steam credentials (linked to your NX account) for logging in, and it'll pass the hash to the fake Client.exe fine.
Just like with the normal launcher it'll do the login stuff, then it'll try to launch Client.exe. After that Mabinogi runs the same as if you'd launched through the NX launcher.
As for the setup I've used, I put Morrighan.exe into Steam's Mabinogi folder where Client.exe is. When I run Morrighan.exe with the parameters provided, it creates Morrighan.log and replaces Client.exe with a copy of itself (renaming the original to Client.exe.Morrighan.bak) and shows a window with instructions. When nxsteam.exe is run, Client.exe is executed and it immediately gives an error about how it cannot create Morrighan.log since the log file is already in use by the real Morrighan.exe ofc.
The problem is that Morrighan looks for a special parameter that the NX launcher passes to the client.exe, -NXAL, which Steam presumably doesn't use. Without that parameter it assumes the client should just be started, which then leads to this error. The easiest way to fix this would be to look for a Steam specific launch parameter in addition to the NX launcher one, provided that one exists.
Could you check what parameters nxsteam passes to the client.exe?
