ACE Permissions

[DementedDude]

How would I go about adding permissions to a specific resource only? Or is that possible?

[Syntasu]

Basic Aces & Principals overview/guide

Basics: Aces & Principals Aces and principals are the default “permissions” system built into fxserver. It’s very easy to use, as long as you know the basics and you just start trying out some stuff. It’s also very easy to use this from within resources. Just use ExecuteCommand() to add/remove aces or principals, and use IsPlayerAceAllowed() to check if a player is allowed access to an ace (either directly or via inherited permissions). Principals Let’s start by taking a look at what a Princi…

Should cover everything you need.

[DementedDude]

Yeah I’ve read it many times, didn’t help the tiny brain.

[Syntasu]

You can always ask in the topic, Big chance Vespura can answer your questions.

[Vespura]

Not really sure what you’re trying to do here?

Do you want to give your resource permissions to do something? or do you want to add “permissions”/aces to “principals” (players) so they can use something in your resource?

[DementedDude]

Basically add perms to a resource. Only given steam ID’s can use that resource.

[Vespura]

@DementedDude

Basically add perms to a resource. Only given steam ID’s can use that resource.

what does the resource do exactly?
Is it a menu? do you use commands? do you interact with stuff in the world for it to work? Very basic example would be like this:

in server.cfg

add_ace identifier.steam:steamidhere "the.permission.name.you.want" allow

then in a server script:

if IsPlayerAceAllowed(playerSource, "the.permission.name.you.want") then
    -- do your code here
end

if you want this in a client script, use something like this at the top of your client file.

local allowedToUse = false
Citizen.CreateThread(function()
    TriggerServerEvent("<resourceName>.getIsAllowed")
end)

RegisterNetEvent("<resourceName>.returnIsAllowed")
AddEventHandler("<resourceName>.returnIsAllowed", function(isAllowed)
    allowedToUse = isAllowed
end)

-- In your resource, check "allowedToUse" whenever you want to "do" something that needs permissions, for example
if allowedToUse then
    -- do your cool code here
end

Server script:

RegisterServerEvent("<resourceName>.getIsAllowed")
AddEventHandler("<resourceName>.getIsAllowed", function(source)
    if IsPlayerAceAllowed(source, "the.permission.name.you.want") then
        TriggerClientEvent("<resourceName>.returnIsAllowed", source, true)
    else
        TriggerClientEvent("<resourceName>.returnIsAllowed", source, false)
    end
end)

[DementedDude]

Thank you @Vespura I was looking for the client side perm. Nailed it!

[Fiat_Panda]

Sorry, I need help. I would like to limit the / eup command, only to those in game is set “agent” and “policeman”, how do I do? The guide says:

to restrict this, replace, false with, true in the RegisterCommand in eup_ui.lua and give command.eup add_ace

I changed “false” to “true”, but I did not quite understand what he meant by “give command.eup add_ace”. I need help, please, thank you!

[Vespura]

@Fiat_Panda

Sorry, I need help. I would like to limit the / eup command, only to those in game is set “agent” and “policeman”, how do I do?

That’s not using ace permissions.

@Fiat_Panda

to restrict this, replace, false with, true in the RegisterCommand in eup_ui.lua and give command.eup add_ace

I changed “false” to “true”, but I did not quite understand what he meant by “give command.eup add_ace”. I need help, please, thank you!

Add this somewhere in your server.cfg.

add_ace identifier.steam:<steam64 hex id> command.eup allow

[Fiat_Panda]

Thanks so much! Instead of adding the steam ID hex, is there a way to add the group in the job category?

[Vespura]

@Fiat_Panda

Thanks so much! Instead of adding the steam ID hex, is there a way to add the group in the job category?

if you’re talking about principal groups, then yes, but if you’re talking about some resource/framework specific group then no.

[Fiat_Panda]

No, I’m talking about general groups. I refer to those who are in game “agent” and “captain”

[Vespura]

@Fiat_Panda

No, I’m talking about general groups. I refer to those who are in game “agent” and “captain”

Then that’s a no. You can’t do that with aces/principals permissions.

[Fiat_Panda]

I see. So there is no way, right?

[Vespura]

Not with aces, you’ll have to seek support for whatever framework you’re using.

[Fiat_Panda]

Ok @Vespura, thanks for your help

[fluorine]

@Vespura

Then that’s a no. You can’t do that with aces/principals permissions.

‘Frameworks’ should be adding principals for this, anyway, in an ideal case.

[PolarBear]

@Vespura

@DementedDude

Basically add perms to a resource. Only given steam ID’s can use that resource.

what does the resource do exactly?
Is it a menu? do you use commands? do you interact with stuff in the world for it to work? Very basic example would be like this:

in server.cfg

add_ace identifier.steam:steamidhere "the.permission.name.you.want" allow

then in a server script:

if IsPlayerAceAllowed(playerSource, "the.permission.name.you.want") then
    -- do your code here
end

if you want this in a client script, use something like this at the top of your client file.

local allowedToUse = false
Citizen.CreateThread(function()
    TriggerServerEvent("<resourceName>.getIsAllowed")
end)

RegisterNetEvent("<resourceName>.returnIsAllowed")
AddEventHandler("<resourceName>.returnIsAllowed", function(isAllowed)
    allowedToUse = isAllowed
end)

-- In your resource, check "allowedToUse" whenever you want to "do" something that needs permissions, for example
if allowedToUse then
    -- do your cool code here
end

Server script:

RegisterServerEvent("<resourceName>.getIsAllowed")
AddEventHandler("<resourceName>.getIsAllowed", function(source)
    if IsPlayerAceAllowed(source, "the.permission.name.you.want") then
        TriggerClientEvent("<resourceName>.returnIsAllowed", source, true)
    else
        TriggerClientEvent("<resourceName>.returnIsAllowed", source, false)
    end
end)

This does not work for me. Cant get the perms to work on client script.

[Vespura]

Permissions don’t work client side, triggering events is the only way to sync permissions between server and client side. Like explained in that post that you quoted.