YetAnotherConfigLib

YACL Version Ranges Explained: Minimums, Caps and Exact Pins

A version range is the condition a mod places on its library. A minimum lets you use that build or any later compatible one. A capped range sets a floor and a ceiling. An exact pin allows one build. The loader checks the installed file against the condition at startup and reports both numbers when they disagree.

Voxel ruler across YACL JAR files marking the allowed version zone

Where ranges come from

Every mod that depends on YACL writes the condition into its own metadata when its author builds it. The loader reads that metadata before the game opens. This is why the wording in an error message is worth trusting over a forum post: the message is generated from the file in your folder, for the version you actually installed, at the moment it failed.

The same mod can carry different conditions in different releases. A range you satisfied last month can tighten after a mod update. When a previously working profile starts failing after an update, compare the new message with the old setup before changing anything else. The update moved a boundary, and the message tells you which one.

Minimum versions: the open door

The most common condition is a minimum: version 3.7.0 or later, in the style Fabric's loader uses in its messages. Any YACL build at or above the floor satisfies it, provided the build also targets your Minecraft version and loader. In practice you pick the newest build the finder offers for your combination, and it clears the floor with room to spare.

The trap hides in that proviso. A minimum says nothing about game versions. YACL 3.7.0 satisfied the number while never being published for Minecraft 1.20.1 to 1.20.6, a gap documented in a public issue for the Zoomify mod. The number can be reachable and the file still unavailable for your setup. Both halves of the match matter every time.

Capped ranges: the ceiling matters

Some mods cap the range because a later library changed behaviour they rely on. A capped condition might accept the 3.6 line and refuse 3.7. In that case the newest build is the wrong answer, and installing it produces the same class of error as installing one that is too old. The loader message reports what it found and what it wanted; read both halves instead of assuming the fix is always newer.

Forge and NeoForge mods express ranges in the interval style used by their metadata, with brackets and commas. You do not need to parse the notation perfectly. The loader's plain-language summary in the error screen, and the mod's release page, both restate the condition in words.

Exact pins and single-version conditions

An exact pin appears most often in modpacks, where the set was tested as a unit. It behaves like a range whose floor and ceiling meet. Treat a pin as a request for that specific file, find it through the older releases route, and resist the urge to round it up to the newest build. If the pinned build genuinely cannot be found for your game version and loader, the pack's own notes for your pack version outrank any general advice, including this page.

How the loader reports a failed range

A Fabric message names the requesting mod, the library's internal name yet_another_config_lib_v3, the required condition and the versions it found. A real example from the Zoomify issue reads, in part: requires version 3.7.0 or later of YetAnotherConfigLib, but only the wrong versions are present: 3.6.6 and 3.5.0. Notice that two copies were present at once. Duplicate files are their own fault, covered in the troubleshooting category, and they make range messages harder to read because the loader lists every copy it found.

Copy the full message into a note before you change files. After each change, compare the new message with the old one. A message that changes tells you the last change had an effect, even if the game still stops. A message that stays identical tells you the file you changed was not the file the loader is reading, which points at the profile folder problem instead.

How ranges appear on mod pages

Mod pages express the same conditions in friendlier words. A requirements list may say YACL 3.x, meaning the whole third line is acceptable, or name a specific build it was tested with, which authors write as guidance rather than as the coded condition. The coded condition inside the mod file is what the loader enforces. When the page and the loader message seem to disagree, the loader message wins, because it quotes the file in your folder.

Marketplace pages add one more layer: the dependencies shown for a specific file version. Always open the dependencies of the exact file you downloaded. A project page's general description can lag several releases behind its newest file, and its requirements sentence may describe a version you do not run.

Version numbers are not decimals

Library versions compare part by part, not as decimal numbers. Version 3.10 is later than 3.9, even though 3.10 looks smaller if read as a decimal. The catalog's own history shows the pattern: 3.9.7 was followed by 3.9.9 and 3.9.10 within the same game branch. When you judge whether a build clears a floor of 3.9.5, compare the parts in order: the 3 matches, the 9 matches, and 10 beats 5. Players who read versions as decimals occasionally reject the newest build as too old, which is a confusing five minutes nobody needs.

Ranges and the mods that set them loosely

Not every author sets a careful range. Some mods accept any version of the library's current line, trusting the library's own consistency. Those mods almost never appear in mismatch stories. The ones that do appear set either a floor that raced ahead of publishing or a ceiling that guarded a real incompatibility. Reading a range is therefore partly reading an author's caution level, and a tight range is information: this author found, or fears, a sharp edge. Respect it even when a newer build tempts you.

If you build packs, set your own notes the same way. Record not just the library version you shipped but the range the strictest mod in the set imposed. That single line explains your choice to anyone maintaining the pack after you, including future you.

Floors, ceilings and game versions interact

A range is checked against the library, but the library builds available to satisfy it are bounded by your game version. Picture the range as a window and the catalog for your game version as the buildings visible through it. A wide window over an empty street still gives you nothing to install. This interaction is why the same mod can be easy to satisfy on one game version and impossible on its neighbour, and why moving a whole profile's game version is sometimes the honest answer to a range problem.

Reading a range written by the loader at startup

The loader prints ranges in its own notation when it refuses to start, and the notation is compact: a mod id, a version predicate and the version it found. Reading it aloud in words is the skill: this mod wants the library at 3.7.0 or above; the folder holds 3.6.6. Every range dispute reduces to that sentence, plus one check of the catalog to see whether a build satisfying the predicate exists for your game version and loader. Players who translate the notation into a sentence stop fearing the message, because the sentence contains the whole problem and most of its solution.

Keep the found version in the sentence. Many players fix the predicate side, hunting for any satisfying build, while the found side holds the real story: a duplicate, a wrong-loader file or a build for another game version that the loader counted and rejected. The message reports what it found; believe it, and go and look at the file it means.

Exact pins, and why some mods use them

Most ranges are floors or spans, but a mod may pin an exact build. Pins appear when a mod depends on behaviour that changed between builds, or when an author wants to freeze a known-good pairing during a fast-moving season. An exact pin is brittle by design: it trades your freedom to update the library for the author's certainty. Honour it literally. The build either matches digit for digit or the loader refuses, and near misses are misses. The finder makes pins easy to satisfy deliberately, because older builds remain selectable rather than being hidden behind the newest.

When two mods pin differently, the conflict is real and no file resolves it. One mod changes version or leaves the set. Recognising a true conflict early, from the written conditions, saves the hours players spend hoping a download exists that arithmetic forbids.

Ranges across game versions

A subtle trap: a range is satisfied per profile, but players carry expectations across profiles. A build that satisfied a mod on 1.20.1 says nothing about 1.21.1, where the same mod may have raised its floor. When you rebuild a set on a new game version, re-read every requirement as if new. The mods kept their names; their conditions moved with them. The version-range habit is therefore not a fact to learn once but a check to run at every assembly, which is why this site repeats it in the download, install and troubleshooting routes alike.

Choosing inside a range

  1. Identify the condition type: minimum, capped range or exact pin.
  2. In the finder, fix the game version and loader first.
  3. For a minimum, take the newest build offered. For a capped range, take the newest build inside the cap. For a pin, take the named build.
  4. Read the offered filename and confirm its library number sits inside the condition.
  5. Start the game and confirm the message is gone, then test the mod's settings screen.