Prepare the modpack instance

Publishing turns the selected environment configuration into a distributable version. Prepare that source as the clean installation a player should receive.

Before building the pack

• Sign in with a Tegra account, which is required to create and manage projects.
• Use a dedicated instance for the pack.
• Back up worlds used for testing.

Build the environment

1. Create an instance or choose an installation already separated for the project.
2. Give the environment a name that identifies its purpose, such as Stable, Beta, or Minecraft 1.21.1.
3. Install mods through Tegra search whenever possible. This lets Tegra record the file source for automatic resolution in the manifest.
4. Add resource packs, shaders, and custom files required by the experience.
5. Adjust settings in config and, when applicable, defaultconfigs.
6. Start the game and validate world creation, server connections, menus, recipes, and the pack’s core features.

Choose distributed content

Tegra scans these environment areas by default:

• mods;
• resourcepacks;
• shaderpacks;
• config;
• saves;
• defaultconfigs;
• options.txt.

Internal Tegra files and local instance metadata are excluded from publication.

During override selection, mods, resource packs, shaders, and files under config without an automatic download are selected by default. Worlds, defaultconfigs, and options.txt remain available but start unselected.

Caution

Review every world before including it. A file under saves can contain inventories, coordinates, messages, and other data from the test environment.

Understand automatic resolution

When an installed mod has a recorded download source, Tegra includes its reference in the manifest. The player obtains that file during installation without requiring its binary in the override archive.

A file with no recognized source must be selected as an override to reach the player’s installation. This includes private builds, team-created content, and manually added files.

Check the license and redistribution rules before sending any file as an override.

Validation checklist

• The game starts from a clean installation.
• Required dependencies are installed.
• Client and server settings were tested in the appropriate context.
• Personal files were removed or unselected.
• The pack works without data available only on the creator’s computer.

When the instance is ready, continue to publish the first version.