4 commits

Author	SHA1	Message	Date
Daniel Gibson	b38aff8995	Fix sending clients from lobby to game when lobby and game are on same server ... In the current case (only "direct" lobby backend, i.e. connect to a server directly), lobby and game are always on the same server anyway.. It used to send the IP of the first network interface.. that kinda works on Windows and FreeBSD in LANs (i.e. not over the internet or even behind a NAT), but not at all on Linux, because the first device seems to be the loopback device there (at least on my machine).. Now it sends net_ip (so it should even work behind NAT) or, if net_ip is set to "localhost" (the default), 0.0.0.0 is sent, which the client interprets as "just use the IP of the lobby you're already connected to"	2013-03-17 23:35:12 +01:00
Daniel Gibson	ee88148bd1	eliminate more longs ... for 64bit compatibility.	2012-12-13 01:28:41 +01:00
Robert Beckebans	f55a763ca4	Formatted code using Artistic Style for better readability.	2012-11-28 16:47:07 +01:00
Brian Harris	5016f605b8	Initial commit	2012-11-26 12:58:24 -06:00