Conquer Resource Wiki

CptSky · 07/13/2010, 16:14

Quote:

Originally Posted by .Arco

Would be nice to tell us what patch this is for

The patch with the new password encryption

-impulse- · 07/13/2010, 22:17

Quote:

Originally Posted by Korvacs

Whats Junk?

Timestamp or character's uid.

Korvacs · 07/16/2010, 20:15

Quote:

Originally Posted by -impulse-

Timestamp or character's uid.

I guessed that much, i need to know which lol

Basser · 07/16/2010, 23:09

Quote:

Originally Posted by .Arco

Would be nice to tell us what patch this is for

Obviously its the new password encryption, pretty sure its around 5180.

~~-Fáng-~~ · 08/04/2010, 07:04

"EntityMovement" Packet for 5165 needs to be changed (?):
------------------------------------------------------

Code:

 Version 5165:
Packet Layout   
Offset      Type        Value
0 	    ushort 	16
2 	    ushort 	10005
4 	    uint 	Direction
8 	    uint 	Entity_ID
12 	    uint 	Timer

=]

Korvacs · 08/04/2010, 09:41

You dont have the speed bool in there....

~~-Fáng-~~ · 08/04/2010, 10:49

Quote:

Originally Posted by Korvacs

You dont have the speed bool in there....

Yah. Doesn't work with it in there.

Korvacs · 08/04/2010, 10:51

Then your structure is wrong, there is a speed bool in there somewhere.

~~pro4never~~ · 08/05/2010, 02:40

ok couple super simple packets that I'm fairly sure were already logged before... I don't remember seeing them but I'm confident they must be somewhere

Password seed packet: Sent Server>Client when it connects to login server

Offset	Type	Value
0	ushort	8
2	ushort	1059
4	uint	Value

Value should just be a random password seed value. Save the number to the char so that you can interpret the password when it's sent.

And Sadly I don't have all the values logged for it yet but maybe someone can fill in the blanks for me..

5290+ auth packet: I have enough values so that it can be interpreted nicely for proxies but sadly not enough info to properly write a custom packet...

Server>Client sent once login details are confirmed. length 52 for valid login, 32 for invalid.

Offset	Type	Value
0	ushort	52
2	ushort	1055
4	uint	CharUID
8	uint	Key
12	uint	Port
16	ushort	Junk
18	ushort	Junk 2 (or combined)
20	string	IpAddress

Junk and junk 2 I'm not sure what they do... They are unique to your character though.

Char UID, Junk and Junk 2 remain constant with the same character but if you log a diff char they change. Not sure what the value is referring too though. I separated them into 2 ushorts rather than a uint to see if they made more sense that way but they are still rather strange.

<edit> works to make functional 5290+ login server even w/ the unknown junk values. Fixed the typo. Length for valid is 52 not 55. Thanks for pointing it out

Not sure how useful those will be to ppl but seeing as I logged them lastnight figured I'd share. If anyone needs some packet structures for current tq patch I could whip up a few. I think most of them are still fairly similar to 5200 though.

tanelipe · 08/05/2010, 20:05

You should try XORing what you call as junk with character uid, key or port and see if it makes anymore sense, lol. That's what TQ usually does. (Well the UID part anyways.)

~~pro4never~~ · 08/05/2010, 20:35

Quote:

Originally Posted by tanelipe

You should try XORing what you call as junk with character uid, key or port and see if it makes anymore sense, lol. That's what TQ usually does. (Well the UID part anyways.)

Good idea. I simply left as they were because it works perfectly fine if you just set them to a constant value (I used a random one I logged from tq server and set it to that). Works perfectly fine for me to be able to login now so I figured I'd post it as is.

_DreadNought_ · 08/05/2010, 23:49

Quote:

Originally Posted by pro4never

ok couple super simple packets that I'm fairly sure were already logged before... I don't remember seeing them but I'm confident they must be somewhere

Password seed packet: Sent Server>Client when it connects to login server

Offset Type Value
0 ushort 8
2 ushort 1059
4 uint Value

Value should just be a random password seed value. Save the number to the char so that you can interpret the password when it's sent.

And Sadly I don't have all the values logged for it yet but maybe someone can fill in the blanks for me..

5290+ auth packet: I have enough values so that it can be interpreted nicely for proxies but sadly not enough info to properly write a custom packet...

Server>Client sent once login details are confirmed. length 55 for valid login, 32 for invalid.

Offset Type Value
0 ushort 55
2 ushort 1055
4 uint CharUID
8 uint Key
12 uint Port
16 ushort Junk
18 ushort Junk 2 (or combined)
20 string IpAddress

Junk and junk 2 I'm not sure what they do... They are unique to your character though.

Char UID, Junk and Junk 2 remain constant with the same character but if you log a diff char they change. Not sure what the value is referring too though. I separated them into 2 ushorts rather than a uint to see if they made more sense that way but they are still rather strange.

Not sure how useful those will be to ppl but seeing as I logged them lastnight figured I'd share. If anyone needs some packet structures for current tq patch I could whip up a few. I think most of them are still fairly similar to 5200 though.

Thanks got me logged in 5291 with that

btw guys alot of packets changed alot you should see what happens when I try to: Change direction/Jump/Walk/Equipment(Whole new packet involved)/Character info(Pretty much that mostly)/Cps/BoundCps/Entity spawn/Itemlock/CreateCharacter(You can create it, it will get 40% on the screen that says 'Character was successfully created' but just Alt + F4 then relog and you can login)/General Data/Chat and alot more.

fm_sparkart · 08/14/2010, 10:58

Quote:

Originally Posted by pro4never

ok couple super simple packets that I'm fairly sure were already logged before... I don't remember seeing them but I'm confident they must be somewhere

Password seed packet: Sent Server>Client when it connects to login server

Offset Type Value
0 ushort 8
2 ushort 1059
4 uint Value

Value should just be a random password seed value. Save the number to the char so that you can interpret the password when it's sent.

And Sadly I don't have all the values logged for it yet but maybe someone can fill in the blanks for me..

5290+ auth packet: I have enough values so that it can be interpreted nicely for proxies but sadly not enough info to properly write a custom packet...

Server>Client sent once login details are confirmed. length 55 for valid login, 32 for invalid.

Offset Type Value
0 ushort 55
2 ushort 1055
4 uint CharUID
8 uint Key
12 uint Port
16 ushort Junk
18 ushort Junk 2 (or combined)
20 string IpAddress

Junk and junk 2 I'm not sure what they do... They are unique to your character though.

Char UID, Junk and Junk 2 remain constant with the same character but if you log a diff char they change. Not sure what the value is referring too though. I separated them into 2 ushorts rather than a uint to see if they made more sense that way but they are still rather strange.

Not sure how useful those will be to ppl but seeing as I logged them lastnight figured I'd share. If anyone needs some packet structures for current tq patch I could whip up a few. I think most of them are still fairly similar to 5200 though.

The first 2 bytes for me is 34 0 => 52

~~pro4never~~ · 08/15/2010, 05:16

Quote:

Originally Posted by fm_sparkart

The first 2 bytes for me is 34 0 => 52

Sorry i must have typod. Just loooked at my source and it's 52 for me also. I'll edit it

fm_sparkart · 08/15/2010, 17:21

What is the packet structure for the key exchange?

Right now I receive a packet of size 186, I just relay it to the client because I am not sure what to do with the packet. I am not sure how to get the keys because I am not sure how the packet is structured.