Quote:
Originally Posted by ConnorMcLeod
If you use modulo, use 32, not 31 ;)
|
Actually....I didn't realize i did that! I was wondering why you were pointing out something so minescule as 0 indexing and strange declarations.
Thanks for specifying, i wouldn't have noticed otherwise.
Quote:
Originally Posted by claudiuhks
Message SayText may be sent as MSG_ONE or MSG_ONE_UNRELIABLE.
The first parameter is a byte and it somehow means the color. If you set the byte a player index which is TERRORIST the color for ^x03 will be red. If you set the byte a player index which is CT the color for ^x03 will be blue.
The second parameter is a string and it should start with ^x01, ^x03 or ^x04. The message to be printed.
Of course there may be many combinations of bytes and strings but this is the basically. Make sure that the entity is not null.
If you want to send a blue colored message to a TERRORIST player and there are no CT players on server you have to send a TeamInfo message as MSG_ONE or MSG_ONE_UNRELIABLE to the target transfering it to CT then after sending the SayText message you have to transfer him again to TERRORIST sending a new TeamInfo message again.
PHP Code:
if( pev_valid( iEntity ) == 2 )
message_begin( MSG_ONE, get_user_msgid( "SayText" ), _, iEntity );
|
Yes, i got all that from reading Connor's colorchat.ini. But thanks.
__________________