How to Verify YACL Is Loaded and Working
A YACL install is verified, not assumed. Three checks, in order: the game reaches the title screen without a loader error, the library appears in the mods list or the instance log, and the dependent mod's settings screen opens and keeps a change. Pass all three and the chain from file to feature is proven.

Check one: a clean start
Start the profile you installed into. Reaching the title screen means the loader accepted every file in the mods folder, including YACL, and found no unsatisfied requirement. If the game stops with an error page instead, the verification ends here and the troubleshooting begins: copy the message, note the first mod and version it names, and work from that text.
A clean start alone does not prove YACL loaded. A profile can start perfectly with YACL absent when no installed mod requires it at launch, or with the file sitting in a subfolder the loader skipped. That is why the next two checks exist.
Check two: the mods list or the log
On Fabric, Mod Menu shows the loaded mods from the title screen. Open it and search for YetAnotherConfigLib; the entry shows the version that loaded, which should match the filename you installed. On loaders without an in-game list, use the log. Open the instance's logs folder, then latest.log, and search for yet_another_config_lib. The loader records each mod it loads, and the entry confirms both presence and version.
Read the version in the log against your notes. A mismatch here explains many confusing sessions: the log reports the file the loader actually read, which may be an older copy in a folder you forgot, not the one you downloaded today. If the log names a different version, you have a profile or duplicate problem, and the find-the-profile guide is the next stop.
Check three: the settings screen test
- Open the mod you installed YACL for and find its settings screen, through Mod Menu's config button, the mod's own menu or its key binding.
- Change one obvious, harmless option, such as a display toggle.
- Close the screen completely, reopen it and confirm the option kept your change.
- If the mod offers it, restart the game and check once more. A change that survives a restart proves the settings are being written to the config file as well.
This is the check that matters to you as a player, because the settings screen is the entire reason the library is on your machine. A library that loads but cannot open its consumer's screen has not finished the job, and the settings category covers what to do in that case.
Reading partial results
| Result | Likely meaning | Next step |
|---|---|---|
| Title screen, no YACL in list or log | File is in the wrong folder or a subfolder | Re-run the profile identity routine |
| YACL listed, wrong version | An older copy is being read, or a duplicate exists | Check the mods folder for a second YACL file |
| YACL listed, settings screen missing | The dependent mod's entry point differs, or the mod failed to initialise its screen | Try the mod's own menu or key binding; read the log for the mod's name |
| Settings open, changes do not stick | Config file is not being written | Work through the settings-not-saving guide |
Work down the table in order. Each row assumes the checks above it passed, which keeps you from chasing a settings problem when the real fault is a folder.
Reading the log like a professional
The latest.log is a diary the loader writes every launch, oldest entries first. Mod loading happens near the start. Search for the library's name and read the lines around any hit: the loader records the mod's name, version and the file it came from. A warning mentioning YACL deserves a read even when the game starts; warnings about a version range being wider than tested, or a config failing to parse, are tomorrow's bug reports arriving early.
Keep the log from a known-good launch. When a later launch fails, comparing the two logs around the library's name shows what changed: a version that moved, a file that vanished or a new mod entering the conversation. Support threads run on exactly this evidence, and having it ready shortens any report you file.
The settings screen as the final word
Everything before the settings test proves the library is present. The settings test proves it is useful. That distinction matters because a library can load while its consumer fails to build a screen, for reasons inside the consumer mod. If your checks pass and a screen still misbehaves, your evidence now points at the mod, and the mod's tracker is the right venue, with your log and versions attached. You have done the library's part of the diagnosis completely.
Verification for pack players
In a pack, verify against the pack's records rather than the newest available. The mods list should show the YACL version the pack ships, and a different version there means the set has drifted, through an update, a manual change or a partial install. Drift is worth catching during verification rather than mid-session, because the pack author's support will start from the shipped set and so should you.
If you changed the library deliberately, your verification target is the build you chose and the reason you chose it. Write both into the profile notes while the launch is fresh, so the drift reads as a decision when you meet it again.
What a warning in the log is worth
Not every log line about the library is a failure. Loaders note when a mod's declared range is wider than the author's tested range, or when a config value was clamped to a valid one. Those lines are the system narrating its judgement calls. Read them once, decide whether they touch anything you use, and move on. The discipline is to read, not to panic: a log with no warnings at all is rare in a large mod set, and chasing every line is its own way to lose an evening.
Verification when the game will not reach the title screen
Some failures stop the game before any menu exists, and then the mods list route is unavailable. The log becomes the only witness. Search it for the library's mod id, yet_another_config_lib_v3, and read the lines around the match. A line recording the mod as loaded, followed later by another mod's failure, clears the library and indicts the later mod. No match at all means the loader never registered the file, which points back to the folder, the filename or a duplicate confusing the scan. The log test is slower than the menu test and stronger: it works when nothing else does, and it timestamps the library's fate inside the exact launch that failed.
Save that log before you change anything. Launch logs are usually overwritten on the next start, and the failing launch is the evidence. A saved copy lets you compare the before and after of your fix line by line.
Two verifications for two different claims
Notice that verification splits into two claims that are often confused. The first claim is presence: the loader loaded a YACL build. The second is fitness: the build satisfies the mods that required it. The mods list proves presence. Fitness is proven by the dependent mod running and its screen opening, or by the absence of a range complaint at launch. A player can hold presence without fitness, the wrong build loads beautifully, and fitness without presence is impossible. Naming which claim you have proven tells you which guide to open next when something still feels wrong.
Making verification a reflex
Build the check into the install motion itself: download, place, launch, open the list, read the version, close. Thirty seconds. The players who skip it are not saving time; they are borrowing it from a future debugging session at compound interest. Every troubleshooting guide on this site begins by re-running this verification because it is so often skipped, and each begins there reluctantly, the way a doctor begins with the obvious questions. Make the reflex yours and most of those guides become reading material instead of rescue.
Verification closes the loop the download opened
The download finder promises a file matched to your version and loader. Verification is where that promise is kept or caught. Treat the two as one act split across a launch: select, place, start, read. Once the read-back becomes part of the same motion as the download, the library stops being a source of surprises and becomes what it was published to be, invisible groundwork under the mods you actually think about.
Keep the evidence
When everything passes, note the working combination in the profile's notes or a simple text file: game version, loader, YACL version and the dependent mod's version. That note turns any future update into a comparison instead of an investigation. Modpack players will find the same habit pays off when a pack update changes one part of the set.


