[PRoSToTeM@]

Originally Posted by georgik57 They can easily overflow the client.

No, its ok. Overhead is very low, 1 byte for '\n'/'\r' char vs 4 bytes: 2 for message_begin, 1 for playerId and 1 for end of string (EOS).

[georgik57]

Originally Posted by PRoSToTeM@ No, its ok. Overhead is very low, 1 byte for '\n'/'\r' char vs 4 bytes: 2 for message_begin, 1 for playerId and 1 for end of string (EOS).

I'm confused. I meant I'd prefer using a new line if any worked instead of multiple chat messages.

[PRoSToTeM@]

Originally Posted by georgik57 I'm confused. I meant I'd prefer using a new line if any worked instead of multiple chat messages.

It seems there is no way to do it without multiple messages. But it isn't so principal because only text size is important.

[georgik57]

So not only the number of messages counts, but the amount of data(which is more important?) they're transmitting too?

[PRoSToTeM@]

Originally Posted by georgik57 So not only the number of messages counts, but the amount of data(which is more important?) they're transmitting too?

Yes. The network size of chat message is 4 bytes + length of the text in bytes.

[georgik57]

Didn't know about that. Thanks. What about the rest of the nonsense I said?

Originally Posted by georgik57 Are there any other special characters like ^n and ^r new-line related? Would trying them both at once make any difference? If yes, which one of them should be first? I've read the titles.txt and resource/cstrike_english.txt files and they seem to be using \n only for new lines. I know that in AMXX, \ is used to mark the continuation of a line, no matter if it is located inside a string or not, so I'm guessing that when I'm trying to send "An enemy is near you!\nAn enemy is near you!" AMXX messes with it?

[georgik57]

bumping this cause of reasons

[georgik57]

bump

[georgik57]

^
|

[georgik57]

uperino