modwright 0.1.0

package/knowledge/subnautica2/ue5.ue4ss.yaml

@@ -0,0 +1,203 @@
+game: subnautica2
+topic: ue5.ue4ss
+title: UE4SS — the Unreal Engine scripting loader, its layout and its version problem
+facts:
+  - id: subnautica2.ue4ss.live-repo-vs-archived-original
+    claim: The live UE4SS project is `UE4SS-RE/RE-UE4SS`. The similarly-named `ue4ss/ue4ss` is the
+      ARCHIVED original (archived 2023-01-02, last release 1.3.5, maximum UE 5.0) and must not be
+      cited or linked.
+    status: community
+    source: https://github.com/UE4SS-RE/RE-UE4SS and https://github.com/ue4ss/ue4ss (archive banner and
+      final release), read 2026-09-11
+    tags:
+      - ue4ss
+      - repo
+      - provenance
+      - archived
+      - generic
+    detail: Worth recording because the archived repo still ranks in search results and its
+      documentation describes an installation layout three major versions out of date.
+  - id: subnautica2.ue4ss.ue56-only-in-experimental
+    claim: UE 5.6 support exists ONLY in UE4SS's rolling `experimental-latest` prerelease. The latest
+      tagged stable, v3.0.1 (2025-02-14), descends from v3.0.0, whose notes claim support only for
+      UE 5.2 and 5.3. There has been no tagged stable release in roughly nineteen months.
+    status: community
+    source: https://github.com/UE4SS-RE/RE-UE4SS/releases/tag/experimental-latest (notes list, as
+      separate bullets, added support for UE 5.4, 5.5, 5.6, 5.7 and 5.8; last rebuilt 2026-09-11)
+      and https://github.com/UE4SS-RE/RE-UE4SS/releases/tag/v3.0.1, both read 2026-09-11
+    tags:
+      - ue4ss
+      - version
+      - ue5.6
+      - experimental
+      - compat
+      - generic
+      - blocker
+    detail: 'This is the single most consequential fact for any UE 5.4+ game. It has an awkward
+      consequence for a compat rule table: `experimental-latest` is a moving target under a fixed
+      tag, so there is no version to pin a `VersionRequirement` against. Model it as an `advisory:
+      true` rule with empty `requires` that fires whenever UE4SS is present — per
+      src/core/compat/types.ts, advisories exist for exactly this, "a standing reminder that should
+      show up whenever a component is present at all". A user who installed the stable release on a
+      5.6 game has a loader that cannot work, and no version comparison would have told them.'
+  - id: subnautica2.ue4ss.install-layout-stable-vs-experimental
+    claim: "The two UE4SS lines install differently. Stable 3.0.x puts `dwmapi.dll`, `UE4SS.dll`,
+      `UE4SS-settings.ini` and `Mods/` all directly in the game's `Binaries/Win64/`. Experimental
+      moves everything except the proxy DLL into a `ue4ss` subfolder: `Binaries/Win64/dwmapi.dll`
+      plus `Binaries/Win64/ue4ss/{UE4SS.dll, UE4SS-settings.ini, Mods/}`."
+    status: community
+    source: "Stable: https://docs.ue4ss.com/dev/installation-guide.html. Experimental, verbatim from the
+      release notes: \"All UE4SS files (including UE4SS.dll, settings, and mods) now reside in a
+      `ue4ss` subfolder next to your game executable. Only the proxy DLL (dwmapi.dll) remains in the
+      game's Win64 directory.\"
+      (https://github.com/UE4SS-RE/RE-UE4SS/releases/tag/experimental-latest). Both read
+      2026-09-11."
+    tags:
+      - ue4ss
+      - install
+      - layout
+      - paths
+      - modroot
+      - generic
+    detail: A surface must offer BOTH paths as candidates and report which exists rather than assuming,
+      since the choice of path is really a choice of UE4SS line. `dwmapi.dll` became the proxy DLL
+      in v3.0.0, replacing `xinput1_3.dll`; the docs note the proxy can be "a name of any DLL that
+      is loaded by the game engine or by its dependencies", so its name is not a reliable detection
+      key on its own.
+  - id: subnautica2.ue4ss.mod-folder-and-mods-txt
+    claim: "A UE4SS mod is one directory under `Mods/`, with `Scripts/main.lua` for a Lua mod and/or
+      `dlls/main.dll` for a C++ mod. Enablement is `Mods/mods.txt`, one `ModName : 1` line per mod
+      (1 enabled, 0 disabled); an `enabled.txt` file inside a mod folder is an alternative marker."
+    status: community
+    source: "https://docs.ue4ss.com/dev/installation-guide.html (folder tree) and
+      https://docs.ue4ss.com/dev/guides/creating-a-lua-mod.html (the verbatim `MyLuaMod : 1` line
+      and the `Mods\\MyLuaMod\\scripts\\main.lua` tree), read 2026-09-11"
+    tags:
+      - ue4ss
+      - mods
+      - modstxt
+      - loadorder
+      - lua
+      - generic
+    detail: "`mods.txt` is a genuine load-order file in the `plugins.txt` mould — ordered, one name per
+      line, with an enabled flag — and each entry resolves to a real directory under the same root,
+      so a surface can set `modId` on every entry with confidence. Note the docs are inconsistent
+      about the case of the scripts subfolder (`Scripts` in the install guide, `scripts` in the mod
+      guide); it is case-insensitive on Windows. The precedence of `enabled.txt` relative to
+      `mods.txt` is not spelled out anywhere in the docs — a mod directory present but listed in
+      neither is the most common cause of a mod silently doing nothing."
+  - id: subnautica2.ue4ss.usmap-dumper-keybind
+    claim: "UE4SS can generate the `.usmap` mappings file a UE5 game needs for external asset tooling:
+      the Dumpers feature writes `Mappings.usmap` next to the `*-Shipping.exe`, bound to `Ctrl +
+      Numpad 6`."
+    status: community
+    source: https://docs.ue4ss.com/dev/feature-overview/dumpers.html, read 2026-09-11
+    tags:
+      - ue4ss
+      - usmap
+      - mappings
+      - dumper
+      - tooling
+      - generic
+    detail: 'Verbatim from the page: "By default the dump includes Blueprint-generated classes, structs
+      and enums in addition to native types." The other dumpers are UHT-compatible headers (`CTRL +
+      Numpad 9`), a C++ header generator (`CTRL + H`), `.umap` recreation (`Ctrl + Numpad 7`) and
+      `DumpAllObjects()` → `UE4SS_ObjectDump.txt` (`CTRL + J`). This matters beyond UE4SS itself:
+      generating mappings requires running a dumper against the LIVE process, which is why no
+      asset-level tooling can be built or tested without the game installed
+      (subnautica2.ue5.usmap-requires-a-running-game).'
+  - id: subnautica2.ue4ss.per-game-config-files
+    claim: Games that "have altered the engine in ways that make UE4SS not work out of the box" get a
+      `Binaries/Win64/CustomGameConfigs/<GameName>/` folder holding `UE4SS-settings.ini`,
+      `MemberVariableLayout.ini` (struct offsets), `VTableLayout.ini` (vtable index overrides) and
+      `UE4SS_Signatures/*.lua` (AOB signatures for `FName::FName`, `FName::ToString` and
+      `StaticConstructObject`).
+    status: community
+    source: https://docs.ue4ss.com/dev/custom-game-configs.html and
+      https://github.com/UE4SS-RE/RE-UE4SS/blob/main/docs/custom-game-configs.md, read 2026-09-11
+    tags:
+      - ue4ss
+      - offsets
+      - aob
+      - signatures
+      - per-game
+      - config
+      - generic
+    detail: There is NO `VersionDefinitions` file and no per-game `Config.ini` in current RE-UE4SS; that
+      naming is stale and circulates widely. The need for hand-written AOB signatures dropped
+      sharply in v3.0.0, which replaced the built-in address scans with `patternsleuth`
+      (https://github.com/UE4SS-RE/RE-UE4SS/releases/tag/v3.0.0). A game needing no
+      CustomGameConfigs entry is the normal case now, not the exception.
+  - id: subnautica2.ue4ss.logicmods-blueprint-path
+    claim: UE4SS's bundled `BPModLoaderMod` loads blueprint mods from the game's
+      `Content/Paks/LogicMods/` directory; the pak's name must match the mod folder name used in the
+      editor, and the pak must contain a `ModActor` asset.
+    status: community
+    source: Community-documented, not on docs.ue4ss.com — the official page
+      (https://docs.ue4ss.com/dev/feature-overview/blueprint-modloader.html) is a stub pointing at a
+      video. Path and ModActor requirement from downstream modding wikis, e.g.
+      https://pwmodding.wiki/docs/developers/ue4ss-modding/logic-mods/introduction. Read 2026-09-11.
+    tags:
+      - ue4ss
+      - logicmods
+      - blueprint
+      - pak
+      - modloader
+      - generic
+      - community
+    detail: "Independently corroborated for at least one game by Nexus Mods' own Vortex extension, which
+      routes \"LogicMods\" to `Content/Paks/LogicMods/`
+      (https://github.com/Nexus-Mods/game-subnautica2). Note that the per-game shape can differ from
+      the generic description: Subnautica 2's modkit requires a FOLDER per mod inside LogicMods
+      holding the full IoStore triplet, not a bare `.pak`
+      (subnautica2.modding.logicmods-is-folder-per-mod)."
+  - id: subnautica2.ue4ss.log-and-console
+    claim: "UE4SS writes `UE4SS.log` beside its DLL, and exposes a console and a GUI console configured
+      in `UE4SS-settings.ini` under `[Debug]`: `ConsoleEnabled`, `GuiConsoleEnabled`,
+      `GuiConsoleVisible`, `GraphicsAPI` (default `opengl`; `dx11`/`d3d11` also valid) and
+      `ToggleGuiKey=O` with CTRL."
+    status: community
+    source: https://github.com/UE4SS-RE/RE-UE4SS/blob/main/assets/UE4SS-settings.ini and
+      https://docs.ue4ss.com, read 2026-09-11
+    tags:
+      - ue4ss
+      - log
+      - console
+      - settings
+      - triage
+      - generic
+    detail: "`UE4SS.log` is a natural second log source for a UE game's surface alongside the engine's
+      own `Saved/Logs` file, and is the log-line fallback transport a ModWright bridge would use if
+      file writes fail. The docs advise setting both GUI console keys to 0 for play because the GUI
+      console \"will severely impact game performance\". Other settings worth knowing: `[Overrides]
+      ModsFolderPath` / `ModsFolderPaths` relocate the Mods directory (so the mod root is not
+      guaranteed to be the default path), and `[General] EnableHotReloadSystem=1` with
+      `HotReloadKey=R` hot-reloads LUA mods only — nothing in the pak or IoStore path hot-reloads."
+  - id: subnautica2.ue4ss.shared-folder-and-enabled-txt
+    claim: "Not every folder under UE4SS's `Mods/` is a mod: `shared` is the shared Lua library a build
+      ships with, and a tool walking `Mods/` must exempt it rather than report it as a mod with no
+      entry point. Neither the Lua-mod guide nor the installation guide mentions `enabled.txt` at
+      all — the docs' only enablement mechanism is the `ModName : 1` line in `mods.txt`."
+    status: community
+    source: https://docs.ue4ss.com/dev/guides/creating-a-lua-mod.html — verbatim, "Make sure that your
+      build of UE4SS contains `Mods\shared\Types.lua` (a development build from Github releases
+      contains it)", and the enablement passage "The mod must be added and enabled in
+      `Mods\mods.txt` with a new line containing the name of your mod folder ... and `1` for
+      enabling or `0` for disabling the mod"; read 2026-09-11 together with
+      https://docs.ue4ss.com/dev/installation-guide.html, neither of which names enabled.txt
+    tags:
+      - ue4ss
+      - mods
+      - shared
+      - main.lua
+      - mods.txt
+      - enabled.txt
+      - validator
+    detail: "`subnautica2.ue4ss.mod-shape` exempts `shared`, accepts either entry point
+      (`scripts/main.lua` or `dlls/main.dll`, matched case-insensitively because the two doc pages
+      disagree on the case of `scripts` — see `subnautica2.ue4ss.mod-folder-and-mods-txt`), and
+      treats an `enabled.txt` as enabling a folder that mods.txt does not name, since ModWright
+      research recorded that convention; the docs do not back it, so if a real UE4SS build ignores
+      `enabled.txt` the rule's \"will not load\" warning is the one to revisit."
+    related:
+      - subnautica2.ue4ss.mod-folder-and-mods-txt

package/knowledge/valheim/bepinex.loader.yaml

@@ -0,0 +1,247 @@
+game: valheim
+topic: bepinex.loader
+title: BepInEx 5 as Valheim's plugin loader — folder layout, Doorstop, and the exact LogOutput.log
+  line formats
+facts:
+  - id: valheim.bepinex.loader.folder-layout
+    claim: "A BepInEx install creates five folders under `BepInEx/`: `core` (the framework assemblies),
+      `plugins` (user plugins), `config` (per-plugin `.cfg` files), `patchers` (preloader patcher
+      plugins) and `cache`."
+    status: community
+    source: https://docs.bepinex.dev/articles/user_guide/installation/index.html
+    tags:
+      - bepinex
+      - layout
+      - plugins
+      - config
+      - patchers
+      - modroots
+    detail: "These map onto four distinct ModWright mod roots with different rules: `plugins` is
+      directory- or file-delimited and isolated, `config` is a merged tree of shared text files,
+      `patchers` is a separate load stage that runs before any plugin, and `cache` is derived state
+      that must never be deployed to."
+  - id: valheim.bepinex.loader.doorstop-files-beside-the-exe
+    claim: "On Windows x64 the loader is three files placed next to the game executable, not inside
+      `BepInEx/`: `winhttp.dll` (the Doorstop loader DLL), `doorstop_config.ini` and
+      `.doorstop_version`. On Linux and macOS the equivalent is a `run_bepinex.sh` script that must
+      be edited to name the executable and then made executable with `chmod u+x`."
+    status: community
+    source: https://docs.bepinex.dev/articles/user_guide/installation/index.html
+    tags:
+      - bepinex
+      - doorstop
+      - winhttp
+      - install
+      - detect
+    detail: Presence of `winhttp.dll` plus `doorstop_config.ini` in the game root is the cheapest "is
+      BepInEx installed at all" check available, and it needs no launch. It is also the check that
+      distinguishes a game-directory install from an r2modman profile install, where the same three
+      files live in the profile instead.
+  - id: valheim.bepinex.loader.doorstop-config-keys-renamed-at-5-4-23
+    claim: "`doorstop_config.ini`'s section and key names are not stable across BepInEx 5: up to 5.4.22
+      the file is `[UnityDoorstop]` with camelCase keys (`enabled`, `targetAssembly`,
+      `redirectOutputLog`, `ignoreDisableSwitch`, `dllSearchPathOverride`), and from 5.4.23 on it is
+      `[General]` + `[UnityMono]` with snake_case keys (`enabled`, `target_assembly`,
+      `redirect_output_log`, `boot_config_override`, `ignore_disable_switch`,
+      `dll_search_path_override`, `debug_enabled`, `debug_address`, `debug_suspend`)."
+    status: inferred
+    source: BepInEx `doorstop/doorstop_config.ini` at tags v5.4.22 and v5-lts / v5.4.23.5; the 5.4.23.2
+      release notes state it outright — "Settings in `doorstop_config.ini` were renamed, old config
+      files will no longer work" (https://github.com/BepInEx/BepInEx/releases/tag/v5.4.23.2)
+    tags:
+      - doorstop
+      - config
+      - ini
+      - version
+      - detect
+      - parser
+    detail: Both spellings are still in the wild, so a detector that greps for `target_assembly` alone
+      will silently fail to recognise an older install, and one that greps for `targetAssembly` will
+      fail on every current one. The value's whitespace is also inconsistent inside BepInEx's own
+      shipped file (`enabled = true` but `target_assembly=BepInEx\core\...`), so a parser must
+      tolerate optional spaces around `=`.
+  - id: valheim.bepinex.loader.logoutput-path-and-recreation
+    claim: BepInEx's `DiskLogListener` writes `LogOutput.log` into the BepInEx root
+      (`BepInEx/LogOutput.log`) and opens it with `FileMode.Create` unless the `AppendLog` config is
+      on — so by default the file is truncated and rewritten on every launch rather than appended
+      to.
+    status: inferred
+    source: "BepInEx v5-lts `BepInEx/Logging/DiskLogListener.cs` (the constructor's
+      `Path.Combine(Paths.BepInExRootPath, localPath)` and `appendLog ? FileMode.Append :
+      FileMode.Create`), and `BepInEx/Bootstrap/Chainloader.cs` which constructs it as `new
+      DiskLogListener(\"LogOutput.log\", ...)`"
+    tags:
+      - bepinex
+      - logoutput
+      - log
+      - run-scope
+      - truncation
+    detail: 'Good news for `core/logs` run scoping: one file per run means a plain whole-file read is
+      already run-scoped, with none of the Cyberpunk redscript `rCURRENT` in-place-truncation trap.
+      The Valheim-Modding wiki states the same behaviour in prose — the log "will be re-generated on
+      a successful startup by default".'
+  - id: valheim.bepinex.loader.logoutput-fallback-filenames
+    claim: If `LogOutput.log` cannot be opened for writing, BepInEx retries up to five times under the
+      names `LogOutput.log.1`, `LogOutput.log.2` and so on, and only then logs "Couldn't open a log
+      file for writing. Skipping log file creation" and gives up.
+    status: inferred
+    source: BepInEx v5-lts `BepInEx/Logging/DiskLogListener.cs`, the `while
+      (!Utility.TryOpenFileStream(...))` loop
+    tags:
+      - bepinex
+      - logoutput
+      - log
+      - candidates
+      - failure-mode
+    detail: "A log source for Valheim must therefore declare candidates, not one path: an antivirus or a
+      second running instance holding the handle silently moves the log to a numbered sibling. The
+      wiki's Bitdefender note is a real report of exactly this class of problem."
+  - id: valheim.bepinex.loader.log-line-format
+    claim: Every disk log line is formatted by `LogEventArgs.ToString()` as
+      `$"[{Level,-7}:{Source.SourceName,10}] {Data}"` — an opening bracket, the log level
+      left-aligned and space-padded to 7 characters, a colon, the source name right-aligned and
+      space-padded to 10 characters, a closing bracket, one space, then the message. There is no
+      timestamp.
+    status: inferred
+    source: BepInEx v5-lts `BepInEx/Logging/LogEventArgs.cs`, `ToString()`; written by
+      `DiskLogListener.LogEvent` via `LogWriter.WriteLine(eventArgs.ToString())`
+    tags:
+      - bepinex
+      - log
+      - format
+      - signature
+      - regex
+    detail: "Concretely, `[Info   :   BepInEx] ...`, `[Warning: HarmonyX] ...`, `[Error  : Unity Log]
+      ...`. Two consequences for `logSignatures`: a pattern must tolerate variable internal
+      whitespace on both sides of the colon (the padding depends on the length of the level and
+      source names, and a source name longer than 10 characters is not truncated), and **there is no
+      timestamp**, so `RunScope.since` can never be applied line-by-line for this source —
+      `SourceStatus.timestamps` will be false and scoping must fall back to file mtime plus the
+      per-run truncation above."
+  - id: valheim.bepinex.loader.preloader-banner-lines
+    claim: "The preloader writes a fixed banner at the top of every run, in order: `BepInEx <version> -
+      <ProcessName> (<exe last write time>)`, then `Running under Unity v<version>`, `CLR runtime
+      version: <version>`, `Supports SRE: <bool>`, `System platform: <platform>`, then `Preloader
+      started`, `Loaded 1 patcher method from [BepInEx.Preloader <version>]`, `<N> patcher plugin(s)
+      loaded` and `Preloader finished`."
+    status: inferred
+    source: BepInEx v5-lts `BepInEx.Preloader/Preloader.cs`, the `Logger.LogMessage` / `Logger.LogInfo`
+      calls in `Run()`
+    tags:
+      - bepinex
+      - log
+      - banner
+      - version
+      - compat
+      - signature
+    detail: These four version numbers — BepInEx's own, the game exe's, the CLR's and (from the
+      chainloader, below) the detected Unity version — are the whole raw material for a Valheim
+      `compat` surface, and all four are readable from the log with no launch beyond the first.
+  - id: valheim.bepinex.loader.unity-version-is-the-exe-file-version
+    claim: "BepInEx's \"Running under Unity v...\" line does not read a Unity marker file:
+      `Preloader.GetUnityVersion()` returns
+      `FileVersionInfo.GetVersionInfo(Paths.ExecutablePath).FileVersion`, i.e. the PE FileVersion of
+      the game executable itself."
+    status: inferred
+    source: BepInEx v5-lts `BepInEx.Preloader/Preloader.cs`, `GetUnityVersion()`
+    tags:
+      - bepinex
+      - unity
+      - version
+      - pe
+      - compat
+      - detect
+    detail: ModWright already has `core/compat/pe.ts` `readPeFileVersion`, so a Valheim surface can
+      report the same number BepInEx reports without the game ever having been launched, by reading
+      `valheim.exe` directly. Treat it as the Unity player version axis, distinct from Iron Gate's
+      own `1.0.12`-style marketing version.
+  - id: valheim.bepinex.loader.chainloader-lines
+    claim: "The chainloader's own lines are `Detected Unity version: v<version>`, `Chainloader ready`,
+      `Chainloader started`, `<N> plugin(s) to load`, one `Loading [<Name> <Version>]` per plugin,
+      and finally `Chainloader startup complete`."
+    status: inferred
+    source: BepInEx v5-lts `BepInEx/Bootstrap/Chainloader.cs` (`Logger.LogMessage` and `Logger.LogInfo`
+      calls) with `PluginInfo.ToString()` defined in `BepInEx/Contract/PluginInfo.cs` as
+      `$"{Metadata?.Name} {Metadata?.Version}"`
+    tags:
+      - bepinex
+      - log
+      - chainloader
+      - plugin-loaded
+      - signature
+      - success
+    detail: "`Loading [Jotunn 2.26.0]` is the canonical per-plugin success line, and it carries name and
+      version but **not** GUID — so a log-derived inventory is keyed on the human-facing `Name` from
+      `[BepInPlugin]`, which is explicitly allowed to change between versions. Absence of
+      `Chainloader startup complete` at the end of a run is the signal that something aborted
+      mid-load."
+  - id: valheim.bepinex.loader.bepinex-cfg-keys
+    claim: Disk logging is controlled by `BepInEx/config/BepInEx.cfg` section `[Logging.Disk]` with keys
+      `Enabled` (default true), `AppendLog` (default false), `LogLevels` (default Fatal, Error,
+      Message, Info, Warning — note Debug is excluded) and `WriteUnityLog` (default false);
+      `[Logging]` `UnityLogListening` (default true) and `[Chainloader]` `HideManagerGameObject`
+      (default false) are the other two that matter.
+    status: inferred
+    source: BepInEx v5-lts `BepInEx/Bootstrap/Chainloader.cs`, the `ConfigFile.CoreConfig.Bind(...)`
+      declarations at the end of the file
+    tags:
+      - bepinex
+      - config
+      - bepinex-cfg
+      - logging
+      - explain-missing
+    detail: "`[Logging.Disk] Enabled = false` is exactly the kind of reason `GameSurface.explainMissing`
+      exists for: it turns a missing `LogOutput.log` from \"the loader never ran\" into \"logging is
+      switched off\", and those two demand opposite next actions. `WriteUnityLog = false` by default
+      also means the game's own Unity exceptions are in `Player.log` and not in `LogOutput.log`
+      unless someone turned it on."
+  - id: valheim.bepinex.loader.bepinexpack-valheim-is-the-distribution
+    claim: "Valheim does not use a stock BepInEx build: the community standard is
+      `denikson/BepInExPack_Valheim` on Thunderstore, currently version `5.4.2350`, which ships a
+      preconfigured `BepInEx.cfg` with the console enabled and the correct Valheim entry point,
+      Linux run scripts, an edited preloader, a forced `isModded` flag and support for semantic
+      versioning in plugin versions."
+    status: community
+    source: https://thunderstore.io/c/valheim/p/denikson/BepInExPack_Valheim/
+    tags:
+      - bepinex
+      - bepinexpack
+      - thunderstore
+      - version
+      - ismodded
+      - console
+    detail: Two consequences. The pack's version (`5.4.2350`) is not a stock BepInEx version number, so
+      a compat rule comparing it against BepInEx's own releases will read as nonsense — it must be
+      treated as its own component with its own axis. And the forced `isModded` flag means a BepInEx
+      install changes how the game advertises itself on the server list, which is a user-visible
+      side effect of merely installing the loader.
+  - id: valheim.bepinexpack-valheim-install-shape
+    claim: "Manual installation of BepInExPack_Valheim is: extract the archive, then copy the *contents*
+      of the inner `BepInExPack_Valheim` folder into the Valheim game directory, after which
+      `BepInEx`, `winhttp.dll` and `doorstop_config.ini` sit in the game root."
+    status: community
+    source: https://thunderstore.io/c/valheim/p/denikson/BepInExPack_Valheim/
+    tags:
+      - bepinex
+      - install
+      - doorstop
+      - winhttp
+      - detect
+    detail: "The nested-folder step is the single most common manual-install mistake: copying the
+      archive's top folder instead of its contents produces
+      `Valheim/BepInExPack_Valheim/BepInEx/...`, where Doorstop never loads and no log is ever
+      written."
+  - id: valheim.bepinex.loader.console-and-plugins-loaded-indicator
+    claim: With the Valheim pack's default config a BepInEx console window opens alongside the game, and
+      the in-game confirmation that plugins loaded is a "Plugins Loaded" message at the top left of
+      the main menu.
+    status: community
+    source: https://github.com/Valheim-Modding/Wiki/wiki/Client-Troubleshooting
+    tags:
+      - bepinex
+      - console
+      - main-menu
+      - plugins-loaded
+      - verification
+    detail: "This is the cheapest attended verification step for a test run: it needs the main menu
+      only, no save, no character."