manifest.json file is the core configuration file for the Orbis Galactic mod. It defines essential metadata about the mod including version information, authors, dependencies, and load order.
File Location
The manifest file is located at the root of the mod directory:Structure
Complete Example
Here’s the actual manifest.json from Orbis Galactic:manifest.json
Configuration Fields
The organization or team name that created the mod. Used for grouping mods from the same creator.Example:
"TastySyntax"The unique identifier name for the mod. Should match the mod folder name.Example:
"OrbisGalactic"The current version of the mod following semantic versioning (MAJOR.MINOR.PATCH).Example:
"1.4.0"A brief description of what the mod provides.Example:
"A star wars mod for Hytale."An array of author objects containing contributor information.Each author object includes:
Name(string): The author’s display nameEmail(string): Contact email (can be empty)Url(string): Link to author’s profile or repository
The official website or repository URL for the mod.Example:
"https://github.com/Tasty-Syntax/Orbis-Galactic"Object mapping mod names to required version ranges. Mods listed here must be loaded before this mod.Example:
{"OtherMod": "^1.0.0"}Orbis Galactic currently has no dependencies
Object mapping mod names to optional version ranges. These mods enhance functionality if present but aren’t required.Example:
{"EnhancementMod": ">=2.0.0"}Object specifying mods that should be loaded after this mod. Used to control load order.Example:
{"CompatibilityMod": "*"}Whether the mod should be disabled when first installed. Users must manually enable it.
Indicates whether this mod includes custom asset packs (textures, models, etc.).Set to
true if your mod includes assets in the Common/ directory.Array of sub-plugin names that are part of this mod package.Example:
["OrbisGalactic_Weapons", "OrbisGalactic_Vehicles"]Best Practices
Version Numbering
Follow semantic versioning:- MAJOR: Incompatible API changes or major overhauls
- MINOR: New features added in a backwards-compatible manner
- PATCH: Backwards-compatible bug fixes
Author Information
WhileEmail can be left empty, providing a Url helps users:
- Report issues
- Follow development updates
- Contribute to the project
Dependencies
When adding dependencies, use version ranges:"^1.0.0"- Compatible with 1.x.x versions"~1.2.0"- Compatible with 1.2.x versions only">=1.0.0"- Any version 1.0.0 or higher"*"- Any version