Skip to content

Common Errors

This is every error that you can see and how to fix it

Verifying

A check stopped at the first problem

Error: Error: stopped at the first failure, pass --keep-going to carry on

How to fix: Add --keep-going so it checks everything instead of stopping at the first thing it dislikes, then read the whole list.

The project did not pass its checks

Error: Error: 3 things wrong, not building

How to fix: Run ehmodpack verify --keep-going to get the full list of what it dislikes, the count is how many are wrong, and nothing is built until they are sorted.

The lockfile is stale

Error: Error: ehmodpack.lock.json is stale, run `ehmodpack lock`

How to fix:

Your packages.json was edited without re-locking, so the lockfile is a snapshot of something that no longer exists, run ehmodpack lock to regenerate it.

The targets changed

Error: Error: targets changed, softwares.json has 1.21.11+fabric, ehmodpack.lock.json has 1.21.11+fabric, 1.21.8+fabric, run `ehmodpack lock`

How to fix: You added or removed a Minecraft version or loader and the lockfile's list of targets no longer lines up, run ehmodpack lock to rebuild it against the new list.

A resource pack cannot be verified for that version

Error: Error: dramatic-skys has no way to verify this is for 1.21.11!

How to fix: The resource pack's own pack.mcmeta does not declare support for the Minecraft version that target uses. Eh's Modpack reads pack_format, supported_formats, the min_format/max_format pair and any overlay layers out of the zip, and none of them cover this target's pack format, which means Minecraft itself would show the pack as incompatible or complain about invalid metadata.

Update the pack to a version that supports every target you build for, replace it, or fix its pack.mcmeta so the declared range is actually true. This appears in ehmodpack verify (which stops at the first one unless you pass --keep-going) and while sync-pack-active downloads the active packs.

Building

The lockfile is stale

Error: Error: packages.json changed since ehmodpack.lock.json was written, run `ehmodpack lock` first

How to fix: Run ehmodpack lock, then build again.

Commands like add, remove, find --remove, order, update and set-release all change packages.json and none of them re-lock for you, so you might end up in this situation.

The build quietly used an old lockfile

ehmodpack build without --locked only auto-locks when the lockfile is missing completely, a lockfile that exists but is stale gets used silently, and you ship the old mod versions without being told.

How to fix: Either run ehmodpack lock yourself before building, or use ehmodpack build --locked so a stale lockfile stops you instead of quietly shipping.

The target you asked for does not exist

Error: Error: no target matches 1.21.12+fabric, have 1.21.11+fabric, 1.21.11+quilt

How to fix: Your --mc or --loader did not match anything, the message lists the targets you actually have, so pick one of those.

More than one target matched

Error: Error: 1.21.11 is ambiguous, pick one of 1.21.11+fabric, 1.21.11+quilt

How to fix: You left out the part that tells them apart, add --loader as well as --mc.

There is no loader to build against

Error: Error: this modpack does not name a loader, so there is nothing to build against

Error: Error: this pack has no loader ehmodpack knows, pass --loader

How to fix: The project has no usable loader, which usually means softwares.json was edited, either pass --loader explicitly, or fix the file.

The lockfile is from an older version

Error: Error: ehmodpack.lock.json is lock format v1, this build understands v3, run `ehmodpack lock` again

How to fix: The lockfile was written by an older version of Eh's Modpack, running ehmodpack lock regenerates it in the current format.

A download did not match its hash

Error: Error: sodium did not match its sha512, the download is corrupt. got abc123 wanted def456

Error: Error: sodium did not match its sha1, wanted abc123 got def456

How to fix: The file that came back is not the file that was locked, so it refuses rather than continuing, lock again and build once more.

If it keeps happening, the download got cut short, so let it finish before building.

No Java was found

Error: Error: no java was found at all, ehmodpack looked in C:\Program Files\Java, C:\Program Files\Eclipse Adoptium

Error: Error: no java 21 or newer was found (found: java 17 at C:\Program Files\Java\jdk-17\bin\java.exe), ehmodpack looked in C:\Program Files\Java

How to fix: It couldn't find your java installation in all directories, the second error was that the java version for the project wasn't found but found an other old version

Either install Java if you haven't yet, or Update your java to match the project's java version, you can run ehmodpack java after to see if it recognizes

You refused to install java

Error: Error: java 21 is needed to test this pack and nothing was installed

How to fix: test needs that java version to launch the game and you either answered no, or the ask could not happen without a terminal, answer the install question with Yes, or pass --install-java-if-no-there to skip that question

The java vendor is unknown

Error: Error: unknown java vendor foo, have: eclipse-adoptium, azul-zulu, amazon-corretto

Error: Error: this cpu architecture (riscv64) has no java download here

How to fix: --vendor only knows 3 vendors (temurin, zulu and corretto also work), you can either drop --vendor to get a question or do --install-java-if-no-there to get Eclipse Adoptium's java

The auto-download only covers x64 and aarch64 machines

The build stamp could not be written

Error: Error: could not write the build stamp: could not write dist/.built.json

How to fix: Publishing already finished, this only means the .built.json stamp could not be saved, so the next publish with identical inputs cannot skip rebuilding and will do the work again. It is usually a permissions problem in the output folder, and it is safe to ignore if the folder looks fine.

Adding and removing content

It is already in the project

Error: Error: sodium is already in packages.json

How to fix: The project is already added, use ehmodpack remove sodium first if you want to add it again.

It is a modpack

Error: Error: some-pack is a modpack, ehmodpack does not stuff modpacks inside modpacks

How to fix: You cannot add a modpack as a dependency of another modpack, open the other pack with ehmodpack new-from-mrpack instead.

That version does not exist

Error: Error: Sodium has no version 0.7.0.0 for 1.21.11

How to fix: --version is an exact version string from Modrinth, not a range and not "latest", check what exists in the project's versions, if you want the newest one instead, --version '*', * is the value that means "latest".

That project does not support the loader

Error: Error: Some Mod (some-mod) supports ["fabric"], not ["neoforge"]

How to fix: That project has no build for the loader your target wants, because the game and loader is read off from softwares.json, the only fix is using a target of a loader that project supports.

Only some targets worked

Error: Error: skipped sodium for 1.21.8+fabric: ...

How to fix: This is a warning and not an error, you have more than one target and the version only exists for some of them, so it was added where it worked and skipped where it did not, pass --mc to add it for one target only instead.

Nothing was added

Error: Error: nothing was added

How to fix: Every target failed, usually because of the loader or the version above, fix the cause, or point at one target with --mc to find out which part is wrong.

It is not in the project

Error: Error: sodium is not in packages.json

How to fix: Nothing matched that name, names are matched without case, so if it is genuinely is not there, ehmodpack list shows what content you have added.

ehmodpack remove takes only a project name, it removes that project from every target at once, and obviously does not re-lock afterwards.

The query was too vague

Error: Error: give a project id, slug, embedded id, or an exact version string

How to fix: ehmodpack find matches a project id, slug, embedded id or an exact version string, not a loose phrase, try one of those instead.

Updating

The update was aborted

Error: Error: update was aborted before anything was written

How to fix: ehmodpack update found some versions it could not resolve and refused to write a half finished set of pins and will not write it, the individual failures are printed above it, fix those and run it again, ehmodpack update --dry-run shows what it would do without writing.

A project changed identity

Error: Error: some-mod now identifies as AAAAA, but this project is known to be BBBBB

How to fix: A project you track by one identifier is now publishing under another, and it will stop rather then guess, edit packages.json yourself with the right ID/Slug.

Error: Error: some mods changed identity, update packages.json by hand before continuing

How to fix: The same thing for several projects at once, fix them all in packages.json, then run ehmodpack update again.

The download was not the mod you asked for

Error: Error: no modrinth build of some-mod can be confirmed for 1.21.11 (the candidates were not that mod)

How to fix: The file that came back did not identify itself as the mod you asked for, so it refuses to go any further, this usually means the project was renamed or transferred, check the project on Modrinth and fix its entry in packages.json.

No version matched

Error: Error: some-mod has no version matching >=1.21 <1.22 for 1.21.11

Error: Error: some-mod has no version for 1.21.11

How to fix: That project has no build for the Minecraft version your target wants, either drop that target or use a project that supports it.

Publishing

The token is not shaped like a token

Error: Error: That isn't the right token, modrinth only accepts: mrp_, mra_ or mro_!

How to fix: Your Modrinth access token does not start with one of those three prefixes, copy the whole thing, since it is only shown once when you create it.

The token is missing a scope

Error: Error: Sorry, you did not select Read Projects, Create Versions and Write Versions when generating the token, edit it to have it!

How to fix: The token works but is missing scope(s), edit your token on Modrinth and tick Read Projects, Create Versions and Write Versions.

The token was not accepted

Error: Error: That token was not accepted by modrinth, check you copied the whole thing, the token is shown only once when you make it

How to fix: The token got cut off in a paste or in transit, generate a new one and copy it in full.

The token does not work

Error: Error: the token you passed is not working, so nothing was done

How to fix: It is invalid or expired, delete the saved one and do it again, or pass a fresh --token.

Nothing was typed where the token goes

Error: Error: this is not a token

How to fix: The paste did not land, try again and make sure the whole token goes in.

The saved token is damaged

Error: Error: the saved secret is truncated, it cannot be read

How to fix: The encrypted token file on disk is damaged or was cut short, clear it and enter the token again, and if you set a passphrase, remember it, because it is the only thing standing between your token and anyone who reads it.

The project does not exist

Error: Error: Sorry, this project no longer exists, either it was deleted privated or simply gone

How to fix: The project ID you gave is not a live public project any more, or it was made private, copy the ID again from the project you actually mean.

You cannot publish to that project

Error: Error: Sorry, you don't have permissions over AAAA to publish it, did they gave you the exact permissions?

How to fix: That project is not yours to publish to, or your token does not have write access to it.

The project is missing an id or a version

Error: Error: no version to publish, set "version" in packages.json

How to fix: Set the version field in packages.json, as it becomes the name of the release on Modrinth.

Error: Error: no project id, nothing was published

How to fix: The CLI needs the project ID, on Modrinth that is your project page, the 3 dots menu, then Copy ID, you can also set modrinth_project_id in packages.json.

Nothing was left to publish

Error: Error: no target left to publish

How to fix: Your --mc or --loader filter left nothing to build, drop the filter or pick a target that exists.

An external resource pack will probably be withheld

Warning: Warning: Otherwise this is a resource pack for the modpack, Custom UI.zip will most likely will be withheld in Modrinth's side!

How to fix: This is a warning and not an error, a simple notice that anything bundled from your overrides that did not come from Modrinth is "external content of unknown origin" under Modrinth's permissions system, and if that version uploaded gets withield you must tell Modrinth where each file came from.

Before publishing, note the source and license of every external zip so you can declare them on the permissions page, see Modrinth's modpack permissions announcement for their news, files that come from Modrinth itself do not need this.

All of the versions were withheld

Warning: Warning: All of the version(s) published got withheld by modrinth, you might need to resolve it by going over here: https://modrinth.com/project/AAAA/settings/permissions

How to fix: Every version that was just uploaded is hidden until you tell Modrinth the permissions for the external files inside, on your permissions page and for each pending file resolve it, then submit for review again.

Some of the versions were withheld

Warning: Warning: v1.0.1-1.21.8, v1.0.1-1.21.9 was withheld when it was released, you might need to resolve it by going over here: https://modrinth.com/project/AAAA/settings/permissions

How to fix: Same as the above, but only the versions listed in the message are withheld, and the others not listed are public.

The withheld check could not run

Error: Error: could not check whether modrinth withheld anything: modrinth answered 500 for the version list

How to fix: Uploading was a success, but checking whether anything was withheld failed, in most cases Open the project's permissions/versions page to be sure nothing was withheld, if there is, resolve those and try again

Targets and loaders

That target already exists

Error: Error: 1.21.11/fabric is already a target

How to fix: That combination is already in softwares.json.

That version is not one of your targets

Error: Error: no target for 1.21.8, this pack has 1.21.11+fabric, 1.21.11+quilt

How to fix: one-ver was asked to keep only a version that is not in the project, check the list in the message and try again, be noted that one-ver drops every other target when it does run.

There are no targets at all

Error: Error: no targets, add one to softwares.json

Error: Error: nothing to install into, packages.json targets got emptied

How to fix: The project has no build targets, so there is nothing for to work with, add a target, or if you emptied softwares.json by accident, restore it and lock again.

A resource pack has no position

Error: Error: "coolpack" needs a position, like "coolpack"=1, or --off to clear it

Error: Error: "coolpack" needs a position, like "coolpack"=1 or "coolpack" 1

How to fix: Resource packs need an explicit position because load order is bottom up, 1 or top is the top of the stack, bottom also work.

Error: Error: --off does not take a position, just the pack name

How to fix:

--off is a clear, not a move, give just the pack name.

The position is not a number

Error: Error: "toppish" is not a position, use a number like 1, or top or bottom

How to fix: Spelling is off, it is top or bottom, or a number.

The position is 0

Error: Error: a position of 0 is not a thing, 1 is the top of the stack

How to fix: Counting starts at 1.

That is not a resource pack

Error: Error: "sodium" is not a resource pack here, try one of: coolpack, otherpack

How to fix: order only works on resource packs, the message lists the ones you do have.

Network

Blocked by your internet provider

Error: 

Error: We're unable to connect to Modrinth since it has been blocked by your internet provider

If this is your computer on your wifi and this error also is a normal webpage on your browser, then Modrinth is blocked in your territory until it is unblocked

If this is a school device, your school admin blocked Modrinth and its APIs to be able to fetch, contact them to remove the ban or pass EHMODPACK_API= when doing requests

How to fix: Something between you and the API answered by changing the webpage to something else instead, and Eh's Modpack recognizes its wording

Open the same URL in your browser, if it shows a "blocked" page it is blocked, remove it through your ISP's login (if your provider offers that), wait until it gets unblocked, or if it is a school network ask the admin to unblock it, or point eh's modpack way to connect to somewhere else with EHMODPACK_API=<url>.

If the loaders are also blocked you can also pass EHMODPACK_FABRIC_META, EHMODPACK_QUILT_META and EHMODPACK_NEOFORGE_MAVEN.

The API answered with a webpage

Error: Error: We couldn't connect to Modrinth since something between your internet made Modrinth's API a webpage instead

How to fix: The request got HTML where JSON was expected, but it didn't know if it is blocked on your territory or not, if it is a public wifi and it requires login, finish logging in and try again

In most other cases, if opening the URL tells you that page was blocked, Blocked by your internet provider applies

Others

You are not in a project

Error: Error: no packages.json found in . or any parent directory

How to fix: You are not in a eh's modpack project.

The folder already has things in it

Error: Error: <folder> already exists and is not empty, pass --force to write into it anyway

How to fix: ehmodpack new will not write into a folder that already has something in it, pick another name, or pass --force if you really mean it.

Creating a project needs more

Error: Error: the modpack needs at least one minecraft version

Error: Error: the modpack needs at least one loader

How to fix: A project needs at least one Minecraft version and one loader, pass them with --mc and --loader, or answer the questions when prompted.

Git would not start

Error: Error: git init failed in <folder>

How to fix: You passed --git but git could not make the repository, make sure git is installed and on your PATH, or you can not pass --git and do it later

A prompt cannot open

Error: Error: this needs a terminal, pass --mc and --loader instead

Error: Error: removing needs a terminal so you can confirm

How to fix: A prompt needs to ask you something and there is no terminal to ask at, which means output is being piped or redirected, pass the answer as a flag instead.

That loader is not wired up

Error: Error: It only wires fabric up so far, quilt is not there yet sorry

How to fix: That loader is not supported by that part of the tool.

That library is not a Maven coordinate

Error: Error: com.example:thing is not a maven coordinate

How to fix: A library reference was written in a shape Eh's Modpack does not read, fix the coordinate in your overrides.

A template has a placeholder in it

Error: Error: .github/workflows/build.yml still has an unsubstituted __THING__ placeholder, refusing to scaffold it raw

How to fix: That is a bug in Eh's Modpack and not in your project, a template grew a new placeholder and nobody taught the scaffolder to fill it in.

The version cannot be empty

Error: Error: the version cannot be empty

How to fix: ehmodpack set-release was given nothing, give it the version you want, which is usually the tag name.