FuzzyBot: Updating to match new version of source page

2026-11-06T21:50:17Z

Updating to match new version of source page

New page

<languages />



[[File:ShroudForge-Wiki-engine.svg|thumb|left|600px|Engine]]

<br style="clear:both;" />

Check shared requirements for the game, runtime, mod API and parser. These checks explain why a feature is ready, still waiting or unavailable.

== Game and runtime ==

ShroudForge distinguishes the client from the dedicated server. Some features are intended for only one process. The runtime gives supported mods access to the running game. A missing or failed runtime startup can affect several mods at once.

“Waiting for game” or a world that is still loading describes an operating state. It does not by itself mean a mod is broken. World-dependent features become ready only after the required game data exists.

== Game profiles and mod profiles ==

Game profiles describe supported native access for a game build. A missing matching profile can limit particular features. Read the specific message instead of assuming that every mod is unavailable.

DLL compatibility profiles serve a different purpose. They associate a mod with its files and known adaptations. Matching uses the mod ID or folder name without requiring a DLL hash or an exact mod-version match.

== Mod API and parser ==

The mod API supplies functions for Lua mods. A mod needs to support the API it uses and declare the necessary permissions. The parser reads and processes game data for asset changes. A Lua mod and a native DLL can therefore have different requirements.

== If startup fails ==

Read the affected component and its reported cause. When asset preparation fails, ShroudForge can stop game startup to protect file consistency. The message states the required recovery. A loaded DLL confirms its own loading step, rather than every feature of the mod.

[[Category:guide:Shroudforge]]

Engine/en-gb - Revision history

FuzzyBot: Updating to match new version of source page