Entity Spawn packet 5017

[Kiyono]

So I checked different sources and it seems that not one public source unless I missed it has the complete Entity Spawn packet for 5017.
Taking bits and pieces from sources I got the following offsets and really random different packet sizes.

UID = 4
overlaymesh = 8 //all 8? wtf?
Mesh = 8
Avatar = 8
Model = 8
Status = 12
GuildID = 20
GuildPosition = 23
Garment = 24
Helmet = 28
Armor = 32
RHand = 36
LHand = 40
HP = 48
MobLevel = 50
X = 52
Y = 54
Hair = 56
Direction = 58
Action = 59
Reborn = 60
Level = 62
Namesomething? = 80 //value 255
NameLength = 81
Name = 82

So does anyone know what I'm missing or if this is even correct up till now?

[_DreadNought_]

Those are very easy to figure out since theres visual changes when they are correct. Trial and error.

[nTL3fTy]

Here's what I have, from an old project of mine:

offset	datatype	description
0	ushort[2]	header
4	uint	id
8	uint	lookface
12	ulong	effect
20	uint	guild id/rank
24	uint	garment itemtype
28	uint	helmet itemtype
32	uint	armor itemtype
36	uint	right weapon itemtype
40	uint	left weapon itemtype
44	uint	unknown
48	ushort	monster life
50	ushort	monster level
52	ushort	position x
54	ushort	position y
56	ushort	hair
58	byte	direction
59	byte	action
60	byte	rebirth
61	byte	unknown
62	ushort	level
64	byte	unknown
65	byte	nobility ranktype
...	...	...
80	stringlist	strings

[Kiyono]

Thanks, for the answers, though, it's weird that TQ just randomly skipped some values for no real reason.

[pro4never]

Originally Posted by nTL3fTy

Here's what I have, from an old project of mine:

That source makes me cry every time I look at it.

I remember trying to look through it to see how you handled something (I thin it was to do with magic attack types) and it took me probably 20 minutes to track through all the necessary methods lol.

Everything is labeled in tq'isms.

</offtopic>

@Kiyono: Yahhh there's lots of packets with un-used offsets. I can't think of a good example right now but I do remember a few people mentioning there are a few where the client doesn't even process the offset so it's not like we just haven't logged what it does for subtypes or w/e.

[BaussHacker]

Originally Posted by pro4never

That source makes me cry every time I look at it.

I remember trying to look through it to see how you handled something (I thin it was to do with magic attack types) and it took me probably 20 minutes to track through all the necessary methods lol.

That's how I have it with your sources, but we all do things different.

[Kiyono]

Originally Posted by pro4never

@Kiyono: Yahhh there's lots of packets with un-used offsets. I can't think of a good example right now but I do remember a few people mentioning there are a few where the client doesn't even process the offset so it's not like we just haven't logged what it does for subtypes or w/e.

I wasn't implying that you guys were too lazy to log them, just saying that TQ is weird for having gaps in their packets.

[CptSky]

Mine look a little bit different. But, it is based on what I saw with packet sniffing. For the two values used by the monster, it is useless to set them for a player, but you can.

private struct MsgInfo      
{
     public MsgHeader Header;
     public Int32 UniqId;
     public Int32 Look;
     public Int64 Flags;
     public Int16 SynUID;
     public Byte Unknow1;
     public Byte SynRank;
     public Int32 GarmentId;
     public Int32 HeadId;
     public Int32 ArmorId;
     public Int32 RightHandId;
     public Int32 LeftHandId;
     public Int32 Unknow2;
     public UInt16 CurHP; //Used for Monster, but can be used for Player
     public Int16 Level; //Used for Monster, but can be used for Player
     public UInt16 X;
     public UInt16 Y;
     public Int16 Hair;
     public Byte Direction;
     public Byte Action;
     public Byte Metempsychosis;
     public Int16 Level;
     public Int32 Unknow3;
     public Int32 NobilityRank;
     public Int32 UniqId;
     public Int32 NobilityPosition;
     public Byte StringCount;
     public TQString[] Strings;
};