Configuration
Conflict Resolver works out of the box with zero configuration. The two settings below are optional, they only change *how* fixes are applied and *how smart* the tool can be about map merges.
Both go in your server.cfg.
🗂️ Duplicate Handling, conflictresolver:distribute
Controls what happens to the copies that lose a duplicate-file conflict.
setr conflictresolver:distribute writeAll # default| Value | Behaviour |
|---|---|
writeAll (default) | Every duplicate copy is overwritten with the winning file's contents. No matter which resource the game loads first, it always gets the same correct result. Nothing is deleted. |
keepOne | The extra copies are deleted, leaving a single file. Cleanest stream folder, but the redundant files are gone. |
Both modes are backed up first and fully reversible from the Backups panel. If you're not sure, leave it on the default.
[!NOTE] When you manually pick a copy to keep from the dashboard, the others are always removed, your explicit choice is respected exactly.
🧭 Stock Map Baseline, conflictresolver:vanilla_dir
Optional, and most servers never need it.
When two map packs edit the same area, the tool normally can't tell whether a missing prop was deleted on purpose by one pack or simply never added by the other, so it stops and asks you to pick a copy by hand.
Give it a folder containing the stock, unmodified versions of those map files and it gains a reference point. With that, it can tell additions from deletions and safely merge overlapping edits that would otherwise need manual review.
set conflictresolver:vanilla_dir "C:/gta-stock-maps"You can also simply create a folder named vanilla inside the kartik-conflictresolver resource and drop the files there, it's picked up automatically, no convar needed.
What you gain when it's configured:
- More conflicts resolve automatically instead of landing in your lap.
- The dashboard can recommend keeping the edited copy over an untouched stock copy, which is exactly what prevents the classic "my custom collision disappeared" bug.
Without it: nothing breaks. The tool simply falls back to keeping one copy and asking you which.
🧰 Maintenance Commands
Two clean-up passes run as commands rather than from the dashboard, manifestaudit for files a resource includes but never switches on, and ymtdeclarations for clothing that never appears in the menu. Both can preview before changing anything. See Console Commands.
🔐 Access Permissions
Access to the dashboard and the in-world editor is controlled by an Ace permission, see Installation.
add_ace group.admin command.conflicts allow🗄️ Database Backups
The automated database backup system (schedule, local vs Google Drive storage, restore) has its own full setup guide, see Database Backup Setup.