Maintain the project and publish updates

After the first publication, the linked instance remains the project source. Make changes in the correct environment, validate them locally, and publish from the instance page.

Complete the metadata

Open My projects, choose the modpack, and use Edit metadata. Review:

• name and category;
• detailed description;
• website, wiki, support, issues, source, donation, and community links;
• icon and background image;
• a gallery with up to ten screenshots.

The description supports content formatted with the Tegra editor. Explain the pack’s purpose, requirements, main features, server use, and support channels.

Prepare an update

1. Open the linked instance and choose the environment associated with the channel.
2. Add, update, or remove content.
3. Review settings and overrides.
4. Test game startup, world creation or loading, and the pack’s main flow.
5. Create a backup before changes that can affect worlds.
6. Open Publish.

Tegra compares the current files with the last manifest stored for that environment. Generate automatically builds a changelog from added, updated, and removed items. Review the text, especially when a file replacement changes compatibility without clearly changing the mod name.

Automatic comparison is unavailable on the first local publication or after the previous manifest reference is lost. Write the changelog manually in that case.

Choose the next version

Use the update impact to define SemVer:

• PATCH for compatible fixes and adjustments;
• MINOR for new content that preserves expected compatibility;
• MAJOR for changes that require adaptation, a new world, or break important compatibility;
• suffixes such as -beta.1 for test versions.

Each channel has its own sequence and prevents duplicate SemVer values. The build number remains automatic.

Work with channels

Each published environment corresponds to a project channel. Use channels for combinations or stages that must evolve separately, such as a stable release and a beta.

Check the selected environment before publishing. Publishing from the wrong environment sends its files and feeds the channel linked to it.

Inspect versions in My projects

Select a channel in the project to see its versions. Each item shows SemVer, build, and date.

• Pending upload: the version exists but still needs a manifest or overrides. Use Resume upload.
• Delete version: removes the version and uploaded files. Use it only when the version must be removed from history.
• Edit metadata: changes the overall project presentation and does not create a new pack version.

Recommended release routine

1. Make changes in a test environment.
2. Validate client, server, and affected worlds.
3. Confirm overrides.
4. Generate and review the changelog.
5. Publish with a SemVer value not yet used in the channel.
6. Install the version from Explore into a clean instance.
7. Test an update from the previous version when players are active on that line.
8. Publish requirements and incompatible changes with the release.

To review the package composition, return to the modpack creation workflow.