MatchAgent don't work anymore

[alfredao]

After I did the tutorial of Lambda to run more the one server, MatchAgent stopped working, NAT message appears, but still with Agent Error.

[MentaL]

[cerealnp]

I have the same problem, already tried to search for matchagent ports on ollydbg, but i have found nothing. Can someone help us?

[alfredao]

The ports of MatchAgent is on AgentConfig.xml, i changed ports but don't work

[JuanMedina]

ye the same thing

[bunny1995]

i dun think people will release this kind of tut, even if they release i dun think it will works, only some pros like wizkid had his server with 2 or more servers.

[Creativity]

don't you have to also edit the client site ?

[Hakurah]

The tutorial is in the tutorial area... Just search for "Agent Error" and there's a tuto by Lambda that works.

[Demantor]

You may write this on Lambda's tut?

[~Fallen]

i dun think people will release this kind of tut, even if they release i dun think it will works, only some pros like wizkid had his server with 2 or more servers.

wrong wrong wrong. maybe b4 but this is something like common sense now...

[cerealnp]

Fixed it:

void __stdcall MMatchClient__SendCommandByUDP( MCommand* pCommand, const char* szIP, int iPort )
{
	/* here you need to edit the IP's with your server ips and port, for example if the quest server has the UDP port 5601 
	   you need to edit the correct line and put your IP and port. */

	if( strcmp( szIP, "The freakin' 2nd server IP" ) == 0 )
	{
		if (iPort == 7777)
		{
			iPort = 7788;
		}
	}
}

MatchAgent also uses UDP ports to send and recive data, Lambda's dll is currently intercepting all calls to your server ip and changing it to your matchserver port, thats why matchagent was conflicting, cuz it was being redirected to the same port as the second matchserver. You don't need to change nothing on your first server IP if you use the default port (7777). I've used 7788 port for the second server but you can change it to whatever you want.