modwright 0.1.0

package/knowledge/cyberpunk2077/clothing.refits.yaml

@@ -0,0 +1,215 @@
+game: cyberpunk2077
+topic: clothing.refits
+title: ArchiveXL body types and the Blender garment-refit workflow
+facts:
+  - id: cp2077.clothing.refits.body-mod-version-floor
+    claim: 'The body-mods page states a "Minimum required ArchiveXL version: 1.5". The older method of
+      adding the component to each individual appearance still works, but the page directs modders
+      to the new method "(for version >= 1.14)" as more robust and less tedious.'
+    status: community
+    source: "wiki.redmodding.org \"ArchiveXL: body mods and refits\", section \"Summary\" (front-matter
+      line) and the info hint under \"Wait, that's not what I want!\""
+    tags:
+      - archivexl
+      - body-mod
+      - version-floor
+    detail: Framework versions on ArchiveXL's own numbering, so they stay in the claim with no
+      `verified_on`. The archived old method is kept on the wiki as
+      "archived-registering-the-body-tag". Section name corrected 2026-09-07 (there is no "Version
+      Requirements" heading).
+  - id: cp2077.clothing.refits.default-body-tag-is-base-body
+    claim: "\"If no body mod is installed, the value will be `base_body`\" — so `base_body` is what a
+      dynamic appearance's `{body}` substitution resolves to on an unmodified install, and mesh
+      files and folders must be named accordingly."
+    status: community
+    source: 'wiki.redmodding.org "ArchiveXL: body mods and refits", section "Clothing mods: Making use
+      of the tags > Dynamic Appearances" (warning hint)'
+    tags:
+      - archivexl
+      - body-mod
+      - base-body
+      - default
+    detail: The same hint notes `base_body` is also the value for body mods that are vanilla-shaped,
+      naming EVB and VTK Vanilla HD FemV. Section name corrected 2026-09-07.
+  - id: cp2077.clothing.refits.bodytypes-key-snake-cases-name
+    claim: "A custom body type is declared in a `.xl` file as `player: bodyTypes: [ CustomName ]`; for
+      substitutions ArchiveXL converts that name to snake case, so `BoobsForBackProblems` is
+      consumed as `boobs_for_back_problems` and `Adonis` as `adonis`."
+    status: community
+    source: "wiki.redmodding.org \"ArchiveXL: body mods and refits\", section \"1. Registering the body
+      mod\" (the yaml block's inline comment \"for substitutions, this will be converted to snake
+      case\")"
+    tags:
+      - archivexl
+      - body-mod
+      - manifest
+      - bodytypes
+      - naming
+      - snake-case
+    detail: "Corrected 2026-09-07: the snake-case form is used for SUBSTITUTIONS only. Component names
+      keep the declared CamelCase form — see cp2077.clothing.refits.body-tag-patches-player-ent,
+      where the component is named `Body:BoobsForBackProblems`."
+  - id: cp2077.clothing.refits.body-tag-patches-player-ent
+    claim: Registering a body-mod tag means shipping a patch `.ent` whose `components` array holds an
+      `entMeshComponent` whose `name` matches the body mod in the form `Body:<CustomName>`, e.g.
+      `Body:BoobsForBackProblems`. The component name itself carries the tag identity; there is no
+      separate declared field.
+    status: community
+    source: 'wiki.redmodding.org "ArchiveXL: body mods and refits", section "2. Patch the player entity
+      files > Set up the patch .ent" (step 2)'
+    tags:
+      - archivexl
+      - body-mod
+      - resourcepatch
+      - entmeshcomponent
+      - naming
+    detail: "The page's own verification step is the CET snippet
+      `print(GetPlayer():FindComponentByName(\"Body:BoobsForBackProblems\"))`, or checking the
+      component in RedHotTools. A separate CET snippet reads the active body:
+      `print(Game.GetScriptableSystemsContainer():Get(\"PuppetStateSystem\"):GetBodyTypeSuffix(Item\
+      ID.new(), GetPlayer(), nil))`."
+  - id: cp2077.clothing.refits.body-patch-lists-gendered-player-ents
+    claim: "The patch `.ent` is registered through ArchiveXL resource patching, with the `.xl` block
+      `resource: patch: path\\to\\your\\patch_file.ent: - !include player_wa.ent - !include
+      player_ma.ent`. The wiki's instruction is \"Include only the relevant body gender!\", so a
+      female-only body mod lists only `player_wa.ent`."
+    status: community
+    source: 'wiki.redmodding.org "ArchiveXL: body mods and refits", section "2. Patch the player entity
+      files > Register the patch .ent"'
+    tags:
+      - archivexl
+      - body-mod
+      - resourcepatch
+      - gender
+      - manifest
+    detail: "Renamed from cp2077.clothing.refits.body-patch-must-list-both-genders on 2026-09-07: the
+      old claim said a patch \"must list the gendered player .ent paths it targets explicitly\",
+      which inverts the page's actual instruction to include only the relevant gender. Also of note:
+      the page's \"Invisible mesh for body xyz\" troubleshooting entry is forgetting a new body's
+      mesh in the resource-patch list."
+  - id: cp2077.clothing.refits.named-community-body-types
+    claim: "Registered body-mod tag names, with the lowercase substitution value used for `{body}` and
+      for `&body=value` conditional appearances — male V: Adonis/`adonis`, Atlas/`atlas`,
+      Gymfiend/`gymfiend`; female V: Lush/`lush`, Ult/`ult`, Solo_OG/`solo_og`, SoloArms/`soloarms`,
+      Song2/`song2`, Flat/`flat`, ELEGY/`elegy`, RB/`rb`, EBB/`ebb`, EBBP/`ebbp`, EBBRB/`ebbrb`,
+      EBBPRB/`ebbprb`, Angel/`angel`, EVE/`eve`, EVB/`evb`, VHD/`vhd`, Ishtar/`ishtar`,
+      Small/`small`, Big/`big`."
+    status: community
+    source: 'wiki.redmodding.org "ArchiveXL: body mods and refits", section "Supporting mods" (the two
+      tag tables)'
+    tags:
+      - archivexl
+      - body-mod
+      - naming
+      - community-convention
+    detail: "Corrected 2026-09-07: the page flags BOTH EVB and VHD (not EVB alone) with \"These tags are
+      not required unless your mod specially modifies body meshes for these body mods. Otherwise the
+      value is `base_body` since these bodies are Vanilla shaped.\" The previous claim's closing
+      sentence about a mod only needing to cover the body types it intends to support is not on this
+      page; the equivalent statement lives on the dynamic-variants guide (\"you only need to create
+      extra meshes where refits are needed\"). Section name corrected (there is no \"Body Type Tags
+      and Names\" heading)."
+  - id: cp2077.clothing.refits.akl-autofitter-tool
+    claim: "The AKL Autofitter, an auto-refitter by AllKnowingLion shipped with the WolvenKit Blender IO
+      Suite from version 1.5.0, automates conforming a garment mesh to a body mod: with a mesh
+      selected, find it under Mesh Tools in the CP77 panel, pick the target body from the dropdown,
+      and click the button."
+    status: community
+    source: 'wiki.redmodding.org "WKit Blender Plugin: AKL Autofitter", sections "Summary" and "How to
+      auto-refit"; version floor from "R&R: Refitting (step by step)", section "Step 4: Refitting"
+      (success hint, "Starting in version 1.5.0")'
+    tags:
+      - refit
+      - blender
+      - autofitter
+      - wolvenkit-blender-io-suite
+      - tool
+    detail: The refitting guide's hint adds that if you use the plugin instead of refitting by hand you
+      must select all the meshes first. Source corrected 2026-09-07 — the refitting page has no
+      "Autofitter Tool" section; the tool has its own page.
+  - id: cp2077.clothing.refits.manual-refit-proportional-editing
+    claim: Manual refitting exports the base body and the garment from WolvenKit as .glb, imports both
+      into one Blender file, hides the body armature, selects the garment meshes and edits them in
+      Edit Mode with Proportional Editing on at a low Proportional Size (0.1m). Proportional Editing
+      is chosen because it "leaves garment supports intact and prevents the risk of string cheese".
+    status: community
+    source: 'wiki.redmodding.org "R&R: Refitting (step by step)", sections "Step 2: Exporting the meshes
+      from WKit", "Step 3: Importing to Blender" and "Step 4: Refitting"'
+    tags:
+      - refit
+      - blender
+      - proportional-editing
+      - manual-workflow
+    detail: "Rationale corrected 2026-09-07: the page's stated reason is garment support and string
+      cheese, not smooth falloff/creases. The base body meshes are
+      `base\\characters\\common\\player_base_bodies\\player_female_average\\t0_000_pwa_base__full.m\
+      esh` and `...\\player_man_average\\t0_000_pma_base__full.mesh`. Tools used are scale (`S`) and
+      move (`G`), axis-locked with `X`/`Y`/`Z`; the mouse wheel scales the proportional radius once
+      a tool is active. Re-export overwrites the .glb that was originally imported."
+  - id: cp2077.clothing.refits.reimport-requires-garment-support-checkbox
+    claim: Reimporting a refitted mesh means selecting it in the Import Tool and checking the `Import
+      Garment Support` box, and doing the same for the second mesh and the emissive components
+      before importing.
+    status: community
+    source: 'wiki.redmodding.org "R&R: Refitting (step by step)", section "Step 6: Importing into
+      Wolvenkit"'
+    tags:
+      - refit
+      - wolvenkit
+      - garment-support
+      - import
+      - gotcha
+    detail: The page does not state what happens if the box is left unchecked; the previously recorded
+      consequence was trimmed on 2026-09-07. The closest stated consequence is on the string-cheese
+      workaround, where deleting the garment-support parameters "will destroy the automatic deform
+      when you put a jacket on".
+  - id: cp2077.clothing.refits.string-cheese-distortion-fix
+    claim: '"As of 8.9.1, Garment Support is still experimental. If your meshes look like string cheese
+      or twitch all over the place, you can delete the parameters. That will destroy the automatic
+      deform when you put a jacket on, but at least your mesh will work."'
+    status: community
+    source: 'wiki.redmodding.org "R&R: Refitting (step by step)", section "Step 6: Importing into
+      Wolvenkit" (info hint)'
+    tags:
+      - refit
+      - garment-support
+      - string-cheese
+      - bug
+      - workaround
+    detail: Section name corrected 2026-09-07 (the page's "Troubleshooting" section contains only the
+      viewport-shading entry, not this one). The full string-cheese treatment lives on the linked
+      troubleshooting-your-mesh-edits page.
+  - id: cp2077.clothing.refits.export-materials-checkbox-workaround
+    claim: "Known gotcha: if exporting a mesh from WolvenKit's Export Tool fails with \"Error while
+      finding the file: ...\\textures_netrunning_suit.mi\", uncheck \"Export Materials (default)\"
+      under Import/Export: Mesh (3d Model) in the export tool's settings panel and export again."
+    status: community
+    source: 'wiki.redmodding.org "R&R: Refitting (step by step)", section "Step 2: Exporting the meshes
+      from WKit" (the "Export failed: Error while finding file" box)'
+    tags:
+      - refit
+      - wolvenkit
+      - export
+      - bug
+      - workaround
+    detail: 'Renamed from cp2077.clothing.refits.export-tool-mesh-checkbox-workaround and corrected on
+      2026-09-07 on two counts: the checkbox is "Export Materials (default)" (Import/Export: Mesh
+      (3d Model) is the settings section it lives under, not the checkbox), and the failing export
+      is the WolvenKit -> .glb export in Step 2, not an export out of Blender.'
+  - id: cp2077.clothing.refits.viewport-shading-hides-clipping-colour
+    claim: The refitting guide recolours the imported body mesh (Material Properties tab -> uncheck "Use
+      Nodes" -> set a non-white base colour) so clipping is visible. If the colour does not show,
+      the fix is switching Blender's viewport to Viewport Shading (the third globe in the top-right
+      corner), not repainting.
+    status: community
+    source: 'wiki.redmodding.org "R&R: Refitting (step by step)", section "Step 3: Importing to Blender"
+      (step 5) and section "Troubleshooting > My mesh refuses to show any colours!"'
+    tags:
+      - refit
+      - blender
+      - viewport-shading
+      - gotcha
+    detail: "Renamed from cp2077.clothing.refits.viewport-shading-hides-vertex-colors on 2026-09-07: the
+      guide colourises via the material's base colour, not via vertex colours. (Vertex colour does
+      have a documented role elsewhere in Cyberpunk — see
+      cp2077.hair.modding.vertex-color-ao-convention — but not in this workflow.)"

