Difference between revisions of "Crafting (Sequence)"
| Line 1: | Line 1: | ||
| + | [[GameSystemPackets|Baaaaaaaaaaaaaaaaack]] | ||
| + | |||
=Description= | =Description= | ||
| Line 23: | Line 25: | ||
| − | = | + | =The Sequence= |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | |||
| − | |||
On using or doubleclicking the craft item the client sends 3 Packets, through which a crc list of the available schematics is requested. | On using or doubleclicking the craft item the client sends 3 Packets, through which a crc list of the available schematics is requested. | ||
Revision as of 09:26, 2 April 2007
Description
The crafting process is monitored in the Player Object. The relevant values are set through the Yalp 9 at initialization and / or changed through the relevant deltas in the crafting process.
Packetflow
| Client <-> Server Sequence: Survey UI |
|
{{{2}}} |
The Sequence
On using or doubleclicking the craft item the client sends 3 Packets, through which a crc list of the available schematics is requested.
For starters let us break it down into the steps needed to open up the different craft-screens
Step 1 opening the 1st crafting screen
1) client -> server radial menu request Packet
2) client -> server F9996AB6 synchronizeduilisten
3) client -> server 094AC516 requestcraftingsession
server response
4) server -> client Menu response
5) server -> client Schematic List
client response
10) client -> server 5FD21EB0 requestdraftslotsbatch
11) client -> server 9A8B385C requestresourceweightsbatch
server response
12) server -> client answer : requestdraftslotsbatch
14) server -> client answer : requestresourceweightsbatch
opening the 2nd crafting screen
client
18) client -> server ObjectControllerMessage selectdraftschematic request to open the 2nd craft screen
server
(20) server -> client MSCO Object (init, link, 3,6,8,9, close schem object))
(21) server -> client ONAT Object (init, link, 3,6,8,9, close schem object))
16) server -> client blueprints
