Learn how to configure permissions on your new RSGCore Framework!
Ace Permissions?
Aces are the built-in permissions system provided by CFX. They allow for creating new nodes which have aces attached to them. This permission system consists of aces & principals. Essentially think of a tree with branches. We have our ace that we create and then each branch would be our principal which inherits the permissions of our ace
txAdmin should automatically set the server owner as the highest permission level
Learn how to update your docs locally and deploy them to the public.
FiveM ID
Rockstar license (what rsgcore uses)
Discord ID
To get a RedM or Red Dead 2 license you can look up the player on your txAdmin web panel
If they are currently connected to the server, you will get all available identifiers
Players
section as shown belowrsgcore.god and group.admin share the same permissions you can use either one.
While you have permissions you can set users permissions either using commands or the admin menu
Setting permissions using the command
While in the server type in the command /addpermission [id] [addpermissions]
It will look something like this /addpermission 1 god
Setting permissions through the admin menu
In rsg-core/config.lua find RSGConfig.Server.Permissions = {'god', 'admin', 'mod'}
Here you can add more groups, lets say I wanted to make one for police I would have RSGConfig.Server.Permissions = {'god', 'admin', 'mod', 'law'}
Making a command for only leo can access would look like
So now when you add this command using the qbcore function it will automatically generate an ace called rsgcore.law with an ace of command.cuff! Now you can add a principal of a player with add_principal identifier.license:xxxx rsgcore.law
and now that command will be restricted to only those with that permission as well as remove the chat suggestion for anyone without this permission! Imagine if you used this when setting a players job or when a player clocked in/out to dynamically remove the permission. This also completely eliminates the need to ever check job permissions on a command like this because the command itself will already be restricted
Learn how to configure permissions on your new RSGCore Framework!
Ace Permissions?
Aces are the built-in permissions system provided by CFX. They allow for creating new nodes which have aces attached to them. This permission system consists of aces & principals. Essentially think of a tree with branches. We have our ace that we create and then each branch would be our principal which inherits the permissions of our ace
txAdmin should automatically set the server owner as the highest permission level
Learn how to update your docs locally and deploy them to the public.
FiveM ID
Rockstar license (what rsgcore uses)
Discord ID
To get a RedM or Red Dead 2 license you can look up the player on your txAdmin web panel
If they are currently connected to the server, you will get all available identifiers
Players
section as shown belowrsgcore.god and group.admin share the same permissions you can use either one.
While you have permissions you can set users permissions either using commands or the admin menu
Setting permissions using the command
While in the server type in the command /addpermission [id] [addpermissions]
It will look something like this /addpermission 1 god
Setting permissions through the admin menu
In rsg-core/config.lua find RSGConfig.Server.Permissions = {'god', 'admin', 'mod'}
Here you can add more groups, lets say I wanted to make one for police I would have RSGConfig.Server.Permissions = {'god', 'admin', 'mod', 'law'}
Making a command for only leo can access would look like
So now when you add this command using the qbcore function it will automatically generate an ace called rsgcore.law with an ace of command.cuff! Now you can add a principal of a player with add_principal identifier.license:xxxx rsgcore.law
and now that command will be restricted to only those with that permission as well as remove the chat suggestion for anyone without this permission! Imagine if you used this when setting a players job or when a player clocked in/out to dynamically remove the permission. This also completely eliminates the need to ever check job permissions on a command like this because the command itself will already be restricted