package/knowledge/cyberpunk2077/codeware.overview.yaml

@@ -0,0 +1,111 @@
+game: cyberpunk2077
+topic: codeware.overview
+title: Codeware's resource, localization, reflection and compatibility utilities
+facts:
+  - id: cp2077.codeware.overview.documentation-category-list
+    claim: "Codeware's own documentation groups its API surface under nine headings: Lifecycle, World,
+      Entities, Player, User Interface, Resources, Localization, Reflection and Utilities."
+    status: community
+    source: psiberx/cp2077-codeware/README.md, section "Documentation" (list)
+    tags:
+      - codeware
+      - overview
+      - documentation-structure
+    detail: cp2077.codeware.systems.yaml's existing facts are drawn from Lifecycle (scriptable
+      services), and from Player/World-adjacent systems (callback system, appearance refresh, static
+      entities, player system, wardrobe, vehicle unlock); this file's facts are drawn from the
+      remaining Resources, Localization and Reflection sections plus one World-adjacent
+      compatibility idiom.
+  - id: cp2077.codeware.overview.resource-depot-existence-checks
+    claim: "`GameInstance.GetResourceDepot()` exposes `ArchiveExists(name)` and
+      `ResourceExists(depotPath)`, letting a mod check at runtime whether a specific `.archive` file
+      or a specific resource inside any mounted archive is present — the documented uses are
+      verifying that the mod's own archive is actually enabled, and detecting whether another mod
+      (and therefore a resource it ships) is installed."
+    status: community
+    source: psiberx/cp2077-codeware/wiki/Home.md, section "Resources > Checking resource existence"
+    tags:
+      - codeware
+      - resourcedepot
+      - archiveexists
+      - resourceexists
+      - compat-check
+  - id: cp2077.codeware.overview.resource-loading-is-async-token-callback
+    claim: Reading an arbitrary resource at runtime goes through
+      `GameInstance.GetResourceDepot().LoadResource(path)`, which returns a `ResourceToken`; the
+      caller registers a callback (`token.RegisterCallback(this, n"OnResourceReady")`) and only
+      accesses `token.GetResource()` inside that callback — resource loading through this API is
+      asynchronous, not a direct return value.
+    status: community
+    source: psiberx/cp2077-codeware/wiki/Home.md, section "Resources > Reading resources"
+    tags:
+      - codeware
+      - resourcedepot
+      - resourcetoken
+      - async
+      - loadresource
+  - id: cp2077.codeware.overview.resource-ref-assignment-operator
+    claim: A native `ResourceRef`/`ResourceAsyncRef` field added via `@addField` is initialized by
+      assigning a resource depot path to it with the `*=` operator (the wiki's example is
+      `weapon.effect *= r"base\gameplay\game_effects\strongmelee.es";`); `*=` is the only
+      initialization form the page shows.
+    status: community
+    source: psiberx/cp2077-codeware/wiki/Home.md, section "Resources > Resource references"
+    tags:
+      - codeware
+      - resourceref
+      - addfield
+      - operator
+      - syntax
+  - id: cp2077.codeware.overview.localization-provider-package-pattern
+    claim: "Codeware's script-level localization system is wired up in two parts: a
+      `ModLocalizationProvider` subclass resolves a language code (`CName`) to a
+      `ModLocalizationPackage` instance and defines a fallback language via `GetFallback()`; each
+      `ModLocalizationPackage` subclass defines its actual strings in
+      `DefineTexts()`/`DefineSubtitles()` using `Text`/`TextM`/`TextF` (and
+      `Subtitle`/`SubtitleM`/`SubtitleF`) calls, with gendered variants set either as two separate
+      calls or one three-argument `Text(key, female, male)` call."
+    status: community
+    source: psiberx/cp2077-codeware/wiki/Home.md, sections "Localization > Localization providers" and
+      "Localization > Localization packages"
+    tags:
+      - codeware
+      - localization
+      - modlocalizationprovider
+      - modlocalizationpackage
+    detail: Texts registered this way are also pushed into the native localization system, so they
+      remain reachable via `GetLocalizedTextByKey`/`GetLocalizedText` and from TweakDB records — not
+      only from the mod's own redscript.
+  - id: cp2077.codeware.overview.reflection-get-class-and-call
+    claim: "Codeware's `Reflection` API lets a mod resolve a class by name
+      (`Reflection.GetClass(n\"...\")` or `Reflection.GetTypeOf(instance)`), enumerate its
+      properties/functions, and read/write/call them dynamically: `prop.GetValue(instance)`,
+      `getter.Call(instance)`, `setter.Call(instance, [args])`, with a `status`-returning overload
+      of `Call` available to detect argument-count/signature mismatches instead of throwing."
+    status: community
+    source: psiberx/cp2077-codeware/wiki/Home.md, sections "Reflection > Inspecting types and values"
+      and "Reflection > Custom callbacks"
+    tags:
+      - codeware
+      - reflection
+      - getclass
+      - getfunction
+      - call
+      - dynamic-dispatch
+    detail: Reflection-based callback invocation by short function name requires the target function to
+      carry the `cb` qualifier ("Don't forget to use `cb` modifier for callbacks to be able to use
+      functions short names."); this is the same `cb` item qualifier redscript's grammar defines
+      (see cp2077.redscript.modules.item-qualifier-keywords).
+  - id: cp2077.codeware.overview.moduleexists-for-soft-compat
+    claim: For cross-mod or cross-patch compatibility checks that can't be expressed with redscript's
+      own conditional compilation (`ModuleExists()`), Codeware's documented alternative is to use
+      Reflection to check whether a particular class, property or function exists at runtime before
+      touching it, rather than assuming it does.
+    status: community
+    source: psiberx/cp2077-codeware/wiki/Home.md, section "Reflection > Mods and patches compatibility"
+    tags:
+      - codeware
+      - moduleexists
+      - reflection
+      - compatibility
+      - soft-dependency

package/knowledge/cyberpunk2077/codeware.systems.yaml

@@ -0,0 +1,192 @@
+game: cyberpunk2077
+topic: codeware.systems
+title: Codeware's redscript API surface and version floors
+facts:
+  - id: cp2077.codeware.systems.version-floors
+    claim: Codeware's README lists its compatibility as Cyberpunk 2077 2.31, redscript 0.5.31+ and Cyber
+      Engine Tweaks 1.37.0+, and its installation step 1 requires RED4ext 1.29.0+ before extracting
+      `Codeware-x.x.x.zip` into the Cyberpunk 2077 directory.
+    status: community
+    source: cp2077-codeware README.md, sections "Getting Started > Compatibility" (game, redscript, CET)
+      and "Getting Started > Installation" (RED4ext)
+    tags:
+      - codeware
+      - version-floor
+      - redscript
+      - cet
+      - red4ext
+    detail: "Source corrected 2026-09-07: RED4ext is listed under Installation, not Compatibility, and
+      the previous claim's parenthetical \"(per its own README, version 1.18.0 wiki)\" conflated two
+      things. 1.18.0 is the version stamped on line 1 of the Codeware wiki's Home page, and is what
+      every API fact in this file was read against; it is not a floor. Framework versions stay in
+      the claim; \"Cyberpunk 2077 2.31\" is the game version this Codeware release targets, not an
+      observation date, so there is no `verified_on`. This instantiates the general
+      cp2077.packaging.version-matrix-breakage."
+  - id: cp2077.codeware.systems.service-persists-between-sessions
+    claim: '"Services are singletons that created on scripts initialization and, unlike scriptable
+      systems, live between game sessions. To create your own service, you have to define a class
+      derived from `ScriptableService`." The instance is reached with
+      `GameInstance.GetScriptableServiceContainer().GetService(n"MyService") as MyService`.'
+    status: community
+    source: cp2077-codeware wiki Home, section "Lifecycle > Scriptable services"
+    tags:
+      - codeware
+      - scriptableservice
+      - scriptablesystem
+      - lifecycle
+    detail: Its lifecycle callbacks are `OnLoad` ("Scripts loaded"), `OnReload` ("Scripts reloaded"),
+      `OnInitialize` ("Game instance initialized, can access game systems") and `OnUninitialize`
+      ("Game is shutting down") — the same four the Mod Settings page wires `Listen`/`Unlisten`
+      into, see cp2077.ui.modsettings.lifecycle-differs-by-base-class.
+  - id: cp2077.codeware.systems.module-scoped-service-needs-full-path
+    claim: '"If you declare `MyService` in a module, you must include the full path of the module to get
+      the service" — a service declared in `module MyModule.Services` is fetched as
+      `GetService(n"MyModule.Services.MyService")`.'
+    status: community
+    source: cp2077-codeware wiki Home, section "Lifecycle > Scriptable services"
+    tags:
+      - codeware
+      - scriptableservice
+      - module
+      - gotcha
+    detail: 'Corrected 2026-09-07: "passing the bare name returns null" was trimmed — the wiki states
+      the requirement without describing the failure mode.'
+  - id: cp2077.codeware.systems.persistent-field-type-exclusions
+    claim: '"Service properties marked as `persistent` will keep their state forever. Unlike scriptable
+      systems, service state storage is not tied to save files." "Persistence is available for all
+      types except `String`, `ResRef`, `Variant`."'
+    status: community
+    source: cp2077-codeware wiki Home, section "Lifecycle > Scriptable services"
+    tags:
+      - codeware
+      - persistent
+      - scriptableservice
+      - type-exclusion
+    detail: "Corrected 2026-09-07: \"tied to the mod's install instead\" was trimmed — the wiki says
+      only that storage is not tied to save files. The worked example counts game launches since the
+      mod was installed via a `persistent let counter: Int32` inside a struct."
+  - id: cp2077.codeware.systems.unmarked-fields-reset-silently
+    claim: "\"In case of objects, only fields marked as `persistent` are restored, and unmarked fields
+      are reset to defaults on each game launch. It's safe to change persistent data structure at
+      any time.\""
+    status: community
+    source: cp2077-codeware wiki Home, section "Lifecycle > Scriptable services"
+    tags:
+      - codeware
+      - persistent
+      - gotcha
+    detail: 'Corrected 2026-09-07: "with no warning that it was dropped" was trimmed as unsourced, and
+      the reassurance that the structure is safe to change was added since it is the actionable
+      half.'
+  - id: cp2077.codeware.systems.service-object-reference-disposal-risk
+    claim: '"Be careful with storing references to game objects in services. Most objects must be
+      disposed when game session ends. An unreleased reference can interfere with normal object
+      disposal and lead to bugs such as disappearing sounds or crashes."'
+    status: community
+    source: cp2077-codeware wiki Home, section "Lifecycle > Scriptable services" (the "Referencing game
+      objects" blockquote)
+    tags:
+      - codeware
+      - scriptableservice
+      - memory
+      - disposal
+      - gotcha
+  - id: cp2077.codeware.systems.callback-system-target-selectors
+    claim: A callback is registered as `GameInstance.GetCallbackSystem().RegisterCallback(n"<Event>",
+      this, n"<Method>").AddTarget(<selector>)`. Events include `Resource/Load`,
+      `Resource/PostLoad`, `Session/BeforeStart`, `Session/Start`, `Session/Ready`,
+      `Session/BeforeSave`, `Entity/Extract`, `Entity/Assemble`, `Entity/Initialize`,
+      `Entity/Reassemble`, `Entity/Attach`, `Entity/Detach`, `Component/Toggle`, `Input/Key`,
+      `Input/Axis` and `InkWidget/Spawn`. Selectors are typed to the event —
+      `ResourceTarget.Path(ResRef)`, `ResourceTarget.Type(CName)`,
+      `EntityTarget.ID`/`.Type`/`.RecordID(TweakDBID)`/`.Template`/`.Appearance`/`.Definition`,
+      `ComponentTarget.ID`/`.Name`, `InputTarget.Key`/`.Axis`,
+      `inkWidgetTarget.Library`/`.Controller`.
+    status: community
+    source: cp2077-codeware wiki Home, section "Lifecycle > Game events"
+    tags:
+      - codeware
+      - callbacksystem
+      - resourcetarget
+      - entitytarget
+      - syntax
+    detail: "Caution for a validator: the event table names `Entity/Attach`, but the wiki's own
+      `SetRunMode` example registers `n\"Entity/Attached\"` — the two spellings disagree on the same
+      page. Callback lifetime: \"When defined inside scriptable service, callback stays registered
+      until you manually unregister it. When defined in other contexts, callback is auto removed at
+      the end of the session\", overridable with `.SetLifetime(CallbackLifetime.Forever)` or
+      `...Session)`. The callback system can be accessed before the game instance is initialized."
+  - id: cp2077.codeware.systems.callback-once-run-mode
+    claim: '"You can make callback to auto unregister after being fired by calling
+      `.SetRunMode(CallbackRunMode.Once)`." `CallbackRunMode.OncePerTarget` instead auto-unregisters
+      "after being fired for each listed target".'
+    status: community
+    source: cp2077-codeware wiki Home, section "Lifecycle > Game events"
+    tags:
+      - codeware
+      - callbacksystem
+      - runmode
+      - syntax
+  - id: cp2077.codeware.systems.appearance-refresh-vs-load
+    claim: "\"After changing component mesh resource and/or appearance you can request it to load new
+      appearance\" with `comp.LoadAppearance()`; \"After changing any other properties that don't
+      require loading resources you can refresh appearance\" with `comp.RefreshAppearance()`.
+      Supported components are `entMeshComponent`, `entSkinnedMeshComponent`,
+      `entGarmentSkinnedMeshComponent` and `entMorphTargetSkinnedMeshComponent`."
+    status: community
+    source: cp2077-codeware wiki Home, section "Entities > Mesh appearances"
+    tags:
+      - codeware
+      - loadappearance
+      - refreshappearance
+      - entity-component
+    detail: The worked example is `comp.mesh *= r"mod\player\dynamic.mesh"; comp.meshAppearance =
+      n"neon_red"; comp.LoadAppearance();`. Softened on 2026-09-07 from "must be called ... (it
+      re-resolves resources)" to the wiki's own "you can request it to load".
+  - id: cp2077.codeware.systems.static-entity-reposition-without-respawn
+    claim: '"Static entities can be moved now without respawning them at new position" via
+      `entity.SetWorldTransform(transform)`.'
+    status: community
+    source: cp2077-codeware wiki Home, section "Entities > World transform"
+    tags:
+      - codeware
+      - setworldtransform
+      - static-entity
+  - id: cp2077.codeware.systems.player-system-alternate-puppets
+    claim: Codeware adds functions to the player system for the puppets besides the main player object —
+      `playerSystem.GetCustomizationPuppet()`, `GetInventoryPuppet()` and `GetPhotoPuppet()`, from
+      `GameInstance.GetPlayerSystem(GetGameInstance())`, for the customization screen, inventory
+      screen and photo mode respectively.
+    status: community
+    source: cp2077-codeware wiki Home, section "Player > Accessing player objects"
+    tags:
+      - codeware
+      - playersystem
+      - customization
+      - photo-mode
+      - puppet
+  - id: cp2077.codeware.systems.wardrobe-forget-item
+    claim: '"Items can be permanently removed from wardrobe" with
+      `GameInstance.GetWardrobeSystem(GetGameInstance()).ForgetItemID(ItemID.FromTDBID("Items.Glasses_03_basic_09"))`.'
+    status: community
+    source: cp2077-codeware wiki Home, section "Player > Managing wardrobe"
+    tags:
+      - codeware
+      - wardrobesystem
+      - forgetitemid
+    detail: Split from a combined wardrobe+vehicle fact on 2026-09-07; "transmog history" was dropped,
+      as the wiki says only "wardrobe".
+  - id: cp2077.codeware.systems.vehicle-unlock-by-record-id
+    claim: "\"Player vehicles can now be enabled by record ID instead of string, which normally can't be
+      retrieved at runtime\" —
+      `GameInstance.GetVehicleSystem(GetGameInstance()).EnablePlayerVehicleID(t\"Vehicle.v_sport2_q\
+      uadra_type66_avenger_player\", true)`."
+    status: community
+    source: cp2077-codeware wiki Home, section "Player > Unlocking vehicles"
+    tags:
+      - codeware
+      - vehiclesystem
+      - tweakdbid
+      - unlock
+    detail: Split from a combined wardrobe+vehicle fact on 2026-09-07. The record name shape matches
+      cp2077.vehicles.entities.tweak-name-from-ent-filename.