Installation

1. Download the AssetCopy Anchor Link

After purchase, navigate to Cfx.re Keymaster and download the kartik-conflictresolver resource folder.

Extract the resource folder and place it inside your server's resources/ directory (e.g., resources/[kartik]/kartik-conflictresolver).

2. Configure Permissions (Ace Permissions)Copy Anchor Link

Because this tool can modify resource files, delete files, and persist map changes, it is highly restricted. Access is managed using FiveM's native Ace Permissions system.

To allow admins or developers to run the scanner, add the following rule to your server.cfg:

# Allow group.admin to run conflict scanner and map editor commands
add_ace group.admin command.conflicts allow

If you want to grant access to a specific player without adding them to group.admin, you can link their license identifier directly:

# Add a developer to the admin group
add_principal identifier.license:abc123xyz456 group.admin

[!WARNING] Ensure these permissions are configured correctly. Players without the command.conflicts permission will be blocked from opening the scanner dashboard or using the map editor commands.

3. Start the ResourceCopy Anchor Link

Add the following line to your server.cfg file:

ensure kartik-conflictresolver

Restart your server or start the resource dynamically via the server console:

refresh
start kartik-conflictresolver

Once started successfully, you should see the following log in your server console indicating the resource root has been successfully resolved:

[conflictresolver] resources root: C:/FiveM/txData/Qbox_CD3D7D.base/resources
[conflictresolver] loaded X persistent map override(s)

4. Filesystem Write Permission (required to apply fixes)Copy Anchor Link

Recent FXServer artifacts sandbox what a resource is allowed to write. By default a resource may only write inside its own folder. Conflict Resolver fixes conflicts by editing files that belong to other resources (carcols.meta, carvariations.meta, streamed clothing files), so without an explicit grant every fix is blocked.

How to tell this is happeningCopy Anchor Link

Scanning works normally and the conflict is listed, but pressing a fix button appears to do nothing, or reports that there was nothing to fix. The real cause only appears in the server console:

Filesystem write permission check from 'kartik-conflictresolver' for permission fs.write
  on resource '.../resources/[vehicles]/City-Vehicles/data/toreador2/carcols.meta' - write not allowed
[conflictresolver] failed writing [vehicles]/City-Vehicles/data/toreador2/carcols.meta:
  Access to this API has been restricted. Use --allow-fs-write to manage permissions.

The fix, one line (recommended)Copy Anchor Link

add_unsafe_worker_permission kartik-conflictresolver
add_unsafe_child_process_permission kartik-conflictresolver

This covers every resource in a single line. Put it above your ensure lines and restart the server, permissions are read at boot only, so restarting just the resource is not enough.

It is also what allows the scheduled database backup to run mysqldump / mysql.

3. Restart the server. Fixes will now apply.

[!IMPORTANT] Permissions are read before resources start, so the exec line must sit above your ensure lines and the server must be restarted, not just the resource. A scan that turns up a resource you haven't granted yet will add it to the file; re-exec (restart) to pick it up.

[!NOTE] There is no wildcard, FXServer requires one grant per target resource, which is why the file is generated. Servers on artifacts older than ~25770 have no filesystem sandbox and need none of this.

6. Optional SettingsCopy Anchor Link

Conflict Resolver runs with zero configuration, but a couple of optional server.cfg settings change how fixes are applied and how much it can resolve automatically, see Configuration.