Skip to content

Verifying your project

When you have a project you can verify the project to see what will happen, what happened and what can be fixable, which you can run with ehmodpack verify

During verification process it will FIRST check every project against its sha1 and sha512 for every project, and game version(s) you have added so an ETA to finish will depend on the version(s), loader(s), content you have added to your project and mostly your internet speed

Then after verification it will suggest things that might go wrong:

However

When it fixes a version conflict, it can replace it with the same version for the right loader, and if there isn't one for your loader it will grab the latest version instead

  • Bad hashes: a file does not match the sha1 or sha512 it was locked with, so that download is corrupt or something changed it
  • A download that failed: a file could not be downloaded at all, or the project has no download url
  • A changed identity: the mod inside the file now identifies as a different project than the one in packages.json, this one is never fixed for you and you need to edit packages.json by hand
  • Soft conflicts: a mod would like a version of something you do not have, these are only warnings and the pack still works
  • Real conflicts: a mod needs a version of another mod or library and what you have is not it
  • Version conflicts: a mod version that is labeled for the wrong loader or the wrong game version than your target, like a fabric build sitting in a neoforge pack, the label simply does not fit what your pack is

Every file gets a row in a table with its result so you can see what passed and what did not, you can fix those by answering Yes on fix these?