[dilalmon]

So the client index is from 1 to <Maximum Number of Players In the Server>, 0 being the world.
I was in an impression that these indexes don't until a round ends, but that's just seems wrong.

I was storing information in an array as follows:

player_grenadeKills[MAXPLAYERS+1]

and use the array as follows:

onPlayerDeath(Handle:event, const String:name[], bool:dontBroadcast)
{
    new attackerClientID = GetEventInt(event, "attacker");
    if ( attackerClientID > 0 && attackerClientID <= MaxClients  )
    {
          player_grenadeKills[attackerClientID]++;
    }
}

which should contain its information until a new round starts, but it seems I was doing horribly wrong since "sometimes" it isn't working properly.

So when do these indexes change?
Do they change when someone connects or disconnects?

What are more efficient methods of doing this?

[DJ Tsunami]

Do they change when someone connects or disconnects?

Yes.

What are more efficient methods of doing this?

Set player_grenadeKills[client] = 0; in OnClientPutInServer or OnClientDisconnect.

[dilalmon]

When do the client indexes change?
What happens if a client with an index of 9 disconnects? Do players with an index of 10 or bigger get shifted by 1 in their index or does that index become vacant until a new client connects and fills it out?

[thetwistedpanda]

Client indexes are only recycled when it becomes available, such as when a client disconnects. So if 9 disconnects, and three people connect, someone is going to take the 9th index and then the next two available indexes. No other indexes will be affected. Each player also possess a userid, which can be considered unique for most purposes (they're reused after ~65,000 entries). For every successful connection the userid will be incremented by one.

In your OnPlayerDeath, you're using the player's userid. To obtain their client index, you'd have to GetClientOfUserId(GetEventInt(event, "attacker")).

[dilalmon]

Great. Thanks Panda!

[pilger]

I don't know if this might be considered thread hijacking but I have a question that fits on this subject.

Are the client indexes refreshed on map change? I mean, if a player get 9th index and the map change, will the player still use the 9th index or all the indexes will be reasigned to players on the order they connect after the map change?

Thanks in advance!

[Dr. McKay]

Originally Posted by pilger I don't know if this might be considered thread hijacking but I have a question that fits on this subject. Are the client indexes refreshed on map change? I mean, if a player get 9th index and the map change, will the player still use the 9th index or all the indexes will be reasigned to players on the order they connect after the map change? Thanks in advance!

All clients are fully disconnected and reconnected on mapchange. So yes, client indexes are refreshed on mapchange.

[pilger]

Originally Posted by Dr. McKay All clients are fully disconnected and reconnected on mapchange. So yes, client indexes are refreshed on mapchange.

Wouldn't this get in the way of using the method suggested here: https://forums.alliedmods.net/showpo...97&postcount=6 ?
Since all the clients are disconnected and reconnected and recieve new indexes, relying on them between map changes doesn't look like a good idea anymore.

[Powerlord]

Originally Posted by Dr. McKay All clients are fully disconnected and reconnected on mapchange. So yes, client indexes are refreshed on mapchange.

I'd double check that if I were you, since the server clearly knows the client hasn't completed disconnected since it doesn't fire the player_disconnected event for them.

[Dr. McKay]

Originally Posted by Powerlord I'd double check that if I were you, since the server clearly knows the client hasn't completed disconnected since it doesn't fire the player_disconnected event for them.

I'm just going off this.