[gromit190]

I am a little confused about the term "user id".


The GetClientUserId function is described like this:

"Retrieves a client's user id, which is an index incremented for every client that joins the server."

https://sm.alliedmods.net/new-api/cl...etClientUserId


If that is really the case. Then what is the "client index" that you get in the OnClientConnected forward? How is the client index different from the user id?

https://sm.alliedmods.net/new-api/cl...lientConnected


I was hoping that the "user id" is actually a unique user id per steam user... (which would mean that the GetClientUserId description is actually wrong)

[Bacardi]

"UserID" is like ticket for each player who join in server.
That ticket last as long as player not disconnect or re-connect.

With "userID" you find correct person (client index) or you get 0 = person have leave from server.

"userids" start from 1 and grows by one. There are max limit, when number get reset back 1, I don't remember that limit... 65000 ?

"userids" are like temporary ID's for players. If you really want search person with right SteamID then you look players steam id.

*edit

- Client index is array index.
- You have a array start from 0 to MaxClients (max is 64, depends game and mode).
- Client index 0 = is server (or error)
- Valid client index start from 1 to MaxClients.

[gromit190]

Okay. Whats the difference between client index and user id?

When the first client joins the server. His user id will be 1. And his client index will also be 1 (the first client)?
Then what is the point of the user id?

[gromit190]

Originally Posted by Bacardi "UserID" is like ticket for each player who join in server. That ticket last as long as player not disconnect or re-connect. With "userID" you find correct person (client index) or you get 0 = person have leave from server. "userids" start from 1 and grows by one. There are max limit, when number get reset back 1, I don't remember that limit... 65000 ? "userids" are like temporary ID's for players. If you really want search person with right SteamID then you look players steam id. *edit - Client index is array index. - You have a array start from 0 to MaxClients (max is 64, depends game and mode). - Client index 0 = is server (or error) - Valid client index start from 1 to MaxClients.

Okay then I think I understood it. Thanks!

[Psyk0tik]

The difference is that client indexes only go up to 64 while user IDs can go up to 65,535.

Let’s say player A joined first and became client index 1 and was assigned user ID 1. Then more players join to fill up client indexes 2-64 and were assigned with user IDs 2-64. Now let’s say player A left and player B joined to take his place. Player B will now be client index 1 but his user ID will be 65 because there were 64 other players that joined before him (including player A).

We prefer user IDs over client indexes when tracking each player currently on the server because there are more slots to fill up and thus providing more unique numbers to assign to each player that joins. Meanwhile, client indexes only go up to 64 so it becomes unreliable when you have players going in and out of the server and “replacing” each other.

[Bacardi]

Here some code... snip

-saves players userid when plugin start, only.
- with sm_test command you can check stored userids when players leave and come back.

Spoiler

PHP Code:

// global array
int store_userids[MAXPLAYERS];


public void OnPluginStart()
{

    for(int client_index = 1; client_index <= MaxClients; client_index++)
    {
        // Check first, is client in game. If not, skip, go next index.
        if(!IsClientInGame(client_index)) continue;


        // Print player userid
        PrintToServer("Client index %i have userID %i", client_index, GetClientUserId(client_index));
        
        
        // for test, save userid in array when plugin start.
        store_userids[client_index] = GetClientUserId(client_index);

        
    }

    // create sm_test command
    RegConsoleCmd("sm_test", test);
}



public Action test(int client, int args)
{
    int client_index;

    for(int x = 0; x < sizeof(store_userids); x++)
    {
        // When array have userid stored greater than 0 value
        if(store_userids[x] > 0)
        {
            // Try get client index by given userid
            client_index = GetClientOfUserId(store_userids[x]);
            
            // When userid doesn't return client index 0 (error)
            if(client_index > 0)
            {
                PrintToServer("- UserID %i found client index %i", store_userids[x], client_index);
            }
            else
            {
                PrintToServer("- There is no client by this UserID %i", store_userids[x]);
            }
        }



    }

    return Plugin_Handled;
} 


[Ilusion9]

userid = unique id for a player while the server is online. we use these in timers, request frames etc, because if a player disconnects and another one joins, the player who joins can have the clientid of the disconnected one.
clientid = the client entity id. with this we perform actions on the player (slap, kick etc).

its the same thing with entities ids and entities references.

[Austin]

I was wondering the same thing.

Great question and great answers that explain the reasons for both of them.
Thanks....

[Austin]

Some follow up questions….
I saw this from a different post
“SourceMod functions (like GetClientName) take player indexes, which is the same as their entity id”

1) They use the term “player index” is this just clientid?
2) I know entities are a different concept but it looks like
For players, their clientid will = their entityid?

[Bacardi]

You use mostly player/client/entity index in SourcePawn functions.

In game events, it carry player userid, you convert that to player index.

playerid, clientid, entityid, player index, client index, entity index... there are many "names" for that.

Players are entities, both have indexs. It's a like array index.

What different between players and other entities is, game try utilize first 64 index for clients.
- It depends game engine and server max players slots. MaxClients give you right players size.

Game engine have max entity limit (edicts) https://developer.valvesoftware.com/wiki/Entity_limit