-
-
Notifications
You must be signed in to change notification settings - Fork 436
Custom Version Manifest
The version manifest is used by the launcher (as well as Mojang's launcher) to determine:
- The Java libraries to load
- The command line arguments to run Minecraft with
- The main class to run
- The version of Minecraft to obtain assets (textures, sounds, etc.) for
For every version of Minecraft, there is an associated version manifest file.
Mod loaders like Forge, LiteLoader, and a small minority of other mods make modifications to the version manifest. Changes include:
- Adding more libraries to the list
- Modifying the command line arguments and adding
--tweakClass
(tweak classes can be considered Mojang's simple method of modding Minecraft)
When you use the launcher's tools to build the modpack, the manifest is downloaded from Mojang's server for the selected Minecraft version, and then modifications required by any mod (loader) in the loaders/ folder are applied.
This version manifest is embedded into the package manifest, which the launcher later uses.
Rather than sourcing the version manifest from Mojang, you can provide your own.
Simply add in a version.json file into your modpack's project files. It should go into the root folder, not src/.
If you are using a version file from a Mojang launcher profile (that was added by an installer like the Forge installer), you may need to remove some libraries from this file before you can use it. The libraries that need to be removed are the ones that have been added directly into the .jar (like a .jar mod).
Need help? See Getting Help.
Tutorial
Launcher Features:
- Fancy Launcher
- Portable Mode
- Hidden Modpacks
- Deploying Server Modpacks
- Launcher Arguments
- Custom JAR (.jar mods)
- Custom Version Manifest
Customization:
- Localization
- News Page Guide
- Custom Microsoft OAuth application
- Using an IDE (Eclipse, IntelliJ)
Additional Reading:
Find the launcher useful?
Donate to obw, the current maintainer:
Donate to sk89q, the original maintainer: