5250 source confusion

<edit>

Figured out what was confusing me so much. 5250 uses port 9959 rather than 9958 like earlier versions for it's initial connection which was confusing me.

I'll update thread as I run into other annoying problems >.<

Alright fyi i didn't read it all up (damn.. too large), but i'm guessing you can't start a connection.
Have you added the password seed packet? if you don't send it on connection to the client, it won't continue the sequence.
it's 8 bytes long, type 1059 (don't remember well, or was it 1056), just log it off tq's servers.

Quote:

Originally Posted by Nullable Alright fyi i didn't read it all up (damn.. too large), but i'm guessing you can't start a connection. Have you added the password seed packet? if you don't send it on connection to the client, it won't continue the sequence. it's 8 bytes long, type 1059 (don't remember well, or was it 1056), just log it off tq's servers.

Actually I wasn't even dealing with login yet.

It seems that 5250+ changed the login port?


just as a simple test I made a simple program using winsockets and listened on port 9958. With a 5165 client (or 5095 even) it detects that something is trying to connect but 5250 does nothing. Doesn't even try.

THAT is what was confusing me more than actually working out how to login/authenticate the connection.

5250 starts with port 9959 rather than 9958... not quite sure why but w/e. Gives me a starting point... Now I just need to start handling the rest of it.

As far as i understood it works now, and for client versions higher than 5210, the login port is 9959 (can't figure out why did tq change it, wouldn't affect bots in any way..)

That's weird; my client seems to be connecting to 9958, not 9959.
It's version 5263.

Some server groups will still connect to 9958, don't remember which connects to 9959, but for the record they include Constellations, Wonders, Elements and Celeberations.
I will include port writing later in the loader.