We have to sleep like everyone else, be patient for help.
Anyway, I told you how to do this before.
Go to 'Common.h' and add your custom security level in "enum AccountTypes". Since SEC_CONSOLE has to be changed to 5, I believe in your world database -> command table, you have to change the values in the permission column to 5 considering you moved SEC_CONSOLE to 5.
This can be easily done by doing:
UPDATE `command` SET permission='5' WHERE permission='4'
Inside of the world database -> command table, you can add your custom 'VIP' or whatever custom commands you have for your new security group. If you want your custom group to have a player sec level, you can add them in rbac_linked_permissions.
SEC_PLAYER = 0,
SEC_MODERATOR = 1,
SEC_GAMEMASTER = 2,
SEC_ADMINISTRATOR = 3,
SEC_CUSTOM = 4,
SEC_CONSOLE = 5, // must be always last in list, accounts must have less security level always also
In rbac_permissions, I have a custom permission '191':
I linked Player Sec Level to my custom permission. This gives me the player commands:
INSERT INTO rbac_permissions VALUES ('191', 'Role: Sec Level Custom');
Inside of "rbac_default_permissions" I added my custom group, secId 5 (custom):
INSERT INTO rbac_linked_permissions VALUES ('191', '195');
Lastly, I added it to my account (2) in "rbac_account_permissions":
INSERT INTO rbac_default_permissions VALUES ('5', '191');
To test to see if my custom group worked, I linked GameMaster Sec Level to my custom permission '191'. Sure enough, my test worked.
INSERT INTO rbac_account_permissions VALUES ('2', '191', '1', '-1');
Just some information I found out about RBAC. If your commands are working fine on any security group and you restart the server then come back online to find that your commands don't work anymore, that's RBAC, not you or your custom permissions.