5165 - Client is auto-closing.. weird?

09/29/2011 02:40 xBlackPlagu3x#1
Alright so I've search the forums for an answer and I've yet to come across one. I run my project and then I attempt a login. You'd expect *Boom, ding! Thank you for logging in. One moment please.* but instead all I get is *HAAA FAWK YOU!!! H4X H4X H4X!!! Close.* It's really weird and I'm not sure what the problem is. Obviously I can't google this sort of problem as it's not a general problem. So what could it be? My *guess* is that it has something to do with the EntityUID and ItemUID. There are no errors while debugging the server while I log in. Nada.

<Edit> Oh and I've tested this with two different clients. One I've been using since the launch of FoxxCo (2010) and the other is an official 5127 client patched up to 5165. Neither work.

<Edit 2> Fixed, for those of you with Impulse's 5165 source... double-check that the variable "Servername" is set to whatever is in your database. Also you cannot use 127.0.0.1 you MUST EITHER use your 192.168.x.x address, your Hamachi address (Recommended by Fang) or your external IP.
09/29/2011 14:48 BaussHacker#2
Invalid packets = crash. LOTF has some few of them, assuming you're using that.
09/29/2011 15:10 xBlackPlagu3x#3
Quote:
Originally Posted by BaussHacker View Post
Invalid packets = crash. LOTF has some few of them, assuming you're using that.
Actually I'm using Impulse's 5165 o:
03/11/2013 02:03 agathom#4
Darn couldnt figure out till now.. I downgraded impulse 5375 to 5165 client crashes.. im using external.. I am sure its working because if i put wrong password it will say wrong password. it only crashes on right password..
03/11/2013 03:09 Spirited#5
Quote:
Originally Posted by agathom View Post
Darn couldnt figure out till now.. I downgraded impulse 5375 to 5165 client crashes.. im using external.. I am sure its working because if i put wrong password it will say wrong password. it only crashes on right password..
Try using my thread to debug it. There are a lot of common problems people have with updating and downgrading sources. It's most likely your packets or a configuration error. Either way, here's the thread link. It should help you out: [Only registered and activated users can see links. Click Here To Register...]
03/11/2013 04:56 agathom#6
Thanks you so much fang! Just because of wrong buffer offset its fixed now..
03/11/2013 13:27 _DreadNought_#7
Make sure EntityUID is > One million