| All settings that you can apply to a client on the server side are stored in reference to the clients unique ID. This way, when the client reconnects to the server maybe using a new IP, the server can still recoginize the user by the unique ID, and apply these settings. One of the more important settings you can apply to clients is of course to grant or revoke certain permissions to them. Clients joining for the first time will automatically become a member of the default Server Permissions Group that is configured via the server settings. Also clients that join a channel they have not visited before will automatically be inserted into the Default Channel Permission Group (also configured via the server settings). Usually you will also be some kind of administrator group that allows you to configure the server in the way you like it when you are a member of this group. The default group layout contains a "Server Admin" group for this purpose. How does the first client receive elevated permission when there is no other client with elevated permissions yet that could grant these permissions? The solution for this problem is through tokens. A token gives a client administrator privileges when an administrator does not yet exist. It is a long (random looking) string. The new account receives this client token in the welcome email. Once it is used on the client's server, the user is granted administrative powers. Another way a token is used is if the server's administrator wants to assign three users into a clan managment permission group. If these users are not currently connected to the server and are not stored in the administrator's buddy list, they can't be directly added into these groups. The administrator generates three tokens that each promote the client to use it into the server managment group. These are sent these tokens to each user so they can promote their rights. |
MammothGames - Gaming for Everyone
