Stardew Valley Mod Manager
  • Welcome
  • Getting Started
    • Setup and Configuration
      • Downloading The Application
      • Installing the Application
      • Setting up the Application
      • Running with Elevated Privileges
    • Navigating the Mod Manager
    • Updating the Mod Manager
  • Mod Management
    • Installing Mods
    • Enabling and Disabling Mods
      • Enabling Mods
      • Disabling Mods
    • Mod Presets
      • Load a Mod Preset
      • Create a Mod Preset
    • Updating Mods
    • Installing Modpacks
  • Game Save Management
    • Create a Game Save Backup
    • Access Game Save Backups
    • Deleting a Game Save
  • Developer
    • Developing for Stardew Valley Mod Manager
      • Making Mods Compatible with the Mod Update Check utility.
      • Creating a Modpack
        • [Legacy] Create a Modpack
Powered by GitBook
On this page
  • Understanding the Mod Update Check Tool
  • Making your Mod Compatible
  • Pre-Requisites
  • Manifest JSON Examples
  • Check for Compatibility Issues

Was this helpful?

  1. Developer
  2. Developing for Stardew Valley Mod Manager

Making Mods Compatible with the Mod Update Check utility.

This article will help you, as a mod developer, ensure that your mod is compatible with the Mod Update Check utility that is offered within Stardew Valley Mod Manager.

Understanding the Mod Update Check Tool

The Mod Update Check tool allows the Stardew Valley Mod Manager user select a mod and check to see if they have the most up to date version of the mod. It uses a series of important information and details from the local machine and the web to determine this.

If you currently offer your mod via the NexusMods website, the chances are you are already compatible with the Mod Update Check utility.

Making your Mod Compatible

Pre-Requisites

In order for your mod to be compatible with the Mod Update Check utility, please ensure that your mod meets the following criteria:

Manifest JSON Examples

The following is an example of a good manifest.json that is located at the root directory. It is a good manifest.json file as it contains a version number and a properly formatted NexusMods UpdateKey.

{
    "Name": "My Awesome Mod",
    "Author": "RWE Labs",
    "Version": "1.24.8",
    "MinimumApiVersion": "3.14.0",
    "Description": "A really cool mod for demonstration purposes.",
    "UniqueID": "RWELabs.AwesomeMod",
    "EntryDll": "AwesomeMod.dll",
    "UpdateKeys": [ "Nexus:1234" ]
}

The following is an example of a bad manifest.json that is located at the root directory. It is a bad manifest.json file as it contains multiple update keys for different services. Please note when we say this manifest is bad, we only mean in context of being compatible with the Stardew Valley Mod Manager. Otherwise, this Manifest is completely functional and good.

{
    "Name": "My Awesome Mod",
    "Author": "RWE Labs",
    "Version": "1.24.8",
    "MinimumApiVersion": "3.14.0",
    "Description": "A really cool mod for demonstration purposes.",
    "UniqueID": "RWELabs.AwesomeMod",
    "EntryDll": "AwesomeMod.dll",
    "UpdateKeys": [ "Nexus:1234","GitHub:MyUser\Repo2" ]
}

Check for Compatibility Issues

Now that you have created a compatible manifest file, simply open the Stardew Valley Mod Manager and click "Updates". Use this to check your mod for updates.

PreviousDeveloping for Stardew Valley Mod ManagerNextCreating a Modpack

Last updated 2 years ago

Was this helpful?

Page cover image