Difference between revisions of "TANO07"
(New page: __NOTOC__ {|align="center" |- ||{{TANOArchitectureNAV}} |- |} {| border="0" width="90%" cellpadding=6 |- |valign=top| ===BaseLine Struct=== ---- <pre> </pre> ===Deltas Struct=== ---- ...) |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{PageHeader|Baseline|TANO07}} | |
| − | + | ||
{|align="center" | {|align="center" | ||
|- | |- | ||
| Line 6: | Line 5: | ||
|- | |- | ||
|} | |} | ||
| + | <br> | ||
{| border="0" width="90%" cellpadding=6 | {| border="0" width="90%" cellpadding=6 | ||
| Line 13: | Line 13: | ||
---- | ---- | ||
<pre> | <pre> | ||
| − | + | SHORT: OpperandCount | |
| + | LONG: ObjectID | ||
| + | LONG: ObjectID | ||
</pre> | </pre> | ||
| Line 19: | Line 21: | ||
---- | ---- | ||
<pre> | <pre> | ||
| + | SHORT: UpdateCount | ||
| + | SHORT: UpdateType | ||
| + | { | ||
| + | 00: | ||
| + | LONG: ObjectID | ||
| + | 01: | ||
| + | LONG: ObjectID | ||
| + | } | ||
</pre> | </pre> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|valign=top| | |valign=top| | ||
| Line 31: | Line 36: | ||
---- | ---- | ||
| − | + | OpperandCount = 2 | |
| − | - | + | |
| + | ObjectID: | ||
| + | TANO7 is used for the crafting tool in a crafting session. | ||
| + | It contains 2 objects, | ||
| + | one: the manufacturing schematic of the session. | ||
| + | two: the prototype (tano) object of the session. | ||
| + | These 2 objects are updated as you progress through the crafting session. | ||
| + | I could not determine which is which because the server only sets these both to 0. | ||
| + | That would require ASM reversing which I don't care to do, and also because: | ||
| + | All this is set automatically by LINKING (update containment) the MSCO and TANO to the crafting tool. | ||
| + | So setting this is pointless. | ||
| + | The only captures that set this set both values to 0 in a baseline. | ||
| + | However in Pre-CU these should not be set | ||
| + | otherwise it will parse this as a MSC07 and the client will crash. | ||
| + | |||
| + | IF: a /synchronizeduilisten is sent WITH the crafting tool ID as the target (not the MSCO like | ||
| + | it so far has)then the server I THINK can safely send the TANO7 with NULL for both objectIDs | ||
| + | resetting (aka "synchronizing") it. | ||
| + | ---- | ||
===Tags=== | ===Tags=== | ||
| Line 39: | Line 62: | ||
{| align="center" | {| align="center" | ||
|- | |- | ||
| − | ||{{ | + | ||{{100%}} |
|- | |- | ||
| − | |||
|} | |} | ||
| + | ===Sample Packet=== | ||
---- | ---- | ||
| + | <pre> | ||
| + | |||
| + | </pre> | ||
Latest revision as of 09:59, 18 March 2009
Baseline - TANO07
SWGANH Wiki is a repository of Star Wars Galaxies Developer information. This site is only meant to be used by SWGANH Developer team.
|
BaseLine StructSHORT: OpperandCount LONG: ObjectID LONG: ObjectID Deltas Struct
SHORT: UpdateCount
SHORT: UpdateType
{
00:
LONG: ObjectID
01:
LONG: ObjectID
}
|
Variable DescriptionsOpperandCount = 2 ObjectID: TANO7 is used for the crafting tool in a crafting session. It contains 2 objects, one: the manufacturing schematic of the session. two: the prototype (tano) object of the session. These 2 objects are updated as you progress through the crafting session. I could not determine which is which because the server only sets these both to 0. That would require ASM reversing which I don't care to do, and also because: All this is set automatically by LINKING (update containment) the MSCO and TANO to the crafting tool. So setting this is pointless. The only captures that set this set both values to 0 in a baseline. However in Pre-CU these should not be set otherwise it will parse this as a MSC07 and the client will crash. IF: a /synchronizeduilisten is sent WITH the crafting tool ID as the target (not the MSCO like it so far has)then the server I THINK can safely send the TANO7 with NULL for both objectIDs resetting (aka "synchronizing") it. Tags
Sample Packet |
