Morrighan - Client proxy

[exec]

27 minutes ago, Nerguri said:

ps. 'avast!' is discovered virus in this file.

lol, that's a new one. Well, it's a false positive. I'm not sure why it would even think that o.o

[exec]

Update 1.5.7

• NA218 support. Server packets aren't encrypted anymore, just like in KR.

Going forward Morrighan will not be compatible with NA <218 anymore, due to the change in the encryption. If you want to use Morrighan with an older version, use 1.5.6, both are available on GitHub (see download link in the first post). The change on NA doesn't make a difference for Aura in terms of logging, as we never encrypt server packets.

[Nerguri]

Thx!

[Omega]

Morrighan isn't working for me: neither MabiCommerce or MabiPale can connect to it. My packet list stays empty just like it did with the guy above.

It is very odd that it would be broken though, because Kanan Open Source Patcher added a "Start with Morrighan" windows batch file very recently. Seems odd that they would add this convenience to something not working at the moment. I didn't just try to run it with that patcher either. I also tried to use the included MorriOneClick tool.

Here is my Morrighan.log from what I guess is my last attempt before coming here for help. I am shocked that It recognized MabiCommerce subscribing but nothing worked as it should.

11/1/2016 4:49:05 AM [Info] - Morrighan 1.0.5862.36118
11/1/2016 4:49:05 AM [Info] - Starting server...
11/1/2016 4:49:05 AM [Info] - Server listening on '127.0.0.1:11669'
11/1/2016 4:49:05 AM [Info] - Starting Alissa communicator...
11/1/2016 4:49:05 AM [Info] - Starting client...
11/1/2016 4:49:05 AM [Info] - Started client: Client.exe code:1622 ver:237 chatip:208.85.109.37 chatport:8002 setting:"file://data/features.xml=Regular, USA" logip:127.0.0.1 logport:11669
11/1/2016 4:49:05 AM [Info] - Morrighan is ready to serve you
11/1/2016 4:49:52 AM [Info] - Client connected from 127.0.0.1:11681
11/1/2016 4:49:52 AM [Info] - Tunneling connection to '208.85.109.35:11000' through '127.0.0.1:11669'
11/1/2016 4:49:53 AM [Info] - Client closed connection
11/1/2016 4:49:53 AM [Info] - Server listening on '127.0.0.1:11669'
11/1/2016 4:50:01 AM [Info] - Client connected from 127.0.0.1:11686
11/1/2016 4:50:01 AM [Info] - Tunneling connection to '208.85.109.35:11000' through '127.0.0.1:11669'
11/1/2016 4:50:26 AM [Info] - Client closed connection
11/1/2016 4:50:26 AM [Info] - Server listening on '127.0.0.1:11669'
11/1/2016 4:50:27 AM [Info] - Client connected from 127.0.0.1:11694
11/1/2016 4:50:27 AM [Info] - Tunneling connection to '208.85.109.45:11020' through '127.0.0.1:11669'
11/1/2016 4:50:39 AM [Info] - Application subscribed: 'MabiCommerce'
11/1/2016 4:51:27 AM [Info] - Application unsubscribed: 'MabiCommerce'
11/1/2016 4:51:34 AM [Info] - Application subscribed: 'MabiCommerce'
11/1/2016 4:51:48 AM [Info] - Application unsubscribed: 'MabiCommerce'
11/1/2016 4:51:53 AM [Info] - Client closed connection
11/1/2016 4:51:53 AM [Info] - Server listening on '127.0.0.1:11669'
11/1/2016 4:51:57 AM [Info] - Client is closing...
11/1/2016 4:51:57 AM [Info] - Server stopped

 

[exec]

18 minutes ago, Omega said:

It is very odd that it would be broken though

That's because it's not^^ The problem must be somewhere on your side.

In your log I only see MabiCommerce, but if you connect with Pale, does it show the "Application subscribed" message as well? And can you play normally while using Morrighan?

[Omega]

No, it apparently does not:

11/1/2016 5:31:14 AM [Info] - Morrighan 1.0.5862.36118
11/1/2016 5:31:14 AM [Info] - Starting server...
11/1/2016 5:31:14 AM [Info] - Server listening on '127.0.0.1:12210'
11/1/2016 5:31:14 AM [Info] - Starting Alissa communicator...
11/1/2016 5:31:14 AM [Info] - Starting client...
11/1/2016 5:31:14 AM [Info] - Started client: Client.exe code:1622 ver:143 chatip:208.85.109.37 chatport:8002 setting:"file://data/features.xml=Regular, USA" logip:127.0.0.1 logport:12210
11/1/2016 5:31:14 AM [Info] - Morrighan is ready to serve you
11/1/2016 5:31:49 AM [Info] - Client connected from 127.0.0.1:12222
11/1/2016 5:31:49 AM [Info] - Tunneling connection to '208.85.109.35:11000' through '127.0.0.1:12210'
11/1/2016 5:31:50 AM [Info] - Client closed connection
11/1/2016 5:31:50 AM [Info] - Server listening on '127.0.0.1:12210'
11/1/2016 5:31:59 AM [Info] - Client connected from 127.0.0.1:12225
11/1/2016 5:31:59 AM [Info] - Tunneling connection to '208.85.109.35:11000' through '127.0.0.1:12210'
11/1/2016 5:32:17 AM [Info] - Client closed connection
11/1/2016 5:32:17 AM [Info] - Server listening on '127.0.0.1:12210'
11/1/2016 5:32:17 AM [Info] - Client connected from 127.0.0.1:12231
11/1/2016 5:32:17 AM [Info] - Tunneling connection to '208.85.109.45:11020' through '127.0.0.1:12210'
11/1/2016 5:33:00 AM [Info] - Client closed connection
11/1/2016 5:33:00 AM [Info] - Server listening on '127.0.0.1:12210'
11/1/2016 5:33:05 AM [Info] - Client is closing...
11/1/2016 5:33:05 AM [Info] - Server stopped

