![]() Every permission in a Server Group can have the flag "negate" or the "skip" flags set, they will be explained later in this chapter. The logic behind this is to use the best or highest value as result. Since you can be part of multiple Server Groups at once, and since the same permission could be granted in multiple of these Server Groups there has to be a way to figure out the "resulting" permission of the Tier 1 layer in these cases. These server groups can contain any number of permissions, that you receive when becoming part of the group. Tier 1: Server GroupsĮvery client is part of one or more server groups. Now we will discuss each layer and it's special properties in detail. Since the channel group is in a higher tier than the server group, in the end you *can* modify your channels name (but not that of other channels where you are not channel admin). But you are also a "Channel Admin" (Tier 4) and a channel admin has b_channel_modify_name set to true. Tier 5: Channel and Client Specific PermissionsĮxample: You are in the "Guest" server group (Tier 1) which has the permission b_channel_modify_name set to false.If a permission is not granted on any of these 5 layers, it will be assumed to be of zero or false value. Each layer can overwrite permissions from the previous layer. The way a client receives his permissions is determined through a 5 layer system. How do clients get permissions? How are they assigned? Editing the permission system will be explained further down in a separate chapter called "Who can edit the permission system?" These Grant-Permissions control which permissions a client is allowed to grant or revoke, so they are the key to modifying the permission system and are thus usually reserved to administrators. In the client interface these associated needed_modify_power permission are usually displayed as additional "Grant" value of the original permission, instead of as a separate permission of its own, which is why we call these permissions Grant-Permissions as well. ![]() ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Įvery permission has an associated i_needed_modify_power_* permission, for example PERMISSION_b_client_ban_create has an associated permission called PERMISSION_i_needed_modify_power_client_ban_create. I_needed_modify_power_* or Grant-Permissions ![]() This essentially introduces a "pecking order", you can for example grant your lower tier administrators the permission to kick only guests, but your high tier administrators are able to kick any user on the server. If your power is less than the needed kick power of your target, you will not be able to go through. If you have equal or greater power, you will be able to kick this client. When you want to kick a client the permission system will compare your "kick power" with the "needed kick power" of the target of your kick. I_client_kick_power i_client_needed_kick_power You can only successfully issue the action the permission controls if your power is equal or greater than the associated needed power. They always come in pairs, one power permission and one needed power permission. These permissions are a special case of Integer Permissions. Set to "2" you can also create sub-sub-channels and so on.Īs with many permissions that have no logical limit i_channel_max_depth also has a special value of "-1" which means there is no maximum depth limitation for channels. If it is set to "1", you can also create sub-channels. ![]() So if the value is set to "0", it means you can create only top-level channels. In this case it controls how "deep" channel structures you may create. The actual name of the permission, channel_max_depth in this case tells you what this permission controls. These permissions accept integers as values.įrom the name again you can see that it is an integer permission, because it is prefixed with "i_". If it is set to true, you can change the virtual server name, if it is set to false or not set at all you can not edit the virtual server name. In this case the permission controls if you may change the virtual server name. After this prefix is the actual name of the permission, which should give you an idea what the permission is about. These permissions can only have two values, true or false.įrom the name of the permission you immediately see that it a boolean permission, since it begins with "b_". The Permission System is a very versatile and feature rich system that determines which users are allowed to do which actions.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |