Protected Resources

Many paid assets ship escrow-protected, their files are encrypted and signed by Cfx.re so they can't be opened or edited. Conflict Resolver fully respects that protection, and this page explains what you'll see when a conflict involves one.

🏷️ The Lock BadgeCopy Anchor Link

Any copy of a file that lives inside a protected resource is shown with a 🔒 escrow badge in the file list. That badge means one of two things:

• The file can't be read: the tool can't look inside it, so it can't compare it, merge it, or tell you what changed.
• The file can't be written: changing or deleting a file inside a protected resource breaks the resource's signature, so the tool refuses to touch it.

The tool will never pick a protected copy as the default keeper, and it will never silently modify one.

🚧 When Every Other Copy Is ProtectedCopy Anchor Link

Sometimes the only copies you could remove are the protected ones. The tool calls this out plainly, because in that case there is nothing safe to delete, but there is still a clean fix:

Fix it with start order instead. FiveM streams files by name, and the copy from the resource that starts last is the one that actually loads. Move the resource you want to win below the others in your server.cfg.

ensure some-protected-map
ensure the-map-i-want-to-win   # starts last → this copy loads

The dashboard tells you exactly which resource to place after which, so you can copy the order straight into your config.

🚫 Merging Into a Protected ResourceCopy Anchor Link

If you pick a protected resource as the copy to keep, merging is disabled with a short explanation. Merged layouts and collisions have to be written to disk, and that isn't possible inside a signed resource.

What to do: choose a non-protected resource (usually your own custom map resource) as the keeper instead, then merge into that.

✅ What Still WorksCopy Anchor Link

Protection only limits editing. Everything else still applies:

• Protected copies are still detected, listed, and counted as conflicts.
• You still get told which resources clash and what the consequence is in-game.
• Every non-protected copy in the same conflict can still be cleaned, merged, or kept as normal.
• The in-world editor can still hide, move, and override protected props at runtime, those changes are saved as overrides and never touch the original files.

🧭 Quick Rules of ThumbCopy Anchor Link

• Two protected packs clashing? Decide by start order, or disable one of them.
• One protected, one open? Keep the open one as the keeper so merges stay possible.
• Unsure why a fix button is greyed out? Hover it, the reason is always shown.