Well then it's possible that MabiCommerce broke, and that's why it doesn't update prices after subscribing, but I need to get pale to work.

Yeah I can play the game just fine with Morrighan

[exec]

You are clicking on connect in Pale though, right? And you're not getting any errors? (Also check the error log tab in options.)

[Omega]

MabiPale's Connect button works just as one would expect, it grays out because it's supposed to be connected and the Disconnect button becomes available. There is no error pop-up (if hat's what's supposed to happen on error), and the error log in the Settings is blank.

Here's something interesting. If I exit the game without disconnecting Pale, the Diconnect button grays out and the Connect button becomes available. The program knows that it successfully connected to Morrighan, so for some reason I am not getting any packets.

My Windows Firewall is turned off in case you're wondering. I turned it off just to troubleshoot this.

Perhaps I am not using the program properly in some other way? I thought I was supposed to open it up and hit connect, get packets or a running packet log then I could save those to file. Am I suppose to use the Open dialogue for something first?

[exec]

And when you're connected, there's no mention of Pale in Morrighan's log...? Does Morrighan's window "light up"?

[Omega]

It's been a long enough time since I've used it that I don't remember the small Morrighan window or taskbar button lighting up being a feature. If that's what it's suppose to happen, then it's certainly not happening for me right now. For Some reason, now I can't even get MabiCommerce to show up in the Morrighan log anymore. Like it was just able to subscribe for that one run and now it won't show up

Every subsequent Morrighan log I have now looks exactly like the one I most recently posted by with new time stamps

[exec]

What I mean by "light up" is that the grey should turn kind of gold when Pale or any other subscriber connects to Morrighan. That not happening would be a new problem that we haven't had before iirc. If you don't click "Connect", but "Connect to...", what do you get?

[Omega]

Yeah, that gold color thing doesn't happen for me. It shows the the dialogue box with a combo box containing "TFormAlissa". I've tried connecting with that dialogue box before and it made no difference.

[exec]

I'm honestly at a loss here, I don't understand why Pale would be able to connect without Morrighan properly accepting the connection. Have you tried restarting your PC? It seems like it did work at first with MabiCommerce after all.

[Omega]

Restarting my PC did not work.

Well... I am a programmer. So I could download the sources of one or both applications and breakpoint in an attempt to find out what is happening. However, I've never examined the source for either and I would have preferred not to spend so much time on this. If you'd like me to debug this issue, can you tell me where would be the most relevant file or lines to look at, and if you were having this problem, where would be the initial place you'd think to break at?

I'm really doing this because I want to log an old account I retrieved from support. If I can't get Pale to work, I suppose the last thing I can just take screenshots, which is highly error prone and it's going to suck if I miss one. Fixing this issue is the better option.

Edited November 1, 2016 by Omega

[exec]

The thing is, I don't know where to start. Morrighan and Pale use SendMessage to communicate, and a connection is more of a subscription, Pale telling Morrighan to send it data. For you Pale can see Morrighan, so it can "connect" to its window, sending a subscription message to Morrighan. Morrighan however doesn't log that it received the message, which must mean it never arrived. There's nothing to check in between those two.

My only idea right now is that SendMessage might not work properly on your system for some reason, maybe because of a security restriction, but I haven't found much regarding that yet, except for someone mentioning User_Interface_Privilege_Isolation.

Are you running Pale and Morrighan as admin?

[Omega]

It was indeed a privilege issue. By my use of Kanan's patcher, I run Morrighan in administrative access but I had not tried doing that for running MabiPale or MabiCommerce. Thanks for the help: perhaps you should add this as a note to the instructions on how to use either program.

It never used to be required before but you know how Windows 10 is: always changes things without notifying the user.

Edited November 2, 2016 by Omega

[exec]

This is indeed good to know, thanks. Maybe there's a way I can check for that in Pale, so it's not something one has to actively watch out for.

[exec]

Update v1.6.0

• Added tray icon and minimization
• Added G13 server support using parameter "jpG13"

[neverReply]

Hi exec, I try to use Morrighan on the mabinogi China client but I have a problem. I first create a Morrighan.bat file with following command
Morrighan.exe code:1622 verstr:343 ver:343 locale:China env:Regular setting:file://data/features.xml logip:35.162.171.43 logport:11000 chatip:54.214.176.167 chatport:8002 nxlauncher
After that, I put both Morrighan.bat and Morrighan.exe into the Mabinogi game folder, and then I launch the Mabinogi.exe. The China mabinogi launcher has two steps to start the game. First I need to click the "Patch Start" button, and the launcher will check all pack files and possible updates. If everything is ok and up-to-date, the button will change to "Game Start". At this time, I launch the Morrighan.bat and follow the pop-up instruction to click the "Game Start" button. However, an error appears and says that "Failed to create log file, make sure Morrighan isn't running already". I am not sure how to fix it.

[exec]

I would guess that Mabinogi CN uses different start parameters, which Morrighan fails to handle. The nxlauncher method is mainly geared towards NA, and if another region doesn't use the same launcher parameters, it won't work there. What I'd need to know are the parameters that the CN launcher passes to the Client.exe on start.