Client and server are different
A mod’s declared hasClientSupport and hasServerSupport values tell the loader where to attempt loading. They do not prove multiplayer safety, authority, synchronization, or server compatibility.
12 · Compatibility
Compatibility is per mod and per build
Shroudtopia provides a loader contract. It does not make a game-specific patch version-independent. Each mod author must establish supported layouts, features, and modes independently.
Game version field is placeholder
In release 0.2.1-shroudweave.1, context->game.version is initialized as "SVN HERE". Do not use it as a reliable version gate.
Memory signatures can drift
Small hotfixes may move code or alter instructions. Verify executable identity, constraints, and expected bytes; fail closed when they differ.
API compatibility is separate
The fork release is 0.2.1-shroudweave.1. The SDK/API target shown in current examples is 0.1.1. Do not conflate those version numbers.
Current fork notes
Release 0.2.1-shroudweave.1 documents a change that skips Flame-owned and malformed ownership manifests before loading them or applying defaults. It keeps native Shroudtopia manifests and supported legacy DLL discovery. The release notes describe specific validation; they do not establish every possible mod pairing.
Check the release notes and each mod’s own compatibility page before installing.
13 · Troubleshooting
Common problems
Mod does not load
Check architecture (x64), folder path, valid mod.json, expected DLL name, exported CreateModInstance, and the framework log. Confirm the declared client/server flag matches the executable you launched.
Manifest defaults appear missing
Defaults are added only when the mod section is absent. Existing config wins. Confirm manifest id (or folder name) exactly matches ModMetaData.name and the key passed to the getter.
Feature stays inactive
Check mods["your_mod"].active, then inspect your mod’s validation log. An unsupported signature should stay inactive. Do not weaken the guard just to force activation.
Loader or proxy fails at launch
Close the game. Check whether another mod owns winmm.dll. Restore the original backup and resolve proxy compatibility before retrying. Keep the config and logs for diagnosis.
Settings do not take effect
Confirm key spelling, JSON type, range, and the mod key used by Get*. Check whether the mod actually refreshes that value in Update; not every feature supports live edits.