[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F7JTXFADPRH4CDV9PNH1EC":3,"skill-same:01M7F7JTXFADPRH4CDV9PNH1EC":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M7F7JTXFADPRH4CDV9PNH1EC","researching-bgs-mod-internals",null,"Use when asked how a BGS mod works internally.","chaorenex1\u002Fhermes-home-content","chaorenex1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F23194925?v=4","01M7F5NA1D1D02R2MEMYQN2NZT","chan chan","01M7F5NA20KTHMTY2015CYM1TZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fresearching-bgs-mod-internals\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\r\nname: researching-bgs-mod-internals\r\ndescription: Use when asked how a BGS mod works internally.\r\nversion: 1.1.0\r\nauthor: Hermes Agent\r\nlicense: MIT\r\nmetadata:\r\n  hermes:\r\n    tags: [bgs-modding, research, source-analysis, mod-internals]\r\n    related_skills: [diagnosing-bgs-problems, evaluating-bgs-mods, archify]\r\n---\r\n\r\n# Researching BGS Mod Internals\r\n\r\n## When to Use\r\n\r\nUse when the user asks how a Bethesda mod or framework works internally: \"研究一下X原理\", \"how does this mod work\", \"why is it faster\", \"这个框架怎么实现的\", \"what does this setting actually do\".\r\n\r\nNot for inclusion verdicts (use `evaluating-bgs-mods`) or symptoms (use `diagnosing-bgs-problems`).\r\n\r\nThe mod page is a claim; the source is evidence. Version, requirements, and author intent come from Nexus; behavior comes from a pinned commit of the authoritative repository, or, when the uploader ships no repository, from the distributed DLL itself. A DLL\u002Fframework mod is an engine, so explain the layer boundary first: what it computes, what content mods supply, and which layer a user-facing problem belongs to.\r\n\r\n## Procedure\r\n\r\n1. Query the KB first for engine\u002Fframework facts about the current game. If the pack has no record, say `[GAP]` and continue with source evidence.\r\n2. Read the Nexus page for version, uploader, requirements, and the Source Code spoiler. Descriptions sell behavior and routinely omit architecture; never build the explanation from them alone.\r\n3. Resolve the authoritative repo and its fork chain. Framework DLLs are usually forks of forks; the repo linked by the current uploader wins. Record `git rev-parse HEAD` and the credential-free origin. No repo and no source spoiler means step 4b, not a description-based answer.\r\n4. Clone shallow into the scratch directory (`git clone --depth 1 \u003Curl>`), then pin `git log -1 --format='%H %ad %s'`. Read files from disk; do not page source through a web extractor.\r\n4b. Closed-source plugin: download the archive, record the archive hash and entry sizes, then recover the design from the binary (build-provenance strings, string table, hook sites, and the IDs\u002Foffsets each site uses). Full recipe in `references\u002Fdll-static-reverse-engineering.md`. Map every recovered numeric ID onto CommonLibSSE-NG before naming anything: clone the framework at a pinned commit and grep the ID under `include\u002FRE\u002F`; class headers carry member offsets as `\u002F\u002F 0xNN` and `Offsets_VTABLE.h` carries the `VTABLE_*` variant IDs.\r\n5. Map before reading: directory tree, file sizes, entry point (SKSE `main.cpp` \u002F hooks), frame loop, domain core, and config parser. Read that connected slice instead of the whole tree.\r\n6. Trace one frame end to end and write down thread, stage, input, output for each step. That skeleton is the answer; details hang off it.\r\n7. Verify every quantitative claim in source: solver constants, caps, timestep defaults. Grep build presets before crediting an ISA path (`#ifdef AVX2` code is dead unless a preset passes `\u002Farch:AVX2`). Grep for a capability before denying it (`grep -ri cuda`) rather than trusting a leftover comment.\r\n8. Separate engine from content: physics\u002Fanimation\u002Fskeleton frameworks provide the runtime; XML, NIF, and ESP files supplied by content mods are a different layer. State which layer owns the behavior a user is asking about.\r\n9. Deliver in this order: what it is not, data model, per-frame pipeline, cost model (why it is fast), hard limits, practical knobs. Cite repository-relative paths with line ranges.\r\n10. When the conclusion has structure, produce one archify diagram and keep the prose numbers identical to it.\r\n\r\n## Pitfalls\r\n\r\n- Do not explain a fork by its ancestor's README. Check whether the current code still uses the ancestor's solver or replaced it.\r\n- Comments are not features. An extension-point comment or an unbuilt `#ifdef` branch does not ship in the DLL.\r\n- Do not repeat marketing performance claims. Derive the cost model from what the code skips (culling, parallelism, caching) and from its hard caps.\r\n- \"Soft\" behavior may not come from simulating the mesh at all. Find what is actually integrated before explaining softness, jiggle, or stiffness.\r\n- If neither a repository nor an inspectable binary is available, mark the explanation as description-based `[unverified]`; do not present the mod page as architecture.\r\n- Read the runtime dispatch before trusting any constant table. `REL::Module::Runtime` is a bitmask (`AE = 1`, `SE = 2`, `VR = 4`), so a compare against `2` selects SE and `4` selects VR; assuming 1\u002F2\u002F3 ordering silently swaps every ID, vtable, and struct offset in the answer.\r\n- Confirm a struct identity by a layout fingerprint, not by one matching field. `ShadowSceneNode` on VR shifts every member by the documented `+0x28`; a candidate table that shifts by exactly that delta is the same object, while one landing on a plausible member proves nothing.\r\n- A vtable byte offset divided by pointer size is the slot index the framework comments use: on x64 `vtable + 0x150` is slot `0x2A`, which CommonLibSSE-NG names `BSShaderProperty::GetRenderPasses`. Never infer the method from its neighbouring slots.\r\n- Read the plugin's own pre-patch guards to learn the intended target: an opcode-byte check plus a callee-ID comparison names the hook target even when the engine function has no symbol. Cite that ID, and label any human-readable engine name as inference.\r\n- A fix that only writes engine render caches (per-object masks, per-pass arrays) is safe to add and remove because it never touches records or saves; say that explicitly instead of implying the plugin rewrites the renderer.\r\n\r\n## Output conventions\r\n\r\n- Reply in the user's language; keep file names, API names, console commands, and numeric constants verbatim.\r\n- Lead with the one-sentence mechanism, then the layered explanation; do not open with history.\r\n- Distinguish verified source facts from inference; label anything not exercised or read.\r\n\r\n## See also\r\n\r\n- `references\u002Ffsmp-physics-pipeline.md` — worked example: Faster HDT-SMP data model, frame pipeline, collision limits, and tuning map.\r\n- `references\u002Fdll-static-reverse-engineering.md` — no-source plugin: PE\u002Fcapstone procedure, string-to-function xref, and mapping recovered IDs onto CommonLibSSE-NG headers.\r\n- `diagnosing-bgs-problems` — when the question is a symptom rather than a mechanism.\r\n- `archify` — pipeline or architecture diagram for the explanation.\r\n","# Researching BGS Mod Internals\r\n\r\n## When to Use\r\n\r\nUse when the user asks how a Bethesda mod or framework works internally: \"研究一下X原理\", \"how does this mod work\", \"why is it faster\", \"这个框架怎么实现的\", \"what does this setting actually do\".\r\n\r\nNot for inclusion verdicts (use `evaluating-bgs-mods`) or symptoms (use `diagnosing-bgs-problems`).\r\n\r\nThe mod page is a claim; the source is evidence. Version, requirements, and author intent come from Nexus; behavior comes from a pinned commit of the authoritative repository, or, when the uploader ships no repository, from the distributed DLL itself. A DLL\u002Fframework mod is an engine, so explain the layer boundary first: what it computes, what content mods supply, and which layer a user-facing problem belongs to.\r\n\r\n## Procedure\r\n\r\n1. Query the KB first for engine\u002Fframework facts about the current game. If the pack has no record, say `[GAP]` and continue with source evidence.\r\n2. Read the Nexus page for version, uploader, requirements, and the Source Code spoiler. Descriptions sell behavior and routinely omit architecture; never build the explanation from them alone.\r\n3. Resolve the authoritative repo and its fork chain. Framework DLLs are usually forks of forks; the repo linked by the current uploader wins. Record `git rev-parse HEAD` and the credential-free origin. No repo and no source spoiler means step 4b, not a description-based answer.\r\n4. Clone shallow into the scratch directory (`git clone --depth 1 \u003Curl>`), then pin `git log -1 --format='%H %ad %s'`. Read files from disk; do not page source through a web extractor.\r\n4b. Closed-source plugin: download the archive, record the archive hash and entry sizes, then recover the design from the binary (build-provenance strings, string table, hook sites, and the IDs\u002Foffsets each site uses). Full recipe in `references\u002Fdll-static-reverse-engineering.md`. Map every recovered numeric ID onto CommonLibSSE-NG before naming anything: clone the framework at a pinned commit and grep the ID under `include\u002FRE\u002F`; class headers carry member offsets as `\u002F\u002F 0xNN` and `Offsets_VTABLE.h` carries the `VTABLE_*` variant IDs.\r\n5. Map before reading: directory tree, file sizes, entry point (SKSE `main.cpp` \u002F hooks), frame loop, domain core, and config parser. Read that connected slice instead of the whole tree.\r\n6. Trace one frame end to end and write down thread, stage, input, output for each step. That skeleton is the answer; details hang off it.\r\n7. Verify every quantitative claim in source: solver constants, caps, timestep defaults. Grep build presets before crediting an ISA path (`#ifdef AVX2` code is dead unless a preset passes `\u002Farch:AVX2`). Grep for a capability before denying it (`grep -ri cuda`) rather than trusting a leftover comment.\r\n8. Separate engine from content: physics\u002Fanimation\u002Fskeleton frameworks provide the runtime; XML, NIF, and ESP files supplied by content mods are a different layer. State which layer owns the behavior a user is asking about.\r\n9. Deliver in this order: what it is not, data model, per-frame pipeline, cost model (why it is fast), hard limits, practical knobs. Cite repository-relative paths with line ranges.\r\n10. When the conclusion has structure, produce one archify diagram and keep the prose numbers identical to it.\r\n\r\n## Pitfalls\r\n\r\n- Do not explain a fork by its ancestor's README. Check whether the current code still uses the ancestor's solver or replaced it.\r\n- Comments are not features. An extension-point comment or an unbuilt `#ifdef` branch does not ship in the DLL.\r\n- Do not repeat marketing performance claims. Derive the cost model from what the code skips (culling, parallelism, caching) and from its hard caps.\r\n- \"Soft\" behavior may not come from simulating the mesh at all. Find what is actually integrated before explaining softness, jiggle, or stiffness.\r\n- If neither a repository nor an inspectable binary is available, mark the explanation as description-based `[unverified]`; do not present the mod page as architecture.\r\n- Read the runtime dispatch before trusting any constant table. `REL::Module::Runtime` is a bitmask (`AE = 1`, `SE = 2`, `VR = 4`), so a compare against `2` selects SE and `4` selects VR; assuming 1\u002F2\u002F3 ordering silently swaps every ID, vtable, and struct offset in the answer.\r\n- Confirm a struct identity by a layout fingerprint, not by one matching field. `ShadowSceneNode` on VR shifts every member by the documented `+0x28`; a candidate table that shifts by exactly that delta is the same object, while one landing on a plausible member proves nothing.\r\n- A vtable byte offset divided by pointer size is the slot index the framework comments use: on x64 `vtable + 0x150` is slot `0x2A`, which CommonLibSSE-NG names `BSShaderProperty::GetRenderPasses`. Never infer the method from its neighbouring slots.\r\n- Read the plugin's own pre-patch guards to learn the intended target: an opcode-byte check plus a callee-ID comparison names the hook target even when the engine function has no symbol. Cite that ID, and label any human-readable engine name as inference.\r\n- A fix that only writes engine render caches (per-object masks, per-pass arrays) is safe to add and remove because it never touches records or saves; say that explicitly instead of implying the plugin rewrites the renderer.\r\n\r\n## Output conventions\r\n\r\n- Reply in the user's language; keep file names, API names, console commands, and numeric constants verbatim.\r\n- Lead with the one-sentence mechanism, then the layered explanation; do not open with history.\r\n- Distinguish verified source facts from inference; label anything not exercised or read.\r\n\r\n## See also\r\n\r\n- `references\u002Ffsmp-physics-pipeline.md` — worked example: Faster HDT-SMP data model, frame pipeline, collision limits, and tuning map.\r\n- `references\u002Fdll-static-reverse-engineering.md` — no-source plugin: PE\u002Fcapstone procedure, string-to-function xref, and mapping recovered IDs onto CommonLibSSE-NG headers.\r\n- `diagnosing-bgs-problems` — when the question is a symptom rather than a mechanism.\r\n- `archify` — pipeline or architecture diagram for the explanation.\r\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"description":7},"Hermes Agent","1.1.0",{"hermes":27},{"tags":28,"related_skills":33},[29,30,31,32],"bgs-modding","research","source-analysis","mod-internals",[34,35,36],"diagnosing-bgs-problems","evaluating-bgs-mods","archify","main","a3f3199bb87ec3c91248f68a39d88527e1847ae9","skills\u002Fresearching-bgs-mod-internals","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content","https:\u002F\u002Fgithub.com\u002Fchaorenex1","https:\u002F\u002Fblog.aduib.com","A programmer whose only hobby in life is coding","2026-10-20 00:34:32",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add chaorenex1\u002Fhermes-home-content --skill researching-bgs-mod-internals",{"tool":51,"command":52},"bunx","bunx skills add chaorenex1\u002Fhermes-home-content --skill researching-bgs-mod-internals",{"tool":54,"command":55},"pnpm","pnpm dlx skills add chaorenex1\u002Fhermes-home-content --skill researching-bgs-mod-internals","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fresearching-bgs-mod-internals\u002FSKILL.md",true,[59,65],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fdll-static-reverse-engineering.md","REFERENCE","参考文档",5046,"https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fresearching-bgs-mod-internals\u002Freferences\u002Fdll-static-reverse-engineering.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Ffsmp-physics-pipeline.md",6787,"https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fresearching-bgs-mod-internals\u002Freferences\u002Ffsmp-physics-pipeline.md",[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7F8GF32YD5MBQW2TGSRH1YP","web-retrieval-resilience","Web tools fail or search rules break: repair or fall back.","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fweb\u002Fweb-retrieval-resilience\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7F8FP46QESQMCZ1KBT3TW3R","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7F8ER6VXHBNVRQBZS7X08SE","verification-loop","Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS\u002FFAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7F8E4BQJ38KVQVM3MT20PYV","unreal-world-builder","开放世界与环境专家——精通 UE5 World Partition、Landscape、程序化植被、HLOD 和大规模关卡流式加载，打造无缝开放世界体验","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Funreal-engine\u002Funreal-world-builder\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7F8D747SQW2FTP7GBSX38BR","unreal-technical-artist","Unreal Engine 视觉管线专家——精通材质编辑器、Niagara 特效、程序化内容生成和 UE5 项目的美术到引擎管线","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Funreal-engine\u002Funreal-technical-artist\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7F8CKHYJVZVBTN0321J88T2","unreal-systems-engineer","性能与混合架构专家——精通 C++\u002FBlueprint 边界、Nanite 几何体、Lumen GI 和 Gameplay Ability System，面向 AAA 级 Unreal Engine 项目","https:\u002F\u002Fgithub.com\u002Fchaorenex1\u002Fhermes-home-content\u002Fblob\u002Fmain\u002Fskills\u002Funreal-engine\u002Funreal-systems-engineer\u002FSKILL.md",[],[]]