View Single Post
  #5  
Old 07-10-2010, 07:43 AM
KLS
Administrator
 
Join Date: Sep 2006
Posts: 1,348
Default

Naturally I couldn't sleep so I was fiddling with this instead.

0x2121 appears to be OP_TargetBuffs from my collects. With a 17 byte buff entry and larger header than SoD. I find it used in the following cases from collects: Buff fades, Buff added, AA action, MouseTarget. So it looks like on live they expanded it to pretty much everything buff related.

Here's an example packet(I have quite a few more if needed):
Code:
[OPCode: 0x2121] OP_Unknown [Server->Client] [Size: 216]
4a 13 00 00 //entity id
70 17 00 00 //???
01 //seems to always be 0x01
0c //count
00 00 //???

00 //???
00 00 //???
83 26 00 00 //spell id
55 00 00 00 //tics
00 00 00 00 //???
00 //This is a name, I assume it has something to do with making buffs appear on the client
01 //probably buffslot

00 
00 00
96 4a 00 00 
f8 04 00 00 
00 00 00 00 
00 
02 

00 
00 00 
c1 4b 00 00 
55 00 00 00 
00 00 00 00 
00 
03 

00 
00 00 
e2 4b 00 00 
51 01 00 00 
00 00 00 00 
00 
04

00 
00 00 
e5 4b 00 00 
51 01 00 00 
00 00 00 00 
00
05 

00 
00 00 
1f 20 00 00 
44 00 00 00 
00 00 00 00
00 
06 

00 
00 00 
e2 46 00 00 
2d 01 00 00 
00 00 00 00 
00 
07 

00 
00 00 
e3 4a 00 00 
9d 01 00 00 
00 00 00 00 
00 
08 

00 
00 00 
93 47 00 00 
f4 06 00 00 
00 00 00 00 
00 
0a 

00 
00 00 
bf 48 00 00
e5 01 00 00
00 00 00 00 
00 
0b 

00 
00 00 
6f 05 00 00
99 01 00 00 
00 00 00 00 
00 
0c 

00 
00 00 
38 0d 00 00 
c8 05 00 00 
00 00 00 00 
00 
00
If correct it would mean the opcodes in our list are a bit swapped around; though not completely pushed up like normal cause the dz ones are after and only one of the dz opcodes didn't match it's SoD alignment. This may get tricksy.
Reply With Quote