Chat Problem [Serious Problem]

04/06/2011 07:39 Spirited42#1
Hey everyone... I've been trying to fix this for months (on and off)... and I can't figure this shit out... It's so frustrating. I really want it working but I just don't get it.

I've been having problems with my chat from patch 4267 through 4350. I'm using the 4282 client (same problem in the 4267 client).

I'll type something in and it'll add crap to it afterwords like this:
[Only registered and activated users can see links. Click Here To Register...]

Please, I'm desperate for help.

Sincerely,
Spirited
04/06/2011 09:00 Nullable#2
I'd suggest finalizing the message with a null terminator, maybe that will help.
04/06/2011 10:12 Korvacs#3
How are you doing your chat? Unless theres a very specific reason for it you should just be relaying the original chat packet to other people, also the chat that is displayed by your client, that you type, is displayed by the client, not by the server, so if your getting that on the same client as your sending it on its an issue with your client/your computer.
04/06/2011 10:19 Spirited42#4
Quote:
Originally Posted by Korvacs View Post
How are you doing your chat? Unless theres a very specific reason for it you should just be relaying the original chat packet to other people, also the chat that is displayed by your client, that you type, is displayed by the client, not by the server, so if your getting that on the same client as your sending it on its an issue with your client/your computer.
The one I'm testing the chat on is Hybrid's source on clients 4267, 4274, and 4289 (at the moment). I've used CoFuture at these clients, and compared the chat systems. They work at 5017... but then they don't work on lower patches. I've messed around with the packet so many times... I have no idea what's wrong.

Quote:
Originally Posted by Nullable View Post
I'd suggest finalizing the message with a null terminator, maybe that will help.
I'm recoding my source tomorrow so I'll try the null terminator then.
04/06/2011 10:49 Korvacs#5
Have you tried it with multiple clients, sending chat on talk and seeing what the other clients receive? And if possible different clients and computers?
04/06/2011 11:00 Spirited42#6
Quote:
Originally Posted by Korvacs View Post
Have you tried it with multiple clients, sending chat on talk and seeing what the other clients receive? And if possible different clients and computers?
I think so... I can't remember now- it's been such a long time since I tried...
I'll get back to you on that when I recode it all tomorrow. Working on the game server tomorrow.
As far as I can remember tho... it shows up on both.
04/06/2011 11:07 Korvacs#7
If it happens on all of them then its a client issue, the client is sending that data to the server, which means that the string length is likely to be correct for the data that its sending, and is including the rubbish within the string, you need a new client.
04/06/2011 11:43 Spirited42#8
Quote:
Originally Posted by Korvacs View Post
If it happens on all of them then its a client issue, the client is sending that data to the server, which means that the string length is likely to be correct for the data that its sending, and is including the rubbish within the string, you need a new client.
Hmm... I guess we'll see tomorrow.
The only official one I have is 4212... I'd love an official client somewhere between 4282 and 4340. =\

EDIT: I found an official 4274 on some arabic forum. I'm so excited... too bad I have to study tomorrow morning. Night.
04/07/2011 00:25 Spirited42#9
This is with the official (4274) client:

[Only registered and activated users can see links. Click Here To Register...]

[Only registered and activated users can see links. Click Here To Register...]
04/07/2011 01:12 Korvacs#10
Must be a bug with the official client then i guess, the server is able to send a string packet fine without any problems, so yeah client issue.
04/07/2011 02:14 Spirited42#11
Quote:
Originally Posted by Korvacs View Post
Must be a bug with the official client then i guess, the server is able to send a string packet fine without any problems, so yeah client issue.
=\ That's disappointing. I guess I'll have to edit my own client.
Thanks Korvacs.
04/11/2011 14:41 gomila#12
Quote:
Originally Posted by Spirited View Post
The one I'm testing the chat on is Hybrid's source on clients 4267, 4274, and 4289 (at the moment). I've used CoFuture at these clients, and compared the [Only registered and activated users can see links. Click Here To Register...] systems. They work at 5017... but then they don't work on lower patches. I've messed around with the packet so many times... I have no idea what's wrong.



I'm recoding my source tomorrow so I'll try the null terminator then.
could you be more specific please, because I have a similar problem and I don't know how to solve it :)
04/11/2011 21:51 Spirited42#13
Quote:
Originally Posted by gomila View Post
could you be more specific please, because I have a similar problem and I don't know how to solve it :)
Read past the first post. :facepalm: *Extreme frustration*
04/11/2011 22:23 12tails#14
hmmm i coded a 1.0 a some time ago (fully working source... maybe 3 or 4 days)

but... if possible post the packet structure &/or the chat handle... also be sure you're not sending the TQ seal...