Dependencies

Dependencies

How Dependencies Work

Mods declare dependencies in Info.json via the Requirements field. Each entry is a string:

• "ModId" - requires any version
• "ModId-1.2.3" - requires version 1.2.3 or newer

When you activate a mod, DV Mod Manager reads its requirements and activates all dependencies automatically.

Automatic Activation

Dependency resolution uses breadth-first search:

1. You activate Mod A
2. The manager reads Mod A's Requirements
3. Each required mod that's installed but inactive gets activated
4. Newly activated mods' own requirements are processed recursively
5. Continues until all dependencies are active

Version Checking

When a requirement specifies a minimum version (e.g. "SomeMod-2.0.0"), versions are compared using System.Version parsing. Tags like "v2.0.0-beta" are normalized by stripping the prefix.

If the installed version is older than required, the dependency counts as missing.

Missing Dependencies

If a required mod isn't installed, the detail panel lists each missing dependency and its required version.

Limitations

• Only already-installed mods are activated. Missing mods are not downloaded automatically (except when applying profiles, see Profiles Overview)

See Also

• Managing Mods