Proxy not parsing Reconnect packet through update method?

Hey, I've been fooling around with a proxy, I've implemented a few fun features, but when I attempt to send a reconnect packet through a command, for example my /recon command, the reconnect packet isn't being parsed through the update method, meaning it never gets sent to the client. If anyone here has managed to overcome this problem, it'd be great if you could tell me how you fixed it.
Thanks!

Hey i have a gold mine, i wanna keep it for myself but can you tell me how to extract it ?

I'm going to assume that you're mocking me.
I'm not asking how to use my gold mine, my gold mine can connect to realms and everything just fine, I'm just asking for advice on a problem I've been trying to fix for a few weeks.

PM'd you with my skype, thanks alot.

Nearly all packet id's were changed in 17.2, reconnect is 15. I don't know if that is your problem, though.

No, I've had this problem from the beginning of my proxy
Though that is rather interesting, do you think Kabam will change the packet ids every build?

EDIT: Also, how did you find that packet id? I couldn't find it in yogda, I'm going to assume its somewhere in the bytecode..

I do not think they will be changing the ids every build, since they have only changed them a couple times before. The packet ids can be found with rabcdasm and notepad++'s "find in files" feature, just search for "HELLO" and you will find the file that contains them.

Okay, thanks, I figured as much.
Thats probably why my proxy was telling me that it was blocking a squarehit when I loaded up the nexus haha
Any chance you could reply to this so I can PM you?

Yes, HELLO changed to what SQUAREHIT used to be (51). Also, in order to get your command to work you need to know that PLAYERTEXT is 80. I have not found any actual changes to any of the packet contents.

Yeah, I found that. I have a few commands already working, but my problem still seems to be the same..

Check to make sure you are sending all of the correct RECONNECT packet data to the client:

The packet is structured in this order:
string name
string host
int port
int gameId
int keyTime
boolean isFromArena
byte[] key

edit: the byte[] key length is a short