Hey everyone.
I know how hard it is to code features when you don't understand how the feature works or what packets you should be using, so here's my packet log and analysis for interface items:
Packet Log:
My Analysis:
The interface item packet is similar to the item information packet (1008). It's used for multiple functions, such as updating equipment on the character and showing items in interface windows such as a shop in the market. This packet can be useful when coding features such as dyeing equipment. When the color is changed, instead of sending a large spawn packet to everyone in the shop, and instead of unequipping, sending an item packet, and sending the equip packet, you can send this packet. The packet starts with two identities (the item id and character/interface id - not particularly in that order). It then goes to the type of packet it is (what it'll be updating), and then finishes with the item's information. The client doesn't request it at any time from the server. It's the server that sends the packet (and that's it).
Picture:
I know how hard it is to code features when you don't understand how the feature works or what packets you should be using, so here's my packet log and analysis for interface items:
Packet Log:
Code:
Packet 3 -- From: TQServer -- Length: 84 | Receive Length: 92 -- Type: 1108
54 00 54 04 A7 46 5E 0E 39 F6 16 00 00 00 00 00 ; T T§F^9ö
29 10 02 00 77 0E 02 10 02 00 03 00 00 00 00 00 ; ) w
0D 00 00 00 00 00 00 00 00 05 00 00 47 00 00 00 ;
G
00 00 00 00 00 00 01 00 09 00 00 00 28 00 00 00 ; (
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ;
00 00 00 00 54 51 53 65 72 76 65 72 ; TQServer
The interface item packet is similar to the item information packet (1008). It's used for multiple functions, such as updating equipment on the character and showing items in interface windows such as a shop in the market. This packet can be useful when coding features such as dyeing equipment. When the color is changed, instead of sending a large spawn packet to everyone in the shop, and instead of unequipping, sending an item packet, and sending the equip packet, you can send this packet. The packet starts with two identities (the item id and character/interface id - not particularly in that order). It then goes to the type of packet it is (what it'll be updating), and then finishes with the item's information. The client doesn't request it at any time from the server. It's the server that sends the packet (and that's it).
Picture:
