Hi everyone,
I'm setting up TMP4's r40250 reference serverfile on a real cloud VPS (not the bundled VM), and I've got the server fully compiled and running (db + auth + channel1, all connected to MySQL successfully, no errors in syserr).
The issue is on the client side. When I open Client.zip's Metin2Distribute.exe, I get "Error while connecting to the server" — turns out (confirmed via Process Monitor) the client is hardcoded to connect to 192.168.0.122:11000. I couldn't find this IP as plain text or raw bytes anywhere in the exe/dlls, so it must be inside pack/root.epk (encrypted, MCOZ header).
I set up a local port-forward (192.168.0.122:11000/13000-13002 → my real server) as a workaround, which got me past the error to "You will be connected to the server...", but it hangs there forever. On the server side, auth/packet_info.txt shows Handshake: 0 — the server never even registers the connection attempt at the application level, even though the TCP connection shows ESTABLISHED.
Questions:
Is there a known/safe tool to unpack root.eix/root.epk so I can find and edit the target IP directly (instead of the port-forward hack)?
Someone mentioned "FoxFS" for this — is that the right approach, and where can I find the current version/tutorial?
Could the "Handshake: 0" issue be something else entirely (client/server version mismatch, RSA key mismatch)?
Thanks in advance!
