View source for Dependencies/en-gb

<languages />

<!-- ShroudForge MediaWiki migration metadata
title: Dependencies
description: Find required components and known conflicts between mods. This view explains what blocks an active mod and which dependency needs attention.
language: en
creator: Bonsaibauer
source: modules/wiki/articles/dependencies/en.md
-->


Find required components and known conflicts between mods. This view explains what blocks an active mod and which dependency needs attention.

[[File:ShroudForge-Wiki-dependencies.svg|thumb|right|alt=Dependencies|Dependencies]]

== Required mods ==

A mod can declare other mods and their required versions in <code>mod.json</code>. ShroudForge checks whether they are installed, enabled and suitable for the current client or server. A missing or disabled required dependency prevents the affected mod from starting. An incompatible version also blocks it.

Open the named mod, install or enable its requirement, then check this view again. Not every installed mod needs to run in the current process. A client-only mod does not need its own startup on a server.

== Optional dependencies ==

An explicitly optional dependency may be absent or disabled. An extra feature may then be unavailable. If the dependency is present and enabled, its version and further requirements still need to match.

Mods without declared dependencies need no separate problem entry here. Their overall status remains available on their own mod pages.

== Conflicts and cycles ==

Known conflict rules identify two active mods that should not run together in the specified combination. Use the message to decide which one to disable. A dependency cycle means mods require each other to start first. This needs a package correction or a change by the author.

A requirement for <code>shroudforge-api</code> refers to the loader's mod API. It is separate from automatic DLL compatibility-profile matching.


[[Category:guide:Shroudforge]]