YetAnotherConfigLib

Duplicate YACL Files in the Mods Folder: Why Two Copies Break Startup

One instance needs exactly one YACL file. Two copies share the same mod identity, so the loader may stop with a duplicate error or quietly load a version you did not choose. Find every file whose name contains yet_another_config_lib, keep the one that matches your game version, loader and required range, and move the rest out of the instance.

Two identical voxel JARs with a cross marking the duplicate problem

How duplicates get in

Duplicates arrive by ordinary habits. A player downloads a new build and copies it in without removing the old one. A launcher install lands beside a manual install. A pack update adds its tested build to a folder where a personal copy already sits. The real loader message in the Zoomify case listed two versions present at once, 3.5.0 and 3.6.6, which is how common this is: it appears inside other people's error reports as background noise.

Renaming does not defuse a duplicate. Calling the old file old.jar keeps it a YACL file as far as the loader is concerned, because the identity lives inside the file. Even a name like yet_another_config_lib_v3-3.5.0.jar.bak escapes only if the loader ignores that extension in your setup, which is not a thing to rely on.

What the loader does with two copies

Loaders differ in response. Some stop and report the duplicate mod identity, which is honest and easy to act on. Others load one copy and ignore the other, and which copy wins can depend on file order rather than on your intention. That second behaviour is the dangerous one: the game starts, the version in the log is the older file, and every fix you apply to the newer file appears to do nothing.

This is why several troubleshooting guides on this site begin by asking what the log says loaded. The log reports the copy in force. When it disagrees with the copy you installed, duplicates or a wrong folder are the explanation almost every time.

Clear them out properly

  1. Close the game.
  2. List every file in the mods folder whose name contains yet_another_config_lib, including inside any subfolder a pack created.
  3. Decide the keeper by the usual three facts: game version in the name, loader suffix and the library number against your mod's range.
  4. Move the other copies to a backup folder outside the instance, named with the date. Do not delete them until the game has started cleanly once.
  5. Restart the profile and confirm from the mods list or latest.log that the loaded version is the keeper.

Moving rather than deleting keeps the operation reversible. After a clean start and a working settings screen, the backups can go. Until then they are your undo.

Duplicates that hide in subfolders

Some launchers and pack formats place disabled or optional mods in subfolders of the instance, and a few setups scan deeper than the top level. Search the whole instance for the library's filename pattern, not only the mods folder's top level. A copy inside a folder named after a pack version can wake up after an update changes what gets scanned. The rule travels with the search: one instance, one YACL file, anywhere the loader can reach.

Cloud sync folders create a stranger variant: conflicted copies with names like the filename plus your computer's name in brackets. The loader may read those as separate mods too. If your instance lives inside a synced folder, expect these and clear them on sight.

The launcher list versus the folder

A launcher's content list can show one YACL entry while the folder holds two files, because the launcher tracks what it installed and the stray arrived by hand. When the two disagree, believe the folder for what the loader will read, and believe the list for what the launcher will try to manage. Reconcile them by removing the stray file, then let the launcher's copy be the single survivor, or remove both and install once by your chosen route.

Why launchers sometimes create the duplicate

A launcher that resolves dependencies can add its own copy of a library beside one you installed by hand, because its records do not know the manual file is the same mod. The reverse happens when a manual install lands in an instance the launcher manages. Neither tool misbehaves; they simply keep separate books. The folder is where their stories collide, which is why the folder, read directly, is the referee in every duplicate dispute.

After any session where both routes touched one instance, spend ten seconds listing the folder's library files. That glance is cheaper than the debugging session a duplicate schedules for you later.

Duplicates across a pack and its add-ons

Add-on packs and optional mod bundles can each carry the library. Installing two bundles that overlap produces the duplicate even though each bundle was consistent alone. When you stack bundles, treat the second install as a merge: compare its file list with the folder first, and skip the files already present at satisfying versions. The merge mindset applies to any shared library, and YACL is simply the one whose name you now know how to read.

The duplicate that only appears in the log

A duplicate does not always show as two obvious files. One copy can sit in the mods folder while another hides inside a subfolder a pack export created, or inside the folder of a mod that bundles its dependencies. The loader scans deeper than the top level in some setups and reports the mod twice, while your folder listing looks innocent. When the log insists on a duplicate your eyes cannot find, search the whole instance folder for the library's filename pattern and let the file manager enumerate every copy with its full path. The hidden one's path explains its origin, and origin decides whether deletion is safe.

Bundled copies inside another mod's folder deserve care: if a mod genuinely embeds the library, its own documentation says so, and the mods list shows the library once. A stray bundled copy from an export is far more common than true embedding.

Preventing duplicates during pack exports

Exports are the duplicate factory: a pack export gathers the library, your manual additions may include it again, and an import that merges rather than replaces doubles it. When importing an export into an existing instance, choose replace over merge for the mods folder, or audit the folder immediately after a merge with the filename search. The audit takes a minute and is the only step between a merge and a clean set, because no tool in the chain considers deduplication its job. It is yours, briefly, once per import.

One copy, then verify like it matters

After removing a duplicate, the verification is not complete when the game starts. Open the mods list and read the library's version, then open the dependent mod's screen. A duplicate's damage is subtle: the loader may have been running the older of the two copies for weeks, and settings or behaviours you attributed to the mod belonged to that older build. The first session on the single correct copy is the real test, and anything that behaves slightly differently is the duplicate's ghost leaving, not a new fault arriving.

The folder read as a habit

Every duplicate story on this page ends the same way: somebody finally listed the folder and counted. Make that listing a habit rather than a last resort. Before the first launch after any install session, sort the mods folder by name and read the library lines. Two copies announce themselves in that view instantly, while they are still a thirty-second deletion instead of a structured mystery with a log file and a forum thread.

The habit generalises to every library you will ever install. Duplicates are not a YACL problem; they are a folder problem, and folders reward readers.

Duplicates love company

Finding one duplicate is a prompt to look for others. The same session that doubled the library often doubled a companion file or left an older copy of the dependent mod beside its replacement. Read the whole folder once with fresh eyes after the library is single again. The second find, if there is one, is far cheaper now than it would be as next week's unrelated-looking fault, because you already know the story that produced it.

Note the pair you removed and the one you kept, with versions, in the profile record. A duplicate removed without a note invites the same pair back at the next export or reinstall, because nothing in the setup remembers that the two files were ever enemies. The note is the folder's memory of the fight, and it takes one line to write.

Prevent the sequel

Adopt a replace, never add, habit for libraries: every library update is a swap with the old file leaving the folder in the same motion. When you use a launcher mod browser after a manual install, or the reverse, check the folder once afterwards, because each route is blind to the other's files. And when you test builds, test them one at a time, removing each candidate before the next enters. A folder holding three candidates is a riddle you set for yourself.