fx resources read/write permission

[Jeromebro06]

What happened?

its not possible with load / save resorucefile to edit the fxmanifest of the fx resoruces (monitor, yarn, webpack, chat)
if anticheats try to add a shared lua to them have no perms but it is important that works to prevent game injections from cheats etc. a lot of cheats inject code directly into runtime and execute own code in client resources.

Expected result

read / write permissions for fx resources

Reproduction steps

local function installAntiInjection()
    local directive = ('shared_script "@%s/shared.lua"'):format(GetCurrentResourceName())
    
    local content = LoadResourceFile("monitor", "fxmanifest.lua")
    if not content then return print("^1[AntiInjection] fxmanifest.lua not found ^0") end
    
    if content:find(directive, 1, true) then
        return print("^3[AntiInjection] Already installed ^0")
    end
    
    SaveResourceFile("monitor", "fxmanifest.lua", directive .. "\n" .. content, -1)
    print("^2[AntiInjection] Installed successfully ^0")
end

-- error: directory not found (for all fx resources)

Importancy

Unknown

Area(s)

FXServer

Specific version(s)

FiveM 25987 and higher (newest server builds)

Additional information

No response

[Ehbw]

This isn't a bug and is rather intended functionality. A resource shouldn't be writing into other resources manifest, especially system resources like the ones you mentioned.

[Gogsi]

You can allow a resource to write to other resource's folder by adding this to your server.cfg before ensuring the resources.

add_filesystem_permission resource1 resource2

This will allow resource1 to write to resource2's folder. It cannot be done programmatically as the intention is for the server owner to give explicit permission for the resource to do that.

You can also give a Node.js resource permission to start other programs with add_unsafe_child_process_permission resource1. Maybe this can be used to bundle a script with your resource that adds the shared_scripts you want. Then you'd just have to ask the server owner to add_unsafe_child_process_permission in their server.cfg