It could be done, but whoever connects to the server will be able to read the server's IP no matter what you do. It's just how things work.Quote:
Nullable you think you can do a version of this that hides your IP? Just incase some one wants to hack you it's encrypted >.<
Actually I am using an official install, patch 5250. Also a win 7 x64, and I don't have any single issue with it.Quote:
For some reason this is not working for me.
It starts CO, but it simply doesn't connect.
Patch 5250 - uses the official patch.
Running windows 7 - 64 bit, running the application as an Administrator.
What I'm trying to suggest is, waiting for the password seed makes it patch dependent, giving the option to leave it out, makes it patch independent, or at least your 1 step closer.Quote:
Let me explain to you what you're trying to suggest, remove all the password encryption routine in the client and edit it to send login request directly on connection to auth server, don't you think this is just too much for a simple 8 bytes-sized packet? Let alone it is not a simple task (and I am not too fluent with assembly yet to do it).