modwright 0.1.0

package/knowledge/cyberpunk2077/mesh.blender.yaml

@@ -0,0 +1,209 @@
+game: cyberpunk2077
+topic: mesh.blender
+title: blender mesh authoring and export for Cyberpunk 2077
+facts:
+  - id: cp2077.mesh.vertex-cap-65535
+    claim: The engine enforces a hard cap of 65,535 vertices per submesh; exceeding this produces a
+      silently invalid mesh that may render incompletely or fail to load.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vertex
+      - limit
+      - submesh
+      - cap
+      - rendering
+    detail: "The trigger was double-siding: the export script's comment reads \"gunmetal CANNOT be
+      doubled wholesale: 2x 47k verts exceeds the engine's 65535-per-submesh limit\". The fix was
+      NOT to split into more submeshes — only the black submesh is duplicated and normal-flipped (in
+      the exporter script), and inward-facing gunmetal faces are repaired at the source in Blender
+      instead."
+  - id: cp2077.mesh.join-by-material-submesh-order
+    claim: When exporting a kitbashed mesh with multiple materials, join geometry by material slot to
+      create fixed submesh indices; wolvenkit import expects submesh order to match the material
+      assignment sequence.
+    status: inferred
+    source: ModWright research
+    tags:
+      - mesh
+      - material
+      - submesh
+      - join
+      - export
+    detail: 'The current export produces FOUR submeshes, in this fixed order: submesh_00 gunmetal body,
+      submesh_01 red grip, submesh_02 ink lettering, submesh_03 black parts. The script comment
+      explains the ordering rule — "00..02 keep their old indices, black appends as 03 so existing
+      chunkMaterials stay valid" — and grouping is by MATERIAL, not object name, "so face-level
+      edits carry over". The earlier an earlier exporter produced three.'
+  - id: cp2077.mesh.glb-triangulation-required
+    claim: glb export from blender must have all faces triangulated; n-gons or quads produce invalid
+      mesh data at import time.
+    status: verified
+    source: ModWright field verification
+    tags:
+      - glb
+      - blender
+      - triangulation
+      - faces
+      - n-gons
+    detail: The export script triangulates every joined submesh with
+      bpy.ops.mesh.quads_convert_to_tris(quad_method='BEAUTY', ngon_method='BEAUTY') before export.
+      The sources state the requirement; the exact failure mode when it is skipped is not recorded,
+      so do not quote one. In-game verified_on/verified_by removed — this is a WolvenKit import
+      requirement, not an engine observation.
+  - id: cp2077.mesh.glb-tangent-vectors-required
+    claim: glb export must include tangent vectors baked for each vertex; missing tangents cause
+      incorrect normal mapping and lighting at import.
+    status: verified
+    source: ModWright field verification
+    tags:
+      - glb
+      - blender
+      - tangent
+      - normal-mapping
+      - export
+    detail: Tangents are requested explicitly in the glTF export call, not baked automatically by the
+      add-on. The lighting consequence in the claim is reasoning, not something the sources record.
+  - id: cp2077.mesh.glb-uv-layers-required
+    claim: glb export must include uv layers named correctly; missing or incorrectly named uv layers
+      cause material mapping failures.
+    status: verified
+    source: ModWright field verification
+    tags:
+      - glb
+      - uv
+      - blender
+      - layers
+      - material-mapping
+    detail: 'The exact requirement the script enforces: every mesh gets exactly ONE uv layer, named
+      UVMap (capital U, V, M). Meshes with none are smart-projected (angle_limit=1.15,
+      island_margin=0.02); extra layers are removed. The earlier version of this fact spelled the
+      layer "uvMap", which is wrong.'
+  - id: cp2077.mesh.cyberpunk-io-suite-exporter
+    claim: blender 5.1 with Cyberpunk IO Suite 2.0.0 add-on installed provides the export function for
+      glb files compatible with wolvenkit cli; the exporter handles triangulation, tangent baking,
+      and format conformance.
+    status: inferred
+    source: ModWright research
+    tags:
+      - blender
+      - cyberpunk-io-suite
+      - exporter
+      - glb
+      - add-on
+    detail: "Correction to the claim's second half: the export script does the triangulation, uv
+      normalisation and tangent request itself through plain bpy/glTF calls (the exporter script),
+      so those are not services of the add-on. What the add-on supplies is the import side for the
+      vanilla game meshes the kitbash is built from. build.ps1 -Export invokes blender --background
+      --python on the exporter script."
+  - id: cp2077.mesh.kitbash-donor-transfer
+    claim: When kitbashing (combining parts from multiple source meshes), preserve material assignments
+      and uv from donor meshes if possible; copying materials between donors can create mismatches
+      that require post-import fixing.
+    status: inferred
+    source: ModWright research
+    tags:
+      - kitbash
+      - material
+      - donor
+      - uv
+      - transfer
+    detail: One weapon mod's kitbash is imported over the Malorian 3516 mesh as donor, then materials
+      are reassigned by index with a mesh-materials script. Its notes record the resulting
+      chunkMaterials as [pasted__malorian_ml_base, malorian_ml_handle2 (red grip),
+      pasted__malorian_ml_base]. The "preserve if possible / mismatches need fixing" advice is the
+      author's generalisation.
+  - id: cp2077.mesh.material-pasting-convention
+    claim: When a material is copied from a donor mesh during kitbashing, it may be pasted with a
+      "pasted__" prefix in the name; these pasted materials are distinct from the original and allow
+      local overrides.
+    status: inferred
+    source: ModWright research
+    tags:
+      - material
+      - pasted
+      - naming
+      - convention
+      - override
+    detail: 'Only the names are sourced: pasted__malorian_ml_base for body/fittings and
+      malorian_ml_handle2 for the red grip. What the "pasted__" prefix means to the engine or to
+      WolvenKit is not stated anywhere in the sources; the "allows local overrides" reading is an
+      inference.'
+  - id: cp2077.mesh.chunk-materials-array-order
+    claim: The chunkMaterials array in a .mesh file specifies material assignments by index; the order
+      must match the submesh indices created during glb join-by-material.
+    status: inferred
+    source: ModWright research
+    tags:
+      - chunk
+      - material
+      - array
+      - index
+      - order
+    detail: One weapon mod's mesh-materials script keeps one appearance named "default" and writes three
+      chunkMaterials entries — index 0 pasted__malorian_ml_base, 1 malorian_ml_handle2, 2
+      pasted__malorian_ml_base — matching its three-submesh export script. A later four-submesh
+      export deliberately appends black as index 03 "so existing chunkMaterials stay valid", and the
+      shipped mod adds its own materials (mod\<mod>\materials\blackmetal.mi, <mod>_gunmetal.mi).
+  - id: cp2077.mesh.serialize-edit-deserialize-pattern
+    claim: "Complex mesh edits (material reassignment, submesh tweaks) are performed via: cli serialize
+      (binary to json) → Python script edit → cli deserialize (json to binary). This allows
+      programmatic mesh modification without gui interaction."
+    status: verified
+    source: ModWright field verification
+    tags:
+      - serialize
+      - deserialize
+      - mesh
+      - json
+      - edit
+    detail: "This is the pattern behind every scripted asset in the project (mesh materials, case entity
+      and app, sector, localization). In-game verified_on/verified_by removed: it is a WolvenKit CLI
+      workflow, not an engine observation."
+  - id: cp2077.mesh.donor-mesh-replacement
+    claim: When importing a custom glb over a donor mesh path, wolvenkit preserves the donor mesh's
+      material structure and embedded metadata; custom geometry replaces only the vertex/face data.
+    status: inferred
+    source: ModWright research
+    tags:
+      - donor
+      - mesh
+      - import
+      - replacement
+      - metadata
+    detail: The pipeline copies the donor mesh next to the glb and imports with --keep (-k in
+      build.ps1). That the donor's material structure and metadata survive is an inference from the
+      pipeline's shape and from the material-editing script having donor materialEntries to print;
+      no source states it directly.
+  - id: cp2077.mesh.phys-chunk-colliders
+    claim: Custom meshes used in lootable entities require a meshMeshParamPhysics chunk with box
+      colliders set to both Simple and Complex filter types; missing physics prevents interact
+      prompts.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - mesh
+      - physics
+      - collider
+      - box
+      - filter
+      - loot
+    detail: Applies to cache_case_top.mesh and cache_case_bottom.mesh. The prompt only appeared once the
+      physics param was grafted in, which is why this is listed among the late-stage lessons of the
+      completed build.
+  - id: cp2077.mesh.headless-blender-render
+    claim: Headless blender renders are used in the pipeline for icon generation (an icon-render script)
+      and visual QA; blender is launched with --background --python <script> to render without gui.
+    status: verified
+    source: ModWright field verification
+    tags:
+      - blender
+      - headless
+      - render
+      - script
+      - icon
+    detail: Four headless render scripts ship with the mod. README names the newer icon render as the
+      current inventory-icon render (moody top-lit pass + gamma curve); the older icon render is its
+      predecessor. In-game verified_on/verified_by removed — nothing here is observed in the engine.

package/knowledge/cyberpunk2077/nativedb.dump.yaml

@@ -0,0 +1,98 @@
+game: cyberpunk2077
+topic: nativedb.dump
+title: cp2077-nativedb's RTTI dump generation and the shape of its reddump JSON files
+facts:
+  - id: cp2077.nativedb.dump.generation-pipeline
+    claim: "NativeDB's RTTI dump assets are generated by installing the separate `RED4.RTTIDumper`
+      RED4ext plugin, running the game until loading blocks and then closing it, and copying four
+      files from `<game>\\bin\\x64\\dumps\\nativedb\\json` into the NativeDB project's
+      `src/assets/reddump/` folder: `enums.json`, `bitfields.json`, `classes.json` and
+      `globals.json`."
+    status: community
+    source: rayshader/cp2077-nativedb@b5d29af README.md:12-24, section "Setup"
+    tags:
+      - nativedb
+      - rttidumper
+      - dump
+      - generation
+      - reddump
+  - id: cp2077.nativedb.dump.readme-pinned-versions
+    claim: The snapshot of rayshader/cp2077-nativedb read for this intake badges itself as NativeDB
+      version 2.1.0, targeting Cyberpunk 2077 game version 2.31.
+    status: verified
+    verified_on: "2.31"
+    source: rayshader/cp2077-nativedb@b5d29af README.md:2-4, badge row at the top
+    tags:
+      - nativedb
+      - version
+    detail: Verified only as a literal reading of the two badges ("version - 2.1.0", "game - 2.31").
+      `verified_on` records the game version the README itself names, on the game's marketing axis;
+      nothing here was observed in-engine.
+  - id: cp2077.nativedb.dump.json-files-are-flat-lists-of-minified-records
+    claim: Each of the four `reddump/*.json` files is a flat top-level JSON array (not a nested tree
+      keyed by name); every element is an object whose field names are single lowercase letters
+      (`a`, `b`, `c`, ...) rather than descriptive names — the real field meanings are only
+      documented in NativeDB's own TypeScript AST types, not in the dump files themselves.
+    status: verified
+    source: rayshader/cp2077-nativedb@b5d29af src/assets/reddump/{enums,bitfields,classes,globals}.json
+      (structure only; no dump content transcribed beyond single illustrative records) and the
+      field-name comments in src/shared/red-ast/red-enum.ast.ts and red-class.ast.ts
+    tags:
+      - nativedb
+      - reddump
+      - json-shape
+      - minified-keys
+  - id: cp2077.nativedb.dump.enum-and-bitfield-record-shape
+    claim: In `enums.json` and `bitfields.json`, each record has field `a` (the enum/bitfield name),
+      optional `b` (an alias name) and `c` (an array of member objects); each member object has
+      exactly one key, the member's name, whose value is its numeric value (for an enum) or bit
+      index (for a bitfield).
+    status: verified
+    source: 'rayshader/cp2077-nativedb@b5d29af src/shared/red-ast/red-enum.ast.ts, the
+      `RedEnumJson`/`RedEnumMemberJson` interfaces (:4-12, the member interface commented "name:
+      value OR name: bit")'
+    tags:
+      - nativedb
+      - reddump
+      - enum
+      - bitfield
+      - schema
+  - id: cp2077.nativedb.dump.class-record-shape
+    claim: "In `classes.json`, each record has optional field `a` (parent class name), required `b` (the
+      class's own name), optional `c` (an alias name), required `d` (a numeric class-flags bitmask),
+      optional `e` (an array of property records) and optional `f` (an array of function records);
+      an optional `g: true` marks the record as a struct rather than a class."
+    status: verified
+    source: rayshader/cp2077-nativedb@b5d29af src/shared/red-ast/red-class.ast.ts, the `RedClassJson`
+      interface (:9-17)
+    tags:
+      - nativedb
+      - reddump
+      - class
+      - struct
+      - schema
+  - id: cp2077.nativedb.dump.property-and-function-record-shape
+    claim: A property record (inside a class's `e` array) has field `a` (a nested type descriptor),
+      optional `b` (the property name), optional `c` (a numeric flags value) and optional `d` (the
+      byte offset within the containing struct/class). A function record (inside a class's `f`
+      array, or a top-level entry in `globals.json`) has field `a` (the function's full/mangled
+      name), optional `b` (a short display name), optional `c` (the return type descriptor) and
+      required `d` (a numeric flags value); a function's parameters, when present, are an array of
+      property-shaped records under key `e`.
+    status: verified
+    source: rayshader/cp2077-nativedb@b5d29af src/shared/red-ast/red-property.ast.ts, the
+      `RedPropertyJson` interface (:6-11); and src/shared/red-ast/red-function.ast.ts, the
+      `RedFunctionJson` interface (:9-15)
+    tags:
+      - nativedb
+      - reddump
+      - property
+      - function
+      - offset
+      - flags
+      - schema
+    detail: 'Checked against the source (2026-09-08): an earlier detail said the sampled `globals.json`
+      entries carried only `a` and `d`. The first records in the file disprove that —
+      `AIInstantiateObject` is `{"a":...,"d":12}`, but `AT_AddATID` also carries `e` (parameters)
+      and `Abs` carries both `c` (return type) and `e`. All four keys occur in globals; only `a` and
+      `d` are non-optional.'

package/knowledge/cyberpunk2077/npc.appearance.yaml

@@ -0,0 +1,275 @@
+game: cyberpunk2077
+topic: npc.appearance
+title: NPC appearance patching in WolvenKit and AMM custom appearances
+facts:
+  - id: cp2077.npc.appearance.component-prefix-naming
+    claim: "Component names in an NPC's `.app` are prefaced by a body-location code: \"t=torso (t0 is
+      usually the body mesh, t1 is usually clothes), l=legs, h=head, s=shoe\". Vik's default
+      appearance, for example, has `t0_001_ma_body__ripper_doc6245` (body mesh) and
+      `t1_001_ma_full__ripper_doc1487` (shirt)."
+    status: community
+    source: wiki.redmodding.org "Altering Appearances within Wolvenkit - Full Workflow", section
+      "Understanding the .app file" (info hint)
+    tags:
+      - npc
+      - appearance
+      - app
+      - component-prefix
+      - naming
+    detail: The page hedges with "usually" and points at the canonical list under
+      garment-support-how-does-it-work#component-prefixes; the same prefixes are what garment
+      support scores against, which is why the dynamic-variants guide warns not to strip them when
+      renaming components. Page title and section name corrected 2026-09-07.
+  - id: cp2077.npc.appearance.edit-is-export-blender-reimport
+    claim: "Editing an NPC's mesh is a round trip, not a direct `.app` edit: check the mesh in
+      WolvenKit's Export Tool and \"Export Selected\"; in Blender (with the WolvenKit Blender IO
+      Suite installed) use \"File>Import>Cyberpunk GLTF\", edit, then export as a Cyberpunk GLB over
+      the same file; back in WolvenKit use \"Tools>Import Tool\" and \"import selected\"; finally
+      replace the component's \"mesh\" path in the `.app` with the new mesh's relative path
+      (right-click the mesh in the project explorer, \"copy relative path\")."
+    status: community
+    source: wiki.redmodding.org "Altering Appearances within Wolvenkit - Full Workflow", sections
+      "Modifying the Body Mesh" and "Modifying the Clothes"
+    tags:
+      - npc
+      - appearance
+      - blender
+      - export
+      - import
+      - workflow
+  - id: cp2077.npc.appearance.edits-are-per-appearance-not-per-npc
+    claim: "Edits land on the one `appearances` array entry that was modified: \"since we didn't copy
+      the mesh and use a custom path, this mod would not display the other two appearances
+      correctly. You would have to modify the other clothes.\""
+    status: community
+    source: wiki.redmodding.org "Altering Appearances within Wolvenkit - Full Workflow", section
+      "Modifying the Clothes" (closing warning hint)
+    tags:
+      - npc
+      - appearance
+      - gotcha
+      - multiple-appearances
+    detail: Vik has three appearances; the guide edits only the default one and says "the process is the
+      same for all of them". Section name corrected 2026-09-07 (there is no "Known Limitations &
+      Gotchas" heading).
+  - id: cp2077.npc.appearance.duplicated-mesh-needs-dependency-path-updated
+    claim: "\"Note that if you did copy the mesh and created a custom path, you would have to also
+      replace the path under 'AppearanceVisualController>appearanceDependancy' for the component to
+      appear correctly.\""
+    status: community
+    source: wiki.redmodding.org "Altering Appearances within Wolvenkit - Full Workflow", section
+      "Modifying the Clothes" (closing warning hint)
+    tags:
+      - npc
+      - appearance
+      - appearancevisualcontroller
+      - dependency
+      - gotcha
+    detail: "The field really is spelled `appearanceDependancy` in the engine data. Corrected
+      2026-09-07: the page says the component will not \"appear correctly\"; the previous claim's
+      \"silently keeps the old dependency resolved\" was unsourced."
+  - id: cp2077.npc.appearance.amm-collab-file-layout
+    claim: "An AMM custom-appearance Collab is two files in two different places: the Lua at
+      `bin/x64/plugins/cyber_engine_tweaks/mods/AppearanceMenuMod/Collabs/Custom
+      Appearances/your_custom_file.lua` inside the WolvenKit project's Resources directory, and a
+      `your_project_name.archive.xl` created DIRECTLY in that Resources directory, not alongside the
+      Lua."
+    status: community
+    source: 'wiki.redmodding.org "AMM: Custom NPC appearances", sections "The .lua file" (folder tree)
+      and "The .xl file > 1. Create the file"'
+    tags:
+      - npc
+      - amm
+      - collab
+      - file-structure
+      - cet
+    detail: "Corrected 2026-09-07: the previous claim placed the `.xl` \"in that same folder\" as the
+      Lua, which the page contradicts — \"Directly in your project's Resources directory, create an
+      empty text file called `your_project_name.archive.xl`\"."
+  - id: cp2077.npc.appearance.amm-lua-required-fields
+    claim: An AMM Collab Lua returns a table with `modder`, `unique_identifier`, `entity_id` and
+      `appearances`. `unique_identifier` "must be UNIQUE so be creative! NO SPACES OR SYMBOLS
+      ALLOWED"; `entity_id` is a string such as `"0xF43B2B48, 18"` that "You can find... using AMM's
+      Swap tab and looking at the NPC".
+    status: community
+    source: 'wiki.redmodding.org "AMM: Custom NPC appearances", section "The .lua file" (the example Lua
+      and its comments)'
+    tags:
+      - npc
+      - amm
+      - lua
+      - entity-id
+      - naming
+      - required-field
+    detail: The page links a dedicated finding-files-amm-npcs guide for locating the entity ID. Section
+      name corrected 2026-09-07 (there is no "Required Fields (.lua file)" heading).
+  - id: cp2077.npc.appearance.amm-delivered-as-resourcepatch
+    claim: "Community page confirms and extends cp2077.archivexl.manifest-top-level-keys. The Collab's
+      `.xl` uses a `resource:` / `patch:` block mapping the modder's own file to the vanilla file it
+      adds to — `path\\to\\your\\app_file.app: -
+      base\\characters\\appearances\\main_npc\\goro_takemura.app` and `path\\to\\your\\ent_file.ent:
+      - base\\quest\\primary_characters\\takemura.ent` — because \"Do not overwrite an NPC's
+      original files! This will cause compatibility issues for every single modder out there, and
+      risk breaking the NPC with every game update.\""
+    status: community
+    source: 'wiki.redmodding.org "AMM: Custom NPC appearances", danger hint under "Summary" and sections
+      "The .xl file > 1. Create the file", "2. Adjust the .app file path" and "3. Adjusting the .ent
+      file path"'
+    tags:
+      - npc
+      - amm
+      - archivexl
+      - resourcepatch
+      - compatibility
+    detail: Names cp2077.archivexl.manifest-top-level-keys
+      (knowledge/cyberpunk2077/archivexl.manifest.yaml), an inferred fact that lists `localization`,
+      `factories` and `streaming` as the three top-level `.xl` keys while explicitly saying that is
+      only what one weapon-mod manifest uses, not the whole schema. This page documents a fourth
+      top-level key, `resource`, with a `patch` sub-key — the same mechanism as
+      cp2077.clothing.refits.body-patch-lists-gendered-player-ents and
+      cp2077.anims.sets.resourcepatch-mounting-route. Both replaced paths are "relative paths"
+      copied from WolvenKit via `Copy Relative Path`.
+  - id: cp2077.npc.appearance.amm-appearance-names-must-match-exactly
+    claim: The Lua's `appearances` array is "a list of appearances you added" and "It has to be the
+      exact name you added to the entity file".
+    status: community
+    source: 'wiki.redmodding.org "AMM: Custom NPC appearances", section "The .lua file" (comments in the
+      example Lua)'
+    tags:
+      - npc
+      - amm
+      - appearance-name
+      - exact-match
+      - gotcha
+    detail: 'Corrected 2026-09-07: "character-for-character including case" and the stated consequence
+      were trimmed — the page says "exact name" without spelling out case handling or the failure
+      mode.'
+  - id: cp2077.npc.appearance.yaml-indentation-strictness
+    claim: "The `.xl` block is indentation-sensitive: \"Do not change the indent (number of spaces at
+      the beginning of each line)\", and \"If your custom appearances aren't working, run your .xl
+      file through yamllint and fix any mistakes.\""
+    status: community
+    source: 'wiki.redmodding.org "AMM: Custom NPC appearances", info hint under "The .xl file > 1.
+      Create the file" and section "4. Optional: Fixing that damn indent"'
+    tags:
+      - npc
+      - amm
+      - yaml
+      - indentation
+      - gotcha
+    detail: "The body-mods page gives the same advice for its own `.xl`/`.yaml`: \"Double-check your
+      `.yaml` via yamllint and make sure you don't have syntax errors (indent matters)\". Section
+      names corrected 2026-09-07."
+  - id: cp2077.npc.appearance.world-androids-use-the-2-0-templates
+    claim: "The game's android character records resolve, almost all of them, to two Phantom Liberty-era
+      templates: ep1/characters/entities/corpo/corpo__ep1_android_ma.ent (62 records: the Arasaka,
+      Militech, NCPD, security, Kang Tao and Sixth Street androids with their district variants) and
+      ep1/characters/entities/gang/gang__ep1_android_ma.ent (19: Maelstrom, Wraiths, Scavengers).
+      Only Character.android_guards resolves to the base game's
+      base/characters/entities/corpo/corpo__android_ma.ent. Both 2.0 templates use man_base.rig,
+      carry Item_Attachment_Slot with Head, and draw their looks from the base game's
+      corpo__android_ma.app (6 appearances on the corpo template) and gang__android_ma.app (22 on
+      the gang one), under entity-level names prefixed corpo__android_ma_ / gang__android_ma_."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - android
+      - npc
+      - template
+      - appearance
+      - archivexl
+      - patch
+    detail: A mod that patches NPC templates by path (an ArchiveXL resource.patch list) and lists only
+      the base-game android templates misses every world android; a quickhack mod's camera patch did
+      until v0.12.22.
+  - id: cp2077.npc.appearance.spawning-a-default-appearance-record-can-render-nothing
+    claim: "exEntitySpawner.SpawnRecord of Character.maelstrom_android_android2_copperhead_ma (the
+      gang__ep1_android_ma.ent template) with no appearance argument gave an android with no
+      rendered body: only its marker and weak points. GetCurrentAppearanceName read \"default\". The
+      same call with gang__android_ma_maelstrom_droid__lvl2_01 as the third argument rendered. The
+      corpo template's Arasaka record, spawned the same way without an appearance, rendered in
+      corpo__android_ma_arasaka_droid__lvl2_01."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - spawn
+      - appearance
+      - android
+      - codeware
+      - bridge
+  - id: cp2077.npc.appearance.the-distance-proxy-mesh-is-the-engines
+    claim: "An NPC appearance carries an AppearanceProxyMesh (an entSkinnedMeshComponent), the
+      low-detail stand-in the engine switches on and off with the viewer's distance. Script that
+      switches every visual component off and later restores each one's saved on/off state forces
+      the proxy back on if it was on at the save (the NPC far away then). Once the viewer is close,
+      the NPC renders only its weapon: its meshes are on, their masks right, and an off-on of every
+      component does not help. It rendered again by itself later."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - appearance
+      - lod
+      - proxy
+      - mesh
+      - npc
+      - take
+    related:
+      - cp2077.npc.appearance.world-androids-use-the-2-0-templates
+  - id: cp2077.npc.appearance.a-changed-mask-draws-after-an-off-on
+    claim: A visual component's chunkMask change is drawn only once the component re-registers (Toggle
+      off then on); this holds for the AppearanceProxyMesh too. Hiding an NPC by zeroing masks and
+      restoring them later leaves meshes the engine re-enables afterwards drawing nothing (every
+      mask right, every mesh on) until an off-on; one off-on of every enabled visual component, a
+      second and three seconds after the restore, makes it visible. Toggling a component the engine
+      owns (the proxy) to a remembered state is what
+      cp2077.npc.appearance.the-distance-proxy-mesh-is-the-engines warns against; an off-on only
+      when it is on now keeps the engine's state.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - appearance
+      - mask
+      - proxy
+      - toggle
+      - npc
+      - hide
+    related:
+      - cp2077.npc.appearance.the-distance-proxy-mesh-is-the-engines
+  - id: cp2077.npc.appearance.effect-spawners-are-visual-components
+    claim: "entEffectSpawnerComponent is an entIVisualComponent: a hide that toggles every visual
+      component off also disables the NPC's effect spawners. Disabling a spawner does not stop an
+      effect already playing, and an entKillEffectEvent queued in the same frame then fails to stop
+      it: the 2.0 android's eye scan (\"scan\", on ScanEffectSpawner) hung in the air. Left enabled,
+      the kill by name works (with a second kill at the freeze half a second later, the scan went)."
+    status: inferred
+    verified_on: "2.31"
+    source: ModWright research
+    tags:
+      - effects
+      - spawner
+      - kill
+      - hide
+      - npc
+  - id: cp2077.npc.appearance.a-human-looks-head-group
+    claim: "A human NPC look's meshes name their slot by prefix; the head group is h0_ (the head), ht_
+      (teeth), he_ (eyes), heb_ (eyebrows), hh_ (hair), hx_ (makeup), h1_ (hats, masks, kerchiefs)
+      and h2_ (helmets); the body is t0_/t1_/t2_ (torso layers), a0_ (arms; \"_big\" variants on the
+      strong looks), l1_ (legs), s1_ (shoes), g1_ (gloves), i1_ (items, slots, chokers). An NPC
+      template carries no meshes itself: its looks are entries naming an .app appearance
+      (gang__ep1_maelstrom_ma.ent: 38 entity-level looks, all from gang__maelstrom_ma.app, on
+      man_base.rig, the strong looks included)."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - appearance
+      - mesh
+      - human
+      - head
+      - fpp
+    related:
+      - cp2077.npc.appearance.world-androids-use-the-2-0-templates