[question] Packet 0x3b, picking drop. Info about number

[Xorg]

Hello,
I want to have the item structure with info about amount etc.

When I pick up drop and I've already own this kind of item (all countable items) the packet 3b is sent to client when sent pick packet to server.

Those packets looks like:
------- size hd ????? ev hh num
Recv - 07003b c378 5f 02 da
Recv - 07003b b17c 5f 02 db
Recv - 07003b 6572 5f 02 dc
Recv - 07003b bb71 5f 02 dd
Recv - 07003b 1e6f 5f 02 de
Recv - 07003b 9976 5f 02 df
Recv - 07003b ae7a 5f 02 e0
Recv - 07003b 1174 5f 02 e1

I've dropped 8 times 1 geon. After picking those 3 dropped geons above packets are sent.
I dont know how to get correct amount of the items.

The last byte is between 0-255. It always contain a part of number of the items you have after picking. After hittin FF it starts from 0.

The byte before the last is always 0x02.

ev is the value almost static, but if you make relog it changes

???? - every pick its different value.


How can I know what item is picked? (ID) How many of item is picked? (Amount)

[meak1]

if (buf[2] == 0x09)
ItemDropped=*(DWORD*)&buf[3];
is what you dropped only medicine

if (buf[2] == 0x08)
ItemDropped=*(DWORD*)&buf[3];
is what you dropped all items

[bloodx]

Originally Posted by meak1

if (buf[2] == 0x09)
ItemDropped=*(DWORD*)&buf[3];
is what you dropped only medicine

if (buf[2] == 0x08)
ItemDropped=*(DWORD*)&buf[3];
is what you dropped all items

what da .....

@Xorg your Packets looks really crappy lol..

[katze123]

yep... your packet analyzing .. lol
0x%02x should be used to display all bytes... would look much better

[Xorg]

I am using %02x. I dont need to have 0x before of any packet.

The 0x3b packet is useless I see.

Complete itemlist made with 0x04, 0x07, 0x08,0x09 packets.

Any of you got actual item index and its names?
I want to show name of items I ma actually having, beacuse only item index does not say me much.
Its propably inititem and message-e.dat if I am right?

[ChocoDuo]

0x3b isnt a pickup item packet, but simply tells the client to despawn a drop (by ID, which you are told in pkt 0x36, spawn drop)

when you pick up an item youll recv 0x3b followed by 0x09 (alter existing item) or 0x07 (new item)

<that is if my memory serves me well...>

and yes, for names, find the item ID in inititem.dat, part of its info is the name index. this index is in message.dat as an 'itemname' entry (the -e version no longer exists)

[Xorg]

Yeah, your memory serves you well .

... but any of you got new inititem.dat and message.dat, from actual client?

[ChocoDuo]

These are from last update (I think, been a long week already...)

[Xorg]

Thank you

[ChocoDuo]

np, gl with it