Jump to content
  • 0

0x09d4,2 unknown (but known) version


kyrato

Question


  • Group:  Members
  • Topic Count:  19
  • Topics Per Day:  0.00
  • Content Count:  84
  • Reputation:   1
  • Joined:  11/06/13
  • Last Seen:  

Alright so this packet IS defined in packet_db.txt in both 46 and 47. different names though. 

 

im using 20131223 ragexe and that is in my mmo.h

 

packet_db_ver: 46

 

<version>46</version>

 

not sure what could be my problem here. 


server seems to think my client is 45, not sure why or what to change.

 

[info]: 'Lesper' logged in. (AID/CID: '2000001/150016', Packet Ver: '45', IP: '1
27.0.0.1', Group '99').
[Warning]: clif_parse: Received unsupported packet (packet 0x09d4, 2 bytes recei
ved), disconnecting session #3.
[info]: Character 'Lesper' logged off.

and ive set my packet_db.txt to 45,46,and 47 to no avail.

Link to comment
Share on other sites

2 answers to this question

Recommended Posts


  • Group:  Members
  • Topic Count:  19
  • Topics Per Day:  0.00
  • Content Count:  84
  • Reputation:   1
  • Joined:  11/06/13
  • Last Seen:  

Both are disable actually :(

And that packet is a real packet for 46 and it even had 2 bytes like the packet_db.txt shows... I think the issue revolves around the server thinking it's a 45 client. But I don't know where to explore that theory

ok so i know this is probably not what im supposed to do. BUT. it worked

 

so i tried adding the 0x09d4,2,npcshopclosed,0 part to the packet_ver: 45 area but that didnt work. 

 

then i saw this 0x09D4,2,dull,0  //npcshopclosed line in someone else's packet_db.txt and i added it instead and it actually worked out.

 

i cant explain much more than that, but using 20131223c, it shows up in the mapserver as packet_ver: 45 and this packet definitely comes in packet_ver: 46 according to the SVN.

Link to comment
Share on other sites


  • Group:  Development Manager
  • Topic Count:  56
  • Topics Per Day:  0.01
  • Content Count:  732
  • Reputation:   525
  • Joined:  12/13/11
  • Last Seen:  

I'm assuming you didn't disable Packet Obfuscation via source or your client isn't setup properly for packet obfuscation.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...