Crafting (Sequence) - Revision history

Snow: /* schematic */

2007-12-30T19:38:48Z

‎schematic

2007-12-30T10:10:49Z

‎Prototype Creation

2007-12-29T15:55:06Z

‎Prototype Creation

2007-12-29T10:22:48Z

‎Prototype Creation

2007-12-29T10:20:35Z

‎Customization

2007-12-29T10:17:41Z

‎Assembly report

2007-12-29T10:06:14Z

‎Slot Configuration aka Screen 2

2007-05-07T03:28:01Z

‎experimentation

2007-05-07T03:27:08Z

‎Slot Configuration aka Screen 2

2007-05-07T03:26:35Z

‎Slot Configuration aka Screen 2

@@ Line 220: / Line 220: @@
 The 8th part of the object(var7: incap timer) contains the value to display on the upper right corner of the item. If zero it will display nothing.
-=schematic=
+=Schematic=
 =Cancel Crafting Session=

@@ Line 217: / Line 217: @@
 )Creation of the Actual Item after the creation time, as indicated by the counter on the crafting tool.
-The seconds on the crafting tool are displayed through a tano 3. The 9th part of the object [uint32] contains the value t o display on the upper right corner of the item. If zero it will display nothing.
+The seconds on the crafting tool are displayed through a tano 3.
 =schematic=

@@ Line 209: / Line 209: @@
 =Prototype Creation=
-After the customization Packet, the client sends a [[CommandQueueEnqueue_%2800000116%29|Command Queue Enqueue]] Packet with the CreatePrototyp CRC (0xD61FF415), whidh comes with 2 arguments, first an update counter, second the practice flag.
+After the customization Packet, the client sends a [[CommandQueueEnqueue_%2800000116%29|Command Queue Enqueue]] Packet with the CreatePrototyp CRC (0xD61FF415), which comes with 2 arguments, first an update counter, second the practice flag.
 The server response to this is

@@ Line 209: / Line 209: @@
 =Prototype Creation=
-After the customization Packet, the client sends a [[CommandQueueEnqueue_%2800000116%29|Command Queue Enqueue]] Packet with the CreatePrototyp CRC (0xD61FF415).
+After the customization Packet, the client sends a [[CommandQueueEnqueue_%2800000116%29|Command Queue Enqueue]] Packet with the CreatePrototyp CRC (0xD61FF415), whidh comes with 2 arguments, first an update counter, second the practice flag.
 The server response to this is

@@ Line 201: / Line 201: @@
 =Customization=
 When we hit on the create Prototyp button, we will be taken to the Customization screen. Here we will be able to customize certain aspects of our item (colour, name).
-When done, the client will send the [[CraftCustomization_%280000015A%29|Craft Customization]] Packet, in which the customization options are transmitted.
 We answer this Packet by sending the [[CraftingSlotResponse_%280000010C%29|CraftingSlotResponse 0000010C]] Packet in which we send the Controller ID of the CraftCustomization Message (A5 01 00 00).

@@ Line 143: / Line 143: @@
 In order to be ableto get past the assembly stage, we have to update
-) the experimentation flag (Yalp9 delta, var 1, value >= 1) if we want to experiment
+) the experimentation flag (Yalp9 delta, var 1, value >= 1) if we want to experiment)
 ) the crafting stage (Yalp9, delta var 2, value 3)
-then an MSCO 3 delta, which updates section 5 is send
+)then an MSCO 3 delta, which updates section 5 is send
-and an MSCO 7 delta, which updates section 9, 11,12 and 18
+) generic int response to with the result of the assembly
 the MSCO3 contains  information about basic stats of the object we are going to build.
@@ Line 163: / Line 167: @@
 When everything is send and we hit the next button, we will have to decide whether we want to create a prototype, a schematic, or if we want to experiment.
 This is done by the client WITHOUT further server/client communication

← Older revision		Revision as of 10:06, 29 December 2007
Line 110:		Line 110:
	([[Resource_Container_Object\|2) ONCR 3 delta (update resource stack size)]]		([[Resource_Container_Object\|2) ONCR 3 delta (update resource stack size)]]

−	([[Manufacture_Schematic_Object\|3) MSCO 6 delta (to keep track of filled slots ) ]]	+	([[Manufacture_Schematic_Object\|3) MSCO 6 delta (to keep track of filled slots ) ]], only sent when a slot is completely filled.

@@ Line 192: / Line 192: @@
 After the schematic object is updated, the experimentation gets updated clientside through sending :
-[[CraftingExperimentationResponse (00000113)]] (Experimentation answer)
+[[CraftExperimentationResponse (00000113)]] (Experimentation answer)
 =Customization=

@@ Line 130: / Line 130: @@
 The slotconfiguration gets acknowledged through a
-([[GenericIntResponse_%280000010C%29|5) Generic Int response    (slot finalization]])
+([[CraftAcknowledge (0000010C)|5) CraftAcknowledge (0000010C) (slot finalization]])
 in which we send the Controller ID of the CraftEmptySlot Message (08 01 00 00).

@@ Line 119: / Line 119: @@
 To finalize our slot update we have to send
-([[GenericIntResponse_%280000010C%29|5) Generic Int response    (slot finalization]])
+([[CraftAcknowledge (0000010C)|5)CraftAcknowledge (0000010C)  (slot finalization]])
 After sending the CraftingSlotResponse, the animation used to symbolize the filling of the slot is stopped and the client displays the updated slot configuration.