Packet 2031 Unknowns

01/17/2011 05:19 FuriousFang#1

Hey everyone,

I'm a fan of multiple projects and servers. I want to make an NPC server so that my game servers can all access one NPC server. After some thinking, I concluded that just like the 1051 packet, there must be another packet that connects to the NPC server. Would that packet be (possibly) 2031?

So far, we know that the structure is like this:

Code:

[B]Offset          Type               Value[/B]
0                 ushort             16
2                 ushort             2031
4                 uint                 NPC ID
8                 uint                 Unknown
12               ushort             NPC Mode
14               ushort             NPC Type & Direction

Is it possible that the structure might be something like this?

Code:

[B]Offset          Type               Value[/B]
0                 ushort             16 + String Length
2                 ushort             2031
4                 uint                 NPC ID
8                 ushort             Port
10               byte                String Length
11               string              IP Address             
12               ushort             NPC Mode
14               ushort             NPC Type & Direction

Sincerely,
Fang

01/17/2011 05:24 DePredaTe#2

[Only registered and activated users can see links. Click Here To Register...]

01/17/2011 05:33 pro4never#3

Well if it's within your own servers there's no reason you must structure packets the same way...

Personally I like the idea of a central server to manage where data is going. From there you can just forward the packet to whatever project you like or use a different form of IPC. (Named pipes are awesome and something korv was using in one of his projects)

Why would you need a port/ip type information in the packet? It's a complete waste of packet size as you DON'T need it in every packet.

01/17/2011 05:44 FuriousFang#4

Quote:

Originally Posted by pro4never

Well if it's within your own servers there's no reason you must structure packets the same way...

Personally I like the idea of a central server to manage where data is going. From there you can just forward the packet to whatever project you like or use a different form of IPC. (Named pipes are awesome and something korv was using in one of his projects)

Why would you need a port/ip type information in the packet? It's a complete waste of packet size as you DON'T need it in every packet.

You're right.
Hm...
#request close

01/17/2011 05:59 nTL3fTy#5

e*pvp added a nifty little table bbcode a while ago, just so you know.

Offset	Type	Value
0	ushort	16
2	ushort	2031
4	uint	NPC ID
8	uint	Unknown
12	ushort	NPC Mode
14	ushort	NPC Type & Direction

01/17/2011 06:18 FuriousFang#6

Quote:

Originally Posted by nTL3fTy

e*pvp added a nifty little table bbcode a while ago, just so you know.

Offset Type Value
0 ushort 16
2 ushort 2031
4 uint NPC ID
8 uint Unknown
12 ushort NPC Mode
14 ushort NPC Type & Direction

Oh that's nice. How is it used? Just...

Test	Test 2
hi	haha

?

EDIT: =p oh that's awesome
Thanks ^^,

01/19/2011 01:58 BioHazarxPaul#7

Quote:

Originally Posted by nTL3fTy

e*pvp added a nifty little table bbcode a while ago, just so you know.

Offset Type Value
0 ushort 16
2 ushort 2031
4 uint NPC ID
8 uint Unknown
12 ushort NPC Mode
14 ushort NPC Type & Direction

awww i wish i would of knew about this earlier..