Understand the modpack creation workflow
creating-modpacksLearn how instances, environments, channels, versions, manifests, and overrides form a Tegra modpack.create modpack publish modpack project channel environment manifest overridesenModpack creation in Tegra starts from a working instance. The launcher uses the selected environment as the source for the project, publication channel, and version files.
Structure used by Tegra
Section titled “Structure used by Tegra”The workflow has four levels:
- Instance: the local workspace used to build and test the modpack.
- Environment: an instance configuration with a Minecraft version, modloader, and its own files.
- Channel: the remote representation of an environment within the project. Each channel maintains its own version sequence.
- Version: a release identified by SemVer, an optional name, a changelog, and files distributed to players.
A project can contain multiple channels. For example, a pack can have a stable channel and a test channel, with each one linked to its corresponding local environment.
What happens during the first publication
Section titled “What happens during the first publication”When you publish an environment with no existing link, Tegra follows this sequence:
- Creates the project or links the instance to one of your existing projects.
- Creates a channel from the selected environment.
- Registers the version with its Minecraft version, modloader, and SemVer.
- Scans the environment files.
- Generates a manifest with hashes, sizes, and known download sources.
- Compresses the selected overrides.
- Uploads the manifest and overrides.
- Stores the project link and published version reference in the local instance.
The local link lets later publications use the same project and channel. Tegra also keeps the last published manifest as a baseline for change detection and changelog generation.
Manifests and overrides
Section titled “Manifests and overrides”The manifest describes the version contents. It records the Minecraft and modloader versions, included files, their hashes, and known URLs for automatic downloads.
The overrides are a compressed archive containing files that the project must deliver itself. This includes files without an automatic source, such as local mods, configuration, and resources created for the pack.
This separation reduces upload size and preserves the distribution method of projects obtained from compatible platforms.
Responsibility of each app area
Section titled “Responsibility of each app area”- Library and instance page: prepare, test, and publish the active environment.
- My projects: edit metadata, inspect channels and versions, resume pending uploads, and remove versions when required.
- Explore: present the final result for players to install and update.