Unknown packet

So, I wonder if anyone know what this packet is:

0x386f

I'm getting it lately very often on the GameServer but I can't figure out what it is, I haven't found any reference about it anywhere. It doesn't cause any problem, but I would like to know what it does.

Quote:

Originally Posted by Synx7 So, I wonder if anyone know what this packet is: 0x386f I'm getting it lately very often on the GameServer but I can't figure out what it is, I haven't found any reference about it anywhere. It doesn't cause any problem, but I would like to know what it does.

sometimes i see it in my game server too...but dont know anything about it

Quote:

notify Unhandled Game SR_MSG: 0x386f [data size: 0]

Empty sh1t?

i dont think you should worry about :)

Maybe it's backdoor for sql? :p

it has smth to do with fortress war I guess,since 0x385F is fortress notify.

Well, since there is no such packet opcode in sr_gameserver packet handler... I think, it might be just some hindoo-style stuff at sro_client or some server module intercommunication.

edit:
It's a packet sent from shard -> gs, no idea what is it meant for, but if gameserver doesen't handle it, as i said before, dosen't matter.

joymax checking on his kids.

It's not harming your gameserver in any way, nor is it helping it.
Just ignore it ^^

i saw 0x386f in my SMC when i was trying use old school files.. after i load patches.. it just spam's it no stop

I know its a old thread but i get same error on GS randomly.
When get the error the char get DC.I cannot find this opcode in the game client.Probably is created by the client 'on the fly'.I am using BR 110 server files.I know its not a big deal ,but i wanna figure out the reason of this error.
Any clue or solutions?

Regards

Solved: Change the static value 0x386f with 0x2002 in gameserver and error the will never show up.
Regards

Quote:

Originally Posted by hexcode Solved: Change the static value 0x386f with 0x2002 in gameserver and error the will never show up. Regards

Hi. Can you explain me step by step In what way is it changed?

Quote:

Originally Posted by GMCreative Hi. Can you explain me step by step In what way is it changed?

1. Make backup of SR_ShardManager.exe file
2.Open the SR_ShardManager.exe with OllyDBG
3.Right Click ->Search for constants|enter 386F
4.When find the offset click on the line and change the value from 386F to 2002

MOV WORD PTR DS:[ECX],386F <------- change 386F to 2002
to look like this:
MOV WORD PTR DS:[ECX],2002

5.Right Click ->Copy To executable,All modification (copy all) Right Click -> Save File|

Regards

Sorry to push this thread but wth you just did ^ ?

0x386f converts to:

0x3 //Packet Type
0x8 //Packet Dir
0x6F //Opcode which is PARTY_REGISTRATION_DELETED

Changing this to 0x2002 will fuck up the party ASYNC between the gs and shard, because they are waiting value back from each others, what you just did will keep the values of the party registeration in the modules, might not shows up in client but it will be still there in the memory, might just cause crash out of no where or cause memory leak since it will never get deleted and will keep a loop inside the modules.