View source for Datapad Schematics (Sequence)

On loading the Player Object during logging in, the server sends in the Yalp 9 Packet a list of all Schematics that are available to the player.  [[PKT Player Object Initialization|for reference : Player Object Initialization]] 

On opening the Datapad and selecting a schematic for looking at it, the client sends a request to the server for further Information about the looked at schematic. There is one Packet send to request the Slot Information and one Packet send to request the Attribute Data.


{{Box Packet|Object_Init Client --> Server|
<pre>
00 09 00 15 00 19 5A 05 00 
this Packet requests the Slot Data - 1 Slot = 1 place to put a resource / whatever in

46 5E CE 80 					AMSG_INT_PACKET
23 00 00 00 					INT 1
16 01 00 00 					INT 2

E5 55 DB 70 05 00 00 00 			Player ID

00 00 00 00 00 00 00 00 

B0 1E D2 5F 					requestdraftslotsbatch

00 00 00 00 00 00 00 00 

16 00 00 00 					Unicode string length

33 00 38 00 35 00 36 00 35 00 36 00      	3.8.5.6.5.6.7.5.4.3.. 0xe5de8cf7 This is schematic ID
37 00 35 00 34 00 33 00 20 00 32 00 		2.1.4.8.9.0.3.3.8.0. 0x8015a9d4 Next schematic ID
31 00 34 00 38 00 39 00 30 00 33 00 		two ids seperated by 20 00 and end of string marked through 20 00
33 00 38 00 30 00 20 00 			these are both ids send to the datapad through the Yalp in the exact same order
						please note that the second is the crc of the schematic in this case its the solar
                                                tool

Packet 2 : Requests the Attribut Data
						
44 05 00 
this Packet requests the Attribut Data. Not sure what its needed for, see corresponding Packet

46 5E CE 80 					amsg_int_packet
23 00 00 00 					int 1	
16 01 00 00   					int 2

E5 55 DB 70 05 00 00 00 			Player ID

00 00 00 00 00 00 00 00    

5C 38 8B 9A 					requestresourceweightsbatch

00 00 00 00 00 00 00 00 

0B 00 00 00       				size of the Unicode string

2D 00 34 00 33 00 38 00 33 00 39 00 		-.4.3.8.3.9.9.7.5.3
39 00 37 00  35 00 33 00 20 00 


actually that causes me some headache. The ID send in the answer is the exact same as in the other Packet 
and consists of some int and the schem crc. the above value in hex gives us FFFFFFFFE5DE8CF7, from which the 
E5DE8CF7 is the other int that is assigned to the crc.

EB 34                   last two bytes crc
</pre>
}}