I'm so close to getting WAN to work... I think

Alright, well, using both Hex Editing and the modified .jar launcher, I've come to a semi-conclusion that 127.0.0.1 works for my login server, while the rest of my servers are on my external IP - 68.xxx.xxx.69 (The x's are particular, both middle regions are 3 numbers)

So, is it that my xx.xxx.xxx.xx IP address is too long? Because trying my internal IP address at 192.168.1.100 also failed.

I am behind a Linksys WRT54GS router, and I have tried DMZ bypass, but I have yet to try bypassing the router entirely. I also have yet to see if it is just myself that is unable to connect - I have an unmodified ProjectG.exe, a modified one that I'm working with, and the one that came in my repack, ProjectG_Offline.exe

Any insight? I'm really not in favor of setting up a SOCKS connection... but if it's my only option I may have to go with it. I will absolutely not be using Hamachi for this - it's far too vulnerable for a game I can play for free on the legitimate website.

Yeah, your IP is too long.. any combo of 8 digits be it xx.xx.xx.xx or xxx.x.xxx.x or whatever but anything longer will not work.

Is there anything I can do about this? I've gotten so far and I don't want to just ditch all the work I've thrown into this. Is there really no way to make the Pangya client connect to an IP address longer than 8 digits?

Whats the IP you've inputted into the server ini-files?

Are you using NAT?

If you are using NAT, are you also NATing your WAN IP so your LAN can use this?

I'll PM you my IP address. My router is more than likely using NAT but I was sure that by using DMZ I would be able to circumvent it.

Currently my friends and I are making due with Hamachi... sigh... but if I can get it to work with my actual IP address, it would be wonderful.

Well, it turns out I cannot PM until I have 15 posts.

So, I cannot give you my full IP address but it is of the following digit count.

[xx.xxx.xxx.xx (68._ _ _._ _ _.69)]

And thats what you've typed in the ini-files?


I havent set any of this up yet but heres how i would do it:

Forward the ports in the router and obtain routers WAN IP
NAT WAN IP to LAN IP (on lanside, to be able to connect to the WAN IP from the LAN)
input WAN IP into server ini-files
Hex the client exe or use the launcher

it should work.

Okay, I'll have to give that a shot when I'm not dead tired. But yes, my IP address was in all ini files and hexed into the client (and the launcher, additionally, was attempted). All other programs that require forwarded ports have been defeated using DMZ for me, so I was fearing that what gryph1 said is the actual reason. Now that the logon server is my Hamachi IP address (which is an 8 digit IP in the form of

x.xx.xxx.x)

and that IP was hexed in, everything is working as intended so far.

An ip along with dots can be 15 chars at Max.
Posted via Mobile Device

---------- Post added at 12:27 PM ---------- Previous post was at 10:55 AM ----------

I think i found it, the offset i have in the launcher is the wrong one for the loginserver.

Ill check this and return with the result
Posted via Mobile Device

Well, just so everything is clear, the modified .jar launcher works as well. As well as all of my servers work on my external IP address. [xx.xxx.xxx.xx] But, the client wont connect to the login server when I hex in an IP address that long - but does with a shorter IP address, ala Hamachi. [x.xx.xxx.x]

So I figure I can cut lag to a minimum if the game's login is the only Hamachi-based transfer, while the gameserver and authentication server are real-time from me.

I think i found a solution!

I will post back when ive tested it!

---------- Post added at 11:41 PM ---------- Previous post was at 10:40 PM ----------

Woha! I made it work!

Try the updated pangyaLauncher!

Had a chance to try the launcher? Let me know if your having problems
Posted via Mobile Device

Sorry about that wait - thank you chreadie, it works now.

Awsome!
Posted via Mobile Device