Import Modpacks

Ephervex imports Modrinth .mrpack archives and CurseForge modpack exports. It reads the pack's Minecraft release and loader selection rather than choosing newer versions for you. Other launcher exports, including Prism and MultiMC, are not supported. The archive is identified by its contents, so changing its file extension does not change its format. Release builds include the CurseForge API access needed for imports; no key setup is required.

A pack that pins a Forge build for Minecraft 1.12.2 older than 14.23.5.2851 is refused before anything is downloaded, because those builds use an older installer format that Ephervex does not support.

note

Some CurseForge files still need a manual download when their authors disable third-party downloads. Ephervex guides you through those files during import.

Import an archive

Inspect the pack before importing. Required files are included automatically; optional files start off until you select them. New imported instances use temporary storage unless you choose persistent storage.

Desktop

In the host list or on Home, select Import Modpack. Choose an archive with Browse, or drop it onto the window. Dropping a file works only on X11 or XWayland; see Limitations and Troubleshooting.

Review the detected pack, Minecraft release, loader, and file counts. Turn on any optional files you want. You can change the instance name, select Store persistently, and optionally create a linked server from the same pack. Select Import Modpack to begin.

The new instance appears in the host list with a progress bar while the import runs.

The Activity card on Home shows current work and the result.

CLI

Inspect a local archive without creating an instance:

ephervex import pack.mrpack --inspect

Import it with the pack's own name, or choose a name and persistent storage:

ephervex import pack.mrpack
ephervex import pack.mrpack --name "Pack Test" --persistent

Optional files are off by default. --inspect lists their paths. Select one by repeating --optional with its path inside the game directory, or use --all-optional to include them all:

ephervex import pack.mrpack --optional mods/example.jar

--temporary explicitly selects the default storage. The CLI import command creates a client instance; create a linked server separately if you need one.

Import from a link

A pack address must use HTTPS. Ephervex asks before downloading an archive from a host you have not approved. You can allow one download or remember that host for later. A redirect to another host needs its own approval. Trusting a pack host only permits it to serve the archive; it does not change which hosts may serve files listed inside the pack.

Desktop

A website can offer an Open in Ephervex link using the ephervex://import?url=... scheme. The pack's HTTPS address is percent-encoded in the url parameter. For example, DumpViewer (source) can export a stored dump as a Modrinth pack and open it directly in Ephervex. Confirm the browser's request to open Ephervex, review the pack address and choose whether to remember its host, then review the normal import dialog.

Linux packages install the link handler. For an AppImage, register it once from the command line, using the path to the AppImage you downloaded:

./Ephervex-x86_64.AppImage url-handler register
./Ephervex-x86_64.AppImage url-handler status

Use the aarch64 file name for the ARM build. Register again if you move the AppImage. To remove the AppImage's registered handler, run url-handler unregister with the same AppImage command.

You can review or forget remembered hosts under Settings > General > Sites allowed to serve modpacks.

CLI

Pass the HTTPS archive address directly:

ephervex import 'https://example.com/pack.mrpack'

An interactive terminal asks about a new host. --trust once allows just this import; --trust always remembers the host. In a noninteractive command, one of these flags is required for a host you have not approved. Neither flag approves a redirect to a different host in a noninteractive command.

ephervex import 'https://example.com/pack.mrpack' --trust once
ephervex config pack-hosts
ephervex config pack-hosts --forget example.com

--inspect on a URL downloads the archive and asks for host approval before reporting its contents; it does not create an instance.

Resolve files that need a manual download

Some CurseForge authors disable third-party downloads. Ephervex will not fetch those files automatically or substitute another release. The desktop import dialog lists each blocked file with its project and file name.

Desktop

1. Select Open in Browser beside the blocked file, marked in the image.
2. Download the exact file from its provider page and place it in a watched download folder. Ephervex matches the file by hash and continues when it finds a verified copy.

Manage watched folders under Settings > Storage > Watched download folders. The Downloads folder is watched by default until you configure the list.

Skip leaves that file out and records that it needs attention. Use it only when you intend to import without the file.

CLI

The CLI does not offer the desktop's browser, watcher, and Skip controls. If a required CurseForge file is blocked and no verified copy is already in the shared cache, the import fails. Open the pack in the desktop app to resolve or skip the file, then import there.

Imported packs retain their recipe, including server-side files. You can create a linked server from the instance later.