[not a bug] Mcliloc - 0xd6 packet

Moderator: POL Developer

Locked
coltain
Grandmaster Poster
Posts: 159
Joined: Tue Mar 20, 2007 7:17 am
Location: Poland

[not a bug] Mcliloc - 0xd6 packet

Post by coltain » Sat Jan 24, 2009 1:45 am

I had this packet hooked for 097.2 and it worked fine.

I changed core to 098 and it`s not working.

Has something changed in handeling this packet??

Turley
POL Developer
Posts: 670
Joined: Sun Feb 05, 2006 4:45 am

Re: Mcliloc - 0xd6 packet

Post by Turley » Sat Jan 24, 2009 2:44 am

Nope, can you post your uopacket definition?

coltain
Grandmaster Poster
Posts: 159
Joined: Tue Mar 20, 2007 7:17 am
Location: Poland

Re: Mcliloc - 0xd6 packet

Post by coltain » Sat Jan 24, 2009 4:30 am

uopacket.cfg

Code: Select all

Packet 0xD6
{
  Length variable
  SendFunction rcliloc:HandleMegaClillocSend
  ReceiveFunction rcliloc:HandleUnknown
}
I moved the core back to 097.2 and it works perfectly.

When it`s 098 then for items there is "name" shown (only):
should be:
Katana of might
str required 25
additional attack: fire

is:
katana

for npc no message is shown, just a blank field (I can put a screen if this is unclear)

Turley
POL Developer
Posts: 670
Joined: Sun Feb 05, 2006 4:45 am

Re: Mcliloc - 0xd6 packet

Post by Turley » Sat Jan 24, 2009 4:38 am

from core-changes

Code: Select all

Added:   support for new ObjectCacheInfos introduced in 5.0.0
                 old behavior: Server sends 0xBF Sub 0x10 per object ->Client response also with 0xBF Sub 0x10 per item
                 new behavior: Server sends 0xDC per object -> Client response with 0xD6 (there can be more then one serial up to ~16)
                 intern check is 
                 if ((ssopt.ForceNewObjCachePackets) || (isUOKR) || (clientversion.major>=5))
                 since the client sends his clientversion not instantly the first few ObjCacheInfos are sent
                 the old way (thats why the new ssopt is added)
                 Note: since client 6.0.5.0 the clientversion is instantly known (new seed packet)
I would guess that you use a client >=5.0.0 and your ReceiveFunction rcliloc:HandleUnknown blocks the packet.

Pierce
Forum Regular
Posts: 420
Joined: Thu Feb 02, 2006 8:33 am

Re: Mcliloc - 0xd6 packet

Post by Pierce » Sat Jan 24, 2009 9:04 am

Client response with 0xD6 (there can be more then one serial up to ~16)
Is this also the reason for the unexpected 0xd6 messages that spam my pol.log since
over 1-2 years? I was always wondering why the client sends those serials :D

Code: Select all

Client#147: Unexpected message type d6, 11 bytes (IP:xx.xx.xx.xx, Account:yy)
0000: d6 00 0b 00 5e a6 ed 01  ec ae c0                  ....^... ........

coltain
Grandmaster Poster
Posts: 159
Joined: Tue Mar 20, 2007 7:17 am
Location: Poland

Re: Mcliloc - 0xd6 packet

Post by coltain » Sat Jan 24, 2009 10:20 am

thx for a reply

i had this spam also blocked..

MuadDib
Former Developer
Posts: 1090
Joined: Sun Feb 12, 2006 9:50 pm
Location: Cross Lanes, WV

Re: Mcliloc - 0xd6 packet

Post by MuadDib » Thu Jan 29, 2009 4:18 pm

So, a bug, or just had it blocked? :)

Locked