Difference between revisions of "INSO"

From SWGANH Wiki
Jump to: navigation, search
(Description)
 
(4 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
=DataFlow=
 
=DataFlow=
  
 +
{| align="center"
 +
|-
 +
|width="600"|
 
{{PacketFlow|Resource Container Object|
 
{{PacketFlow|Resource Container Object|
 
<graphviz>
 
<graphviz>
Line 22: Line 25:
 
</graphviz>
 
</graphviz>
 
}}
 
}}
 +
|}
  
 
=Description=
 
=Description=
The manufacturing schematic object gets used for all schematics in game.
+
The INSO Object creates the temporary building fence where houses / factories are build.
  
The creation process begins with an Object Init Packet and an Object Link packet, the main data is sent through an [[MSCO03|'''MSCO03''']] and an [[MSCO06|'''MSCO06''']] packet and the creation process is ended through a [[MSCO08|'''MSCO08''']], [[MSCO09|'''MSCO09''']], an object finish and a posture update Packet.
+
The creation process begins with a [[SceneCreateObjectByCrc|'''SceneCreateObjectByCrc''']], then the main data is sent through an [[INSO03|'''INSO03''']] and an [[INSO06|'''INSO06''']] packet, an [[UpdatePvpStatusMessage|'''UpdatePvpStatusMessage''']]. The Object initialization will be completed through sending the [[SceneEndBaselines|'''SceneEndBaselines''']]
  
There are still some parts of the [[MSCO03|'''MSCO03''']] and [[MSCO06|'''MSCO06''']] which are not figured out yet, though as far as I can see they are hopefully not that important.
+
The updatePvpStatusMessage might have had an historical use when it was still planned to do the actual construction work on site through miners or crafters, so that a construction work of the other faction could be destroyed, but else there is no apparent need for this packet as it does just fine without it.
  
Please note: that like with everything these packets can be sent stand alone in an 00 09 or in the pack as an 00 19. To make this a bit clearer I seperated them as single packets. I did not include the headers though (00 09 wx yz and crc at the end) because thats getting redundant.
+
Initialization of the Object starts through sending the [[SceneCreateObjectByCrc|'''SceneCreateObjectByCrc''']] the crc sent is the crc of the shared_construction_installation_base.iff 2073410C.
 
+
The object init Packet contains the ID of the newly created schematic and the crc of the item to be created.
+
 
+
Initialization of the Object starts through sending the [[SceneCreateObjectByCrc|'''SceneCreateObjectByCrc''']] the crc sent is the crc of the object we want to create.
+
 
+
The [[UpdateContainmentMessage|'''UpdateContainmentMessage''']] packet links the schematic to the craft tool we use to create it.
+
 
+
 
+
[[MSCO03|'''MSCO03''']]
+
 
+
[[MSCO06|'''MSCO06''']]
+
 
+
[[MSCO08|'''MSCO08''']]
+
 
+
[[MSCO09|'''MSCO09''']]
+
 
+
the Object initialization will be will be completed through sending the [[SceneEndBaselines|'''SceneEndBaselines''']]
+

Latest revision as of 08:16, 9 June 2007

OSNI Packet Type QuickNav
INSO03 - INSO06 - INSO07

DataFlow

 Client <-> Server Sequence: Resource Container Object

{{{2}}}

Description

The INSO Object creates the temporary building fence where houses / factories are build.

The creation process begins with a SceneCreateObjectByCrc, then the main data is sent through an INSO03 and an INSO06 packet, an UpdatePvpStatusMessage. The Object initialization will be completed through sending the SceneEndBaselines

The updatePvpStatusMessage might have had an historical use when it was still planned to do the actual construction work on site through miners or crafters, so that a construction work of the other faction could be destroyed, but else there is no apparent need for this packet as it does just fine without it.

Initialization of the Object starts through sending the SceneCreateObjectByCrc the crc sent is the crc of the shared_construction_installation_base.iff 2073410C.