DOCUMENTATION / IMPORT

Bring a pack with you

The alpha includes supported copy and import workflows. Compatibility depends on the pack format and provider.

Keep your original

Back up the source instance and any worlds before importing. Work from a copy when possible. Keep the original until you have checked the imported instance and your important data.

Import a pack archive

Open Import and select the pack archive using the workflow available in your build. Use a supported exported pack format; an arbitrary ZIP of game files is not necessarily a valid modpack export.

Read any provider or missing-file prompts. Some files may require an official provider website action. Do not assume every archive can be downloaded or installed completely inside the app.

Copy an existing setup

Use the supported copy/import option for your source. Check the selected Minecraft version, exact loader runtime, game folder and settings after import. Provider metadata and update compatibility may differ between formats.

Check before playing

Review what was prepared, then open the official Minecraft Launcher and choose the matching installation. Microsoft sign-in and Play stay there. If the format is rejected or files are missing, keep the original unchanged and ask for help.

Importing an FTB App folder

Use the supported completed-installation folder workflow. Current and older version-metadata layouts have guarded independent-copy support; other FTB exports are not automatically equivalent. Incomplete installs or runtime/metadata disagreement can be rejected. Native FTB App installation and imported gameplay acceptance remain separate.