YACL Installed but Not Detected: Find Where the Loader Is Looking
Not detected means the loader never read your file, or read a different one. In order: prove which instance folder the starting profile uses, confirm the JAR sits directly inside its mods folder with its original name, remove any second YACL copy, and confirm the profile actually starts with its mod loader.

Start from the loader's point of view
The loader knows one folder: the mods folder of the instance being started, read once at launch. Everything about this fault is a gap between that folder and the place your file actually is. Your job is to close the gap by evidence, not by reinstalling. Reinstalling into the same wrong place reproduces the fault perfectly and adds a duplicate to the confusion.
Open two windows side by side: the folder your file manager shows for the download, and the folder the profile opens from its own settings. If they are not the same path, you have found the fault already, and the rest of this guide is confirmation.
The position checks
- The JAR is directly inside mods, not inside a subfolder. Extracted pack zips often nest the real mods folder one level down.
- The file is the JAR itself, not a folder of extracted contents and not a .zip the browser saved instead.
- The filename ends in .jar with no additions. A browser's (1) suffix after a repeat download is harmless to the loader but signals you may have several copies in play.
- The file size is complete, roughly a megabyte for current builds. A tiny file is an interrupted download wearing the right name.
Fix position problems by moving the untouched file, not by downloading again. Then restart the profile; the loader only rescans at launch, so a running game will keep reporting the old state no matter how correct the folder becomes.
The wrong-instance checks
If the position is right and detection still fails, suspect the instance. Launch the profile, close it, and check which instance's latest.log just changed. Then search that instance's log for yet_another_config_lib. No entry means that instance's loader never saw the file, whatever the file manager suggests. An entry with a different version means the loader read another copy, which points at the duplicate check below.
Players who import packs meet a special case: the import created a fresh instance while the old one kept the familiar name. Your file went into the remembered instance; the game starts the imported one. The log timestamp separates them in under a minute.
Duplicates and disabled files
Search the live mods folder for every file whose name contains yet_another_config_lib. Two copies give the loader a duplicate identity to reject or a choice to make silently, and both outcomes present as not detected from the player's side. Keep the copy that matches your requirement, move the other out of the instance entirely, and restart.
Some launchers can disable a mod in place, which keeps the file visible while the loader skips it. If your launcher lists mods with toggles, check YACL's state there. A file can also be neutralised by a renamed extension, such as .jar.disabled, which some tools append. The loader ignores those, correctly, until the name is restored.
The browser download that never finished
Browsers occasionally leave a partial file with a complete-looking name, especially on interrupted connections. The loader then meets a file it cannot read and reports the mod as absent. Compare the file's size with the release record: current YACL builds run a little over a megabyte. A file far from that is not the file, whatever its name claims. Delete it, download again through the finder and watch the download complete before moving the file.
The same check applies to files that arrived inside pack zips. An extraction that ran out of space can leave a truncated JAR among healthy ones. Size is a crude instrument, but for spotting a file that is mostly missing, crude is enough.
Antivirus and quarantine surprises
Security software occasionally quarantines a downloaded JAR on suspicion, silently removing it from the folder you placed it in. If a file you installed is simply gone, with no duplicate and no wrong folder in play, check the security tool's quarantine or history before downloading a third copy. The publisher's files come from the Modrinth content network, and the checksum routine in the QA-minded guides lets you prove a file's integrity when you need to make that case.
Detection and the case of the renamed profile
Renaming a profile in the launcher changes its label, not its folder, but players often pair a rename with a tidy-up that moves folders too. If detection broke right after a reorganisation, assume the folder moved and prove the live one with the log test rather than trusting the path you remember. Memory of paths decays faster than any other fact in a modded setup, because the launcher hides paths during normal play.
Once the live folder is proven, write its path into the profile notes in full. Future installs then start from the note, and this entire fault class closes for that profile.
A note on cloud-backed instance folders
Instances stored in cloud-synced folders can show a file as present while its content is still a placeholder waiting to download. The loader meets the placeholder and reports the mod missing or unreadable. If your instance lives in such a folder, set the mods folder to be kept on the device, or wait for sync to settle and confirm the file's real size before launching. The size check exposes a placeholder instantly.
The archive that was never extracted
Download tools and browsers occasionally leave the library as a compressed archive, or extract it into a folder of loose files, depending on settings and on what the user clicked. The loader wants one JAR. If your mods folder shows a folder named like the library, or a zip beside the mods, you have found the fault. Download the file again from the finder, watch where the browser puts it, and move the JAR itself, the single file ending in .jar, into the mods folder. Delete the folder or archive from mods so the next audit reads cleanly.
Operating systems that hide file extensions make this harder to see, because the JAR and the archive can share an icon and a name. Turn extensions on in your file manager before a debugging session; the .jar at the end of the name is the whole diagnosis.
Case, characters and odd filenames
A file renamed by a download manager, with a suffix like (1) or a trailing space before the extension, can slip past a strict scan or confuse your own audits. Restore the exact published filename by downloading fresh rather than renaming by hand, because the published name is the one your records, the finder and any checksum all agree on. Filenames are identifiers in this system, and identifiers earn their keep by being boring and exact.
When the loader's own list disagrees with the folder
Rarely, a launcher's content list shows the library enabled while the running game behaves as if it were absent. Trust the game and its log over the list: the list is the launcher's intention, the log is the loader's act. Rebuilding the instance's records, by removing the entry and installing again through the same route you used originally, reconciles them. If the disagreement survives a clean reinstall, the instance itself is suspect, and cloning the profile to a fresh instance, then moving only the mods and config across, is the decisive experiment.
Detection is the loader's testimony
When folder and loader disagree, the loader is the witness that counts, because it alone performed the scan. Your job in this fault is not to convince the loader but to find what its scan actually saw: the folder it opened, the files it registered, the duplicates it choked on. The log records all three. Read the testimony before changing the evidence, and the fix usually names itself.
Close with the folder, not the feeling
End a detection fix by listing the mods folder one final time and reading the library's filename aloud against the finder's selection. It feels ceremonial because it is: the ceremony marks the moment the record, the folder and the loader were all seen to agree. Most returns of this fault trace to a fix that stopped one step earlier, at the game merely starting.
Confirm the profile starts its loader
A vanilla profile loads no mods at all, and a machine with both a vanilla entry and a modded entry for the same pack makes this mistake easy. Read the profile's version details and confirm the loader is part of what starts. On Fabric, the title screen's Mod Menu entry is a quick witness: no Mod Menu button on a setup that installed it means the loader profile is not the one running.
Once the loader profile is confirmed and the file is provably in its folder, detection follows. If it still does not, download a fresh copy through the finder to rule out a corrupt file, install it as the only YACL in the folder and restart. That is the end of the local causes; anything beyond it belongs in the mod's or loader's issue tracker with your log attached.


