Skip to content

Creating a Content Release

Essential Information

A Content Release is essentially a ZIP file containing all the necessary files for your Minecraft instance. This typically includes folders like mods, config, resourcepacks, etc. It should contain the minimum files required for your instance to function correctly.

Whenever you want to update your release, upload a new ZIP file. This new ZIP is identical to the previous one but with the modifications. Every Content Release should include all necessary files, even if they haven't been changed. Later, in the Content JSON, you'll specify which files need to be modified or not, as well as the version of that Content instance.

How to Create a Content Release

To create a Content Release, you can use any launcher. I recommend using MultiMC. Once you have all the necessary files for your instance, compress them into a ZIP file.

Compatible Mod Loaders and Additional Information

ONE Launcher is compatible with all popular mod loaders, including:

  • Fabric
  • Forge
  • Quilt
  • NeoForge

Under no circumstances should you include the Minecraft versions folder. The mod loader is specified in the Content JSON and the launcher will be responsible for installing the corresponding mod loader, so there's no need to include it in the ZIP.

Files to Exclude

In the Content Release ZIP file, you should not include the following:

  • Any user-related information like usercache.json.
  • Any launcher-related files like launcher_profiles.json, realms_persistence.json.
  • Any of the following folders: assets, cache, libraries, logs, versions.

Basically, only include the minimum files required for the instance to function. Nothing more.

Content Release Example

If you'd like to see an example of a Content Release, please refer to this specific point.

Publishing a Content Release

For more information on how to publish your Content Release, continue to the next page.

Released under the MIT License