Mod Organizer Integration Plugins

Collection of plugins to allow better integration of mods with Mod Organizer 2.

Installation

• Download latest release (section Packages > mod-organizer-integration-plugins.zip)
• Extract content of the archive to the root of Mod Organizer 2

Plugins

GitGud Package Tracker

Plugin allows to track the latest versions of mods from GitGud.

On launch it checks the latest versions for all gitgud mods (given that mod creator distributed mod with required metadata). Also checks the latest version of a mod right after it's successful installation.

Example

For example we have non-nexus mod:

If mod contains required metadata you should see the following behavior.

When mod is up-to-date:

When mod is outdated:

For mod creators

To receive MO2 notifications about new versions of the mod (without any need in nexusmods approvals) can be achieved by including metadata inside mod archive. To achive that at the root of mod archive create file meta.ini with section [Plugins] and attributes GitGud\projectId, GitGud\releaseId and GitGud\fileId.

Example of meta.ini file for release https://gitgud.io/madtisa/cc-sk-compatibility-mod/-/releases/1.0.0

[Plugins]
# GitGud project id (number, required)
GitGud\projectId=19426
# Release version of mod (string, optional for now, but will be used in future)
GitGud\releaseId=1.0.0
# File identifier - the name of file in the release (string, optional for now, but will be used in future)
GitGud\fileId=CC-SK Compatibility Mod.zip

Project id can be found on main project folder:

Release and file ids on related release page:

Karryn's Prison Plugin

The plugin adds support for Karryn's Prison game. Without it you won't be able to use MO2 to manage Karryn's Prison mods.

Internal Metadata Extractor

The plugin allows to store mod metadata (e.g. modName, version) inside mod package.

By default MO2 overrides modName and version of non-nexus mods:

After installing the plugin name and version of mod can be specified inside mod archive:

For mod creators

All stardard MO2 metadata properties can specified inside mod archive.

For example, to specify mod default name and mod version you should add meta.ini file with following content:

[General]
# Suggested mod name on installation (string)
modName=CC-SK Compatibility Mod
# Version of the mod. Won't be overriden by MO2 if specified
version=1.0.0

Before installation file meta.ini will be extracted as archive MO2 metadata (as if immitating nexus download) and metadata will be used in process of installing mod and preserved after.

Also useful metadata attributes:

• directURL - required for creating wabbajack modlists
• url - custom url to package page
• hasCustomURL - indicates whether it's a non-nexus mod
• category - List of mod categories
• etc...