Open Asset Conflict Finder · All tool guides

Before you start

A resources folder or ZIP containing the packs that run together.

Step by step

  1. Load all relevant resources in one scan.
  2. Review collisions for stream asset names and vehicle spawn codes.
  3. Identify which resource should own each name. Remove unintended duplicate packs or deliberately rename a resource’s assets and references.
  4. Rescan the revised set and test the affected assets.

What you get

A name-collision report. High-detail vehicle twins within one resource are expected and are not ordinary duplicate conflicts.

Troubleshooting

If a reported collision seems harmless, inspect whether both resources actually run together. Renaming only a file can break metadata references; use an appropriate renaming tool for vehicle packs.

Next steps

Read Installing and checking results before replacing a working resource. For access, failed jobs or download problems, see Troubleshooting tools.