Publish the first version

The first publication creates the remote identity of the modpack and links the local environment to the channel used by later versions.

Open the publication workflow

1. Open the instance from the Library.
2. Select the environment you want to publish.
3. Use Publish on the instance page.
4. If the instance came from another modpack, Tegra opens the fork creation workflow and preserves the origin reference.

Create or link the project

For an environment with no link, choose one option:

• Customize modpack: set the name, slug, icon, and cover before creation.
• Create without customizing: use the instance name and generate the slug automatically.
• Link to existing modpack: associate the instance with a project already owned by your account.

The slug identifies the project in URLs and must be available. Use lowercase letters, numbers, and hyphens. Choose a stable value that is easy to recognize.

When linking an existing project, confirm that the instance represents the correct content. Later publications will feed that project.

Identify the version

Enter a semantic version in MAJOR.MINOR.PATCH format, such as 1.0.0. The same number cannot be reused within the channel.

The version name is optional and can describe the release, such as First release or Performance update. The service assigns the build number as an internal sequence identifier.

Use the changelog to record relevant changes, world requirements, incompatibilities, and server guidance. See semantic versioning to choose the appropriate increment.

Review overrides

Open Version overrides and review every selected file.

• Files with an automatic source remain in the manifest and do not appear as override candidates.
• Selected files enter the compressed archive hosted by Tegra.
• Unselected files stay out of the version.

Include only what is needed to reproduce the pack. Unused settings, test worlds, and personal options increase upload size or alter the player experience.

Publish

1. Confirm SemVer, name, and changelog.
2. Review the selected overrides.
3. Press Publish or Create modpack, depending on the current step.
4. Wait for reading, compression, upload, and finalization to complete.

When complete, the project appears under My projects. The channel uses the environment name, and the local instance stores the project, channel, and current version identifiers.

If the upload is interrupted

The version can be created before its upload completes. It then appears as Pending upload.

Use Try upload again in the dialog, or open My projects, select the channel, and press Resume upload. Review the overrides before retrying because the upload uses the current files from the linked instance.

Avoid creating another version while the previous one is pending. Tegra warns about this state to reduce empty versions in the channel sequence.

Expected result

The channel should show the version with a manifest and, when required, an override archive. Install the modpack into a new instance from Explore and perform a final test outside the creation environment.

After validation, complete the metadata and organize future versions.