Terms & Mechanics

Full-release mod loading, dependencies and permissions

Troubleshoot mod issues by the different states of subscription, loading, enabling and running, and distinguish missing dependencies, scan rejections and capability confirmation prompts.

Identify the game and the mod

The full-release Steam App is 4348910, and this page is based on the built-in loader of Build 26284217. The game's internal version field for this build is still 0.46D, so seeing "compatible with 0.46D" alone cannot be used to determine that it is a Demo package. Also check the author's full-release notes, the actual download source and the package manifest.

A mod's name, version, compatible game version, dependency IDs, assemblies and capability declarations come from its own manifest.xml. Workshop update time, game Build and mod version each represent different information; if the author has not stated it, do not fill it in on their behalf as currently up to date or already compatible. For the installation location and steps, see Full-release Mod Installation.

Follow the actual state

SymptomWhat to check
Subscribed, but not in the listWhether the Steam download is complete and whether the game was launched from the full release; when Workshop loading is unavailable, the loader only reads local packages. Whether the manual package retains the complete directory and manifest, and whether all listed DLLs exist.
Enabled, but no change in functionalityChanging enablement or order marks a restart as required; restart and then check according to that mod's own trigger conditions, and do not treat "subscribed" as already running.
Workshop updated, but it still behaves like the old versionWhen a local copy with the same ID is read first, it can shadow the Workshop copy; check the entry's actual source, folder and version, and avoid keeping two copies with the same ID.
Missing dependencyCheck the corresponding package and its enabled state by the dependency ID in the details; a package with the same name but a different ID cannot substitute for it.
Settings gear unavailable, Home does nothingThe official settings button is only enabled for mods that have registered settings; shortcuts such as Home, F7 and F8 are determined by the specific mod, and there is no unified Home menu.
Failed detection or cannot be enabledRecord the full prompt and the actual package source, then judge according to the table below; a single phrase "scan failed" cannot be used to derive a definite conclusion of an old version or malware.

Refusal versus capability confirmation

A missing DLL listed in the manifest, an unlisted DLL inside the package, a bundled library with the same name as a game assembly, an assembly that cannot be read, a hard rejection by the scanner, or actual use of a capability not declared in the manifest may all block enabling. When the prompt is "undeclared capability", the author needs to correct the correspondence between the manifest and the actual implementation; ticking an existing capability will not patch an incomplete package.

The other type is normal capability confirmation. When a capability is declared in the manifest and has not been verified by the developer list, the loader may ask the user to confirm:

CapabilityMeaning of the prompt
File accessCan read and write local files.
Network accessCan access the internet.
Launch programsCan launch other programs or open links.
Dynamic codeCan load or generate code at runtime.
Native callsCan call system native libraries.
External reflectionCan access system or engine internals through reflection.

Capability confirmation indicates what the mod requests to do; it does not equal Windows administrator privileges, nor does it mean it has passed security certification. When deciding whether to use it, compare the author, Workshop source, update notes and the full detection prompt. The fact that a development package can run does not mean the package released to players has passed checks.

Report useful details

Include the following information in feedback:

  • Game App ID and Build number.
  • Mod name, ID, version and source link.
  • The dependency mods actually enabled.
  • The full prompt text, and the Player.log from this run.

The log directory for the Windows full release is %USERPROFILE%\AppData\LocalLow\Questing Goose Studio\Probably Stolen. When you see "not in the list", "scan rejected" or "loaded successfully but functionality does not work", describe them separately so that different stages can be located.

Source: full release 2026-10-29, Steam Build 26284217. Statically checked against the current built-in loader, mod interface and capability definitions; it does not mean that any third-party mod has passed compatibility or security acceptance.

Comments

0

Loading comments…