[ConnorMcLeod]

From #17, if you use get_players to retrieve a player list, use is_user_connected is just useless.

For other, it's obviously :

if( is_user_connected( id ) )
execute_code_on_id( id )


other way :

if( !is_user_connected( id ) )
return

execute_code_on_id( id )




Writing this i just realized that you may have not understood what the "!" stands for, basically it's the contruary of what you put after, so !0 == 1 and !1 == 0.

[Owyn]

so if i write
if( !is_user_connected( id ) )
{
execute_code_on_id( id )
}

it won't make any sense and won't execute code?

[Exolent[jNr]]

What you put means you want to execute code on a player that isn't connected.

[Owyn]

so how do i check users for MSG_ALL ?

for this stock:

stock Create_DeathMsg_CS(killer_id,victim_id,headshot,weaponname[]){

    message_begin(MSG_ALL,gmsgDeathMsg)
    write_byte(killer_id)
    write_byte(victim_id)
    write_byte(headshot)
    write_string(weaponname)
    message_end()
}

help me make a check pls ^^

[Exolent[jNr]]

A check for what?

[AntiBots]

MSG_All to MSG_BROADCAST

[Owyn]

Originally Posted by Exolent[jNr] A check for what?

is_user_connected

[Exolent[jNr]]

When using MSG_ALL and MSG_BROADCAST, it automatically sends to the players that are connected. There is no check to make.

[Owyn]

yhm... i get this error few times a day or less and i checked all plugins with MSG_ONE etc to have is_user_connected check but still happens )= what else can cause this?

[Owyn]

Originally Posted by taheri6 What types of messages do I need to do that with? PHP Code: #define MSG_BROADCAST        0    // unreliable to all #define MSG_ONE            1    // reliable to one (msg_entity) #define MSG_ALL            2    // reliable to all #define MSG_INIT                     3    // write to the init string #define MSG_PVS            4    // Ents in PVS of org #define MSG_PAS            5    // Ents in PAS of org #define MSG_PVS_R        6    // Reliable to PVS #define MSG_PAS_R        7    // Reliable to PAS #define MSG_ONE_UNRELIABLE    8    // Send to one client, but don't put in reliable stream, put in unreliable datagram (could be dropped) #define MSG_SPEC        9    // Sends to all spectator proxies  Would it only be needed arround MSG_ONE type messages?

you said you could use MSG_ONE_UNRELIABLE instead of MSG_ONE, but will be any difference in msg effect or not? in description it also said "could be dropped" what? O_o