-- How to configure the SQL based access level system :
-- There are two tables.
-- First one is named acess_levels and it's meant to define the different possible
-- groups a GM can belong to.
-- You can see in this table six predefined GM groups. Each group has a different
-- accessLevel, and GM's access_level in the characters table should match with
-- one of these. You could define as many groups as needed and give them whatever
-- number you wanted to, from 1 to 255. Nevertheless please note the fact that
-- there is one group that will be reserved for allmighty administrators, and this
-- group is bound to the following rules:
-- * There's no need/way to restrict the commands this group is able to run, its
-- members will be able to perform ANY admin_command.
-- * One number must be reserved for this group, and by default it is set to 127.
-- * In order to change this default group number or its name/title colors,
-- you should look at the Character.properties configuration file and
-- change the value of MasterAccessLevel, MasterNameColor and MasterTitleColor
-- * You should better not use this group as a part of any childs hierarchy.
-- In our predefined set of examples, access_level=1 is for the highest admin,
-- and access_level=3 is for Event GMs.
-- The rest of the access_levels table columns are expected to be self explanatory.
-- And there is a second table named admin_command_access_rights and in this table
-- administrators should add every command they wanted GMs to use.
-- We left just one query here to show how commands should be added to the table:
-- INSERT IGNORE INTO `admin_command_access_rights` VALUES ('admin_admin','6');
-- If an administrator wanted to grant his GMs from group 4 the usage of the //para
-- command, he should just copy our example and replace values like this:
-- INSERT IGNORE INTO `admin_command_access_rights` VALUES ('admin_para','4');
-- So on, for each command there should be a record in this table. And it would be
-- advisable to use one query per command to avoid messups
Notorious wrote:@Janiii: I'd like to ask if one can use this levelsytem to give characters that are special for some reason, an accesslevel of their own, where IsGM is not set, and thereby use this to have these characters have a different colour, but in all other ways they should be as normal user.
Open up admin_command_access_rights in Navicat.
Set all things that the lowest GM should be able to do to his corresponding level, 5 for instance.
If you have a higher type of GM, set all things he should be able to do to his level, 4 for instance.
If you want even more levels of GM, set them too.
Finally, set all things only a Admin should be able to do, to level 1.
Open up access_levels with Navicat.
Make sure Admin has all other levels set as childAccess.
Make sure the highest level of GM has all levels BELOW his level set as childaccess.
And so on.
Check that isGm is set to 1 on the levels with GM status.
Set the accesslevel on the character using the GM commands.
Or open up table characters with Navicat and find column accesslevel and set it to the correct level on the character you want to be GM.
@Janiii: I'd like to ask if one can use this levelsytem to give characters that are special for some reason, an accesslevel of their own, where IsGM is not set, and thereby use this to have these characters have a different colour, but in all other ways they should be as normal user.
There.. i installed Navi-bloody-cat just for this... lets hope its gonna work!
Users browsing this forum: Baidu [Spider] and 6 guests