[spelworm]

got a question about this
do plugin creators have to make there plugin work with this ?
if yes are there already plugins wich uses this ?

[^BuGs^]

Right now this is optional for plugins to require installing this, however the goal is to make this good enough for it to go into the Sourcemod core so you don't have to worry about downloading something separate.

If this is already being used by plugin authors, they have to indicate that.

[Shaman]

You call it "Client Preferences Ext", but it's not an extension. I think you should call it "Client Preferences API" or something else like that.

[dalto]

Just wanted to say thanks for listening to my feedback.

[Shaman]

Maybe you can add an account system to this and solve all our problems. Here is my idea:

A player sets a user name and a password using "setinfo" before joining.
When a player joins this plugin reads user name and password:
If there is no account with that name, a new account is created for player.
If there is an account with this name and password is true client ets authed.
If player didn't specify a username and a password or account password is wrong, a temporary account is created for player.
After these, other plugins uses "GetClientAccountName(client, buffer...)" to get the account name and saves/reads all info using that account name.

With this method:
1- Users can use their account anywhere. (Friend's computer, cyber cafe, dynamic ip problems = solved.)
2- If a client disconnects it will not be a problem, because there is only one account with the same name.
3- Accounts and saved infos will be constant.
4- By using this system other developers can easily store kill/death ratios, levels, experience points, etc.
5- Players will be able to manage their accounts from internet. (If someone codes a PHP page for it.)
6- Admins can make their server for only registered users.

[^BuGs^]

Originally Posted by Shaman Maybe you can add an account system to this and solve all our problems. Here is my idea: A player sets a user name and a password using "setinfo" before joining. When a player joins this plugin reads user name and password: If there is no account with that name, a new account is created for player. If there is an account with this name and password is true client ets authed. If player didn't specify a username and a password or account password is wrong, a temporary account is created for player. After these, other plugins uses "GetClientAccountName(client, buffer...)" to get the account name and saves/reads all info using that account name. With this method: 1- Users can use their account anywhere. (Friend's computer, cyber cafe, dynamic ip problems = solved.) 2- If a client disconnects it will not be a problem, because there is only one account with the same name. 3- Accounts and saved infos will be constant. 4- By using this system other developers can easily store kill/death ratios, levels, experience points, etc. 5- Players will be able to manage their accounts from internet. (If someone codes a PHP page for it.) 6- Admins can make their server for only registered users.

That's like version 13.0.0.0

[^BuGs^]

Originally Posted by Shaman You call it "Client Preferences Ext", but it's not an extension. I think you should call it "Client Preferences API" or something else like that.

Changed to reflect this.

[Shaman]

Originally Posted by ^BuGs^ That's like version 13.0.0.0

Are you going to do it or shall I code that?

[^BuGs^]

Let say some of us have started it... but not client prefs.

[^BuGs^]

Just an update, I worked on all the ideas so far. I am still working on the prune check, which would be auto-checked on "Query" for a value, but there also be a force native also.