modwright 0.1.0

package/knowledge/cyberpunk2077/vehicles.dashboard-ui.yaml

@@ -0,0 +1,203 @@
+game: cyberpunk2077
+topic: vehicles.dashboard-ui
+title: Vehicle .inkwidget/.inkstyle dashboard UI and the .inkatlas coordinate system
+facts:
+  - id: cp2077.vehicles.dashboard-ui.inkwidget-tree-path
+    claim: Dashboard parts are configured in the `.inkwidget` at `RDTDataViewModel > libraryItems > 0 >
+      packageData > 0 > rootWidget > children > children > [part]`. Each `inkCanvasWidget` is its
+      own part container and can hold further parts, reached at `[root inkCanvasWidget] > children >
+      children > [nested inkCanvasWidget]`.
+    status: community
+    source: "wiki.redmodding.org \"Boe6's vehicles: .inkwidget and .inkstyle - Animated UI\", section
+      \"Learning .inkwidget files\""
+    tags:
+      - vehicle
+      - inkwidget
+      - dashboard
+      - ui
+      - resource-tree
+    detail: The `.inkwidget` is linked from a WorldWidgetComponent through its `widgetResource` field,
+      and its output is previewable in WolvenKit's "Widget Preview" panel. Section name corrected
+      2026-09-07 (there is no "File Structure Overview" heading; the page's three headings are
+      "Learning .inkwidget files", "The .inkatlas file" and "The .inkstyle file").
+  - id: cp2077.vehicles.dashboard-ui.anchor-margin-anchorpoint-distinct
+    claim: "Positioning an `.inkwidget` element uses three distinct values: `anchor`, \"the point on
+      your UV map that the inkwidget starts calculating the position\", chosen from presets such as
+      TopLeft or CenterRight; `margin`, the final location, where `left` is the X offset and `top`
+      the Y offset and `bottom`/`right` can be left at 0; and `anchorPoint`, \"the part offset from
+      it's origin\", where an X of 1 moves the part left by 100% of the part size as defined in the
+      `.inkatlas`."
+    status: community
+    source: "wiki.redmodding.org \"Boe6's vehicles: .inkwidget and .inkstyle - Animated UI\", section
+      \"Learning .inkwidget files\""
+    tags:
+      - vehicle
+      - inkwidget
+      - anchor
+      - margin
+      - anchorpoint
+      - ui
+    detail: '"A typical speedometer will have both X and Y set at 0.5, as this sets the center of the
+      image as the origin, allowing an arrow in the middle to rotate around the center." An
+      inkCanvasWidget can also be moved under "layout > margin". Section name corrected 2026-09-07.'
+  - id: cp2077.vehicles.dashboard-ui.needle-rotation-fields
+    claim: "\"Parts that move/animate on an angle rotation are centered around the inkCanvasWidget's
+      origin.\" The swept range is set on the widget's `logicController`:
+      `analogSpeedNeedleMinRotation` (starting angle), `analogSpeedNeedleMaxRotation` (end/max
+      angle) and `analogSpeedNeedleMaxValue` (\"Max driving speed of the gauge, used in speedometer
+      for MPH value\"). 0 degrees is left from center."
+    status: community
+    source: "wiki.redmodding.org \"Boe6's vehicles: .inkwidget and .inkstyle - Animated UI\", section
+      \"Learning .inkwidget files\""
+    tags:
+      - vehicle
+      - inkwidget
+      - needle
+      - rotation
+      - logiccontroller
+    detail: "\"Some children elements may override this with a default value as a starting position, so
+      this needs to be changed as well. It's located in the `renderTransform > rotation` value in
+      the child inkCanvasWidget.\" The page's worked example uses -25 degrees at 0 speed and 205
+      degrees at full speed. Section name corrected 2026-09-07."
+  - id: cp2077.vehicles.dashboard-ui.inkstyle-linked-via-widget-arrays
+    claim: "\"The .inkstyle file sets the color/overlay of parts. It is linked through an .inkwidget via
+      it's rootWidget 'style' value, and its 'externalDependenciesForInternalItems' array.\""
+    status: community
+    source: "wiki.redmodding.org \"Boe6's vehicles: .inkwidget and .inkstyle - Animated UI\", section
+      \"Learning .inkwidget files\" (closing paragraphs)"
+    tags:
+      - vehicle
+      - inkstyle
+      - inkwidget
+      - dependency
+      - styling
+    detail: 'Spelling caution for a validator: the body text writes
+      `externalDependenciesForInternalItems` while the figure caption for the same field writes
+      `externalDependanciesForInternalItems` (with an "a"). The style path is `RDTDataViewModel >
+      libraryItems > Root > packageData > 0 > rootWidget > style`. An `inkStyleProperty` is
+      referenced back from the widget at `children > children > inkImageWidget > propertyManager >
+      bindings > 0`, with `propertyName` "tintColor" and `stylePath` the `propertyPath` set by the
+      `.inkstyle`. Section name corrected 2026-09-07.'
+  - id: cp2077.vehicles.dashboard-ui.imagewidget-two-part-atlas-reference
+    claim: '"To link an inkImageWidget to a part from the .inkatlas, two values are used":
+      `textureAtlas` (links to the `.inkatlas` file) and `texturePart` (links to the partName in the
+      `.inkatlas`). "The new .inkatlas path must be updated for every inkImageWidget."'
+    status: community
+    source: "wiki.redmodding.org \"Boe6's vehicles: .inkwidget and .inkstyle - Animated UI\", section
+      \"The .inkatlas file\""
+    tags:
+      - vehicle
+      - inkwidget
+      - inkatlas
+      - textureatlas
+      - texturepart
+    detail: 'Corrected 2026-09-07: the "a valid atlas with the wrong part name resolves to nothing"
+      clause is not on this page — that failure mode is recorded separately from the icons page as
+      cp2077.vehicles.dashboard-ui.atlaspartname-mismatch-is-silent. Section name corrected (there
+      is no "Texture & Image Linking" heading).'
+  - id: cp2077.vehicles.dashboard-ui.xbm-needs-tga-not-png-for-alpha
+    claim: '".xbm files that are used for a .inkwidget can be edited, but need a preserved alpha
+      channel. This means .png will not work. .tga files can be easily edited by both photoshop and
+      paint.net, and work well."'
+    status: community
+    source: "wiki.redmodding.org \"Boe6's vehicles: .inkwidget and .inkstyle - Animated UI\", section
+      \"The .inkatlas file\""
+    tags:
+      - vehicle
+      - xbm
+      - texture
+      - alpha-channel
+      - tga
+      - png
+      - gotcha
+    detail: 'TENSION with other verified facts, which are not changed by this: cp2077.ui.xbm-file-format
+      and cp2077.ui.icon-import-gamma-lift record a weapon mod shipping icons through a png -> xbm
+      WolvenKit CLI import that worked (its documented quirk being a gamma lift, not a lost alpha).
+      The two are reconcilable — this page is about dashboard widget textures that need alpha, the
+      weapon icons may not have needed one — but a validator should not treat "png never works for
+      .xbm" as general. Section name corrected 2026-09-07.'
+  - id: cp2077.vehicles.dashboard-ui.inkatlas-uv-percentage-confirms-existing
+    claim: Community page confirms cp2077.ui.icon-atlas-texture-resolution. "Inkatlas files don't slice
+      by pixel coordinates but by percentage as a float value between 0 and 1. The starting point is
+      the TOPLEFT corner, the ending point is the BOTTOMRIGHT corner." Each slot
+      (`inkTextureAtlasMapper`) has four coordinates.
+    status: community
+    source: "wiki.redmodding.org \"Game icons: .inkatlas files\", section \"Summary\"; corroborated by
+      \"Boe6's vehicles: .inkwidget and .inkstyle - Animated UI\", section \"The .inkatlas file\""
+    tags:
+      - inkatlas
+      - uv
+      - percentage
+      - coordinate-system
+      - icon
+    detail: 'Names cp2077.ui.icon-atlas-texture-resolution (knowledge/cyberpunk2077/ui.icons.yaml) as
+      the fact this confirms — that fact states the "displayed size = uv fraction x declared
+      textureResolution" formula but not that the underlying fraction is a plain 0-1 percentage
+      measured from the top-left. The vehicle page names the field carrying it: `RDTDataViewModel >
+      slots > 0/1/2 > parts > [part name] > clippingRectInUVCoords`, whose "Bottom/Left/Right/Top
+      values are the limits for the part image... entered as a float from 0 to 1". Section name
+      corrected 2026-09-07 (there is no "Coordinate System" heading).'
+  - id: cp2077.vehicles.dashboard-ui.inkatlas-three-resolution-slots
+    claim: '"Each inkatlas has three different inkTextureSlots, which support different texture
+      resolutions. For the purpose of modding, it is enough if you work with inkTextureSlot 0 (the
+      first one in the list)."'
+    status: community
+    source: 'wiki.redmodding.org "Game icons: .inkatlas files", section "`inkTextureSlot`s"'
+    tags:
+      - inkatlas
+      - texture-slot
+      - resolution
+    detail: "The vehicle dashboard page names the other two: at `RDTDataViewModel > slots > 0/1/2 >
+      texture`, \"The 1 and 2 slots are 1080p and 720p. We'll ignore them for now, they'll be
+      updated to match later.\" That lines up with the three-enum `textureResolution` set
+      (HD_1280_720, FullHD_1920_1080, UltraHD_3840_2160) recorded in
+      cp2077.ui.icon-atlas-texture-resolution, though neither source states outright that the slots
+      and the enum are the same mechanism. Section name corrected 2026-09-07."
+  - id: cp2077.vehicles.dashboard-ui.atlaspartname-mismatch-is-silent
+    claim: "Community page confirms cp2077.ui.icon-atlas-part-declaration and adds its failure mode:
+      \"Any atlasPartName in the `yaml` must correspond with the name of a part in the
+      inkTextureAtlasMapper. If the corresponding entry can't be found, an empty icon will be
+      displayed.\""
+    status: community
+    source: 'wiki.redmodding.org "Game icons: .inkatlas files", section "Inkatlas: Slot names"'
+    tags:
+      - inkatlas
+      - atlaspartname
+      - silent-failure
+      - gotcha
+    detail: Names cp2077.ui.icon-atlas-part-declaration (knowledge/cyberpunk2077/ui.icons.yaml), an
+      inferred fact that pairs `atlasResourcePath` with `atlasPartName`; the page's example UIIcon
+      record has exactly that shape. "Wrong case" was removed from the claim on 2026-09-07 as
+      unsourced. Section name corrected (there is no "Key Components > Slot Naming" heading).
+  - id: cp2077.vehicles.dashboard-ui.part-mapping-tab-needs-reopen
+    claim: 'Known WolvenKit quirk: the `Part Mapping` tab, which shows which parts of an image
+      correspond to each slot name, only appears once an existing xbm is hooked up — and "As of
+      Wolvenkit 8.11.1, this requires reopening the file".'
+    status: community
+    source: 'wiki.redmodding.org "Game icons: .inkatlas files", section "`inkTextureSlot`s" (warning
+      hint) and section "Inkatlas: Slot names" (figure caption)'
+    tags:
+      - inkatlas
+      - wolvenkit
+      - part-mapping
+      - refresh
+      - gotcha
+    detail: "Corrected 2026-09-07: the page describes the tab not APPEARING until the file is reopened,
+      not showing stale regions after an edit, and says \"As of Wolvenkit 8.11.1\" rather than
+      \"8.11.1+\". The figure caption gives the same fix from the other end: \"If you don't have a
+      partsMapping tab, check your texture path and reopen the InkAtlas\"."
+  - id: cp2077.vehicles.dashboard-ui.docs-flagged-incomplete
+    claim: 'The vehicle dashboard guide opens by flagging its own limits: ".inkwidget and .inkstyle
+      files are not currently well documented. (3/11/25) This guide will only show how to edit an
+      existing vehicle speedometer / gauge cluster for a vehicle."'
+    status: community
+    source: "wiki.redmodding.org \"Boe6's vehicles: .inkwidget and .inkstyle - Animated UI\", info hint
+      at the top of the page"
+    tags:
+      - vehicle
+      - inkwidget
+      - inkstyle
+      - documentation-gap
+    detail: 'Kept as a scope flag on every other fact in this file: none of them should be read as
+      covering authoring a dashboard from scratch. Section name corrected 2026-09-07 (there is no
+      "Important Caveat" heading).'

package/knowledge/cyberpunk2077/vehicles.entities.yaml

@@ -0,0 +1,195 @@
+game: cyberpunk2077
+topic: vehicles.entities
+title: Vehicle .ent/.app structure, naming and drive-model tuning
+facts:
+  - id: cp2077.vehicles.entities.four-core-file-roles
+    claim: "Per the vehicle guide's file-type list: \".ent file is the base file of a vehicle. It
+      contains all settings and child files\"; \".app is the vehicle's appearances settings\";
+      \".rig has 3D information for how the .mesh files are linked and move\"; \".mesh is a 3d file,
+      used for vehicle body parts\"."
+    status: community
+    source: "wiki.redmodding.org \"Boe6's vehicles: What you need to know\", section \"You should know
+      (most of) your mod file types\""
+    tags:
+      - vehicle
+      - ent
+      - app
+      - rig
+      - mesh
+      - file-structure
+    detail: "The same list covers the rest of a vehicle's files: `.xbm` raw textures, `.mlsetup`
+      texture-set settings, `.mlmask` zipped mask/finish layers and normal maps, `.inkatlas`
+      reference texture information, `.inkwidget` texture layering/position/animation, `.yaml`
+      TweakDB items, `.json` string localization, `.phys` collision/interaction bounds. Section name
+      corrected 2026-09-07 (there is no \"File Structure Overview\" heading)."
+  - id: cp2077.vehicles.entities.tweak-name-from-ent-filename
+    claim: '"The tweak name is generated out of the ent file name without the appearance":
+      `v_sportbike2_arch_nemesis_basic_01.ent` yields the record
+      `Vehicle.v_sportbike2_arch_nemesis`.'
+    status: community
+    source: 'wiki.redmodding.org "Cheat Sheet: Vehicles", section "List of vehicles" (the worked example
+      above the table)'
+    tags:
+      - vehicle
+      - naming
+      - tweakdb
+      - ent-filename
+    detail: 'Page title and section name corrected 2026-09-07 (the page is "Cheat Sheet: Vehicles" and
+      has no "Naming Convention" heading).'
+  - id: cp2077.vehicles.entities.master-mapping-files
+    claim: "`base\\vehicles\\base_types_map.csv`, referenced from `base\\appearances_mappings.json`,
+      \"maps vehicle names to their respective .ent files. The names are defined in each vehicle's
+      .app file as `baseEntityType`.\""
+    status: community
+    source: 'wiki.redmodding.org "Cheat Sheet: Vehicles", section "List of vehicles" (opening sentence)'
+    tags:
+      - vehicle
+      - mapping-file
+      - base-types-map
+      - appearances-mappings
+      - baseentitytype
+    detail: "Corrected 2026-09-07: the `baseEntityType` link was added and the claim that the cheat
+      sheet is itself built by reading these two files was removed as unsourced."
+  - id: cp2077.vehicles.entities.filename-regex-archived
+    claim: "`base\\vehicles\\vehicle_filename_parsing.json` defines a regex for allowable vehicle .ent
+      filenames —
+      `(?:v_)?([a-zA-Z]+|av)\\d?_([a-zA-Z]+)_(?:[a-zA-Z]+(?:_[a-zA-Z]+)*)__(?:int|ext)\\d{2}_([a-zA\
+      -Z]+(?:_[a-zA-Z]+)*)_\\d{2}.*\\.ent` — whose group 1 is the base (`av` -> Aerial; `sport`,
+      `standard`, `utility` -> Car), group 2 the manufacturer category, group 3 the partType. The
+      wiki page carrying this is marked ARCHIVED/outdated and notes the regex does not match
+      vehicles such as the Type 66 or the 911, because numbers are not permitted in group 2."
+    status: community
+    source: 'wiki.redmodding.org "Archived: Vehicle Filename Parsing" (whole page)'
+    tags:
+      - vehicle
+      - naming
+      - filename-prefix
+      - regex
+      - archived
+    detail: Renamed from cp2077.vehicles.entities.filename-prefix-conventions and re-sourced on
+      2026-09-07. The previous claim's pattern
+      `v_[type][number]_[manufacturer]_[model]_[variant]_[number].ent` appears on no wiki page, and
+      its statement that Phantom Liberty's special vehicles live under `ep1\vehicles\special\`
+      generalised from a single row of the vehicles cheat sheet (the fake Trauma Team Manticore,
+      `ep1\vehicles\special\av_militech_manticore_fake_trama.ent`); other EP1 vehicles in the same
+      table, such as `v_standard2_archer_hella_ep1__basic_01.ent`, are not under that path. The
+      `av_` prefix for aerial vehicles is real and is what group 1's `av` -> Aerial mapping encodes.
+  - id: cp2077.vehicles.entities.guide-prerequisites
+    claim: "The vehicle-from-scratch guide's stated prerequisites are: WolvenKit installed and set up,
+      the WolvenKit Blender IO Suite, and a text editor; TweakXL (required — \"without it you won't
+      be able to load Vehicle tweak at all\"), ArchiveXL, Virtual Car Dealer and Material and
+      Texture override installed in the game; the Cyberpunk 2077 glTF Importer plugin plus Blender
+      skills including knowing \"the difference between object origin, world origin, and the blender
+      cursor\"; and a photo editor with `.tga` and alpha-channel support."
+    status: community
+    source: "wiki.redmodding.org \"Boe6's vehicles: What you need to know\", sections
+      \"Prerequirements\", \"Mod requirements\", \"You know your way around blender\" and
+      \"Knowledge of a photo editor of your choice.\""
+    tags:
+      - vehicle
+      - prerequisite
+      - blender
+      - gltf-importer
+      - tweakxl
+      - difficulty
+    detail: 'Merged on 2026-09-07 from cp2077.vehicles.entities.rigging-prerequisite-tooling and the
+      narrative-only cp2077.vehicles.entities.declared-most-complex-mod-type, and re-sourced
+      (neither "Rigging Prerequisites" nor "File Organization Pattern" is a heading on this page).
+      The scoping framing those carried is real: "A new standalone car is about the most complex
+      Cyberpunk mod you can make", "Due to the high complexity, this is not a good first mod", and
+      the guide asks new modders to complete the linked tutorials in the green boxes first. The page
+      also gives a model budget: "Vanilla game cars range between 80k and 120k vertices."'
+  - id: cp2077.vehicles.entities.chassis-and-total-mass-must-match
+    claim: In `gamedataVehicleDriveModelData_Record`, `chassis_mass` and `total_mass` are both floats in
+      LBS with a sample value of 1750.0. The reference states it makes sense that `chassis_mass` is
+      always <= `total_mass`, that the role of the difference between them is unclear, and that
+      "experiments show a lower car stability at high speeds when these two values are not equal".
+    status: community
+    source: 'wiki.redmodding.org "Cheat Sheet: Vehicle Properties", section
+      "gamedataVehicleDriveModelData_Record" (the `chassis_mass` and `total_mass` rows)'
+    tags:
+      - vehicle
+      - drive-model
+      - mass
+      - stability
+      - gotcha
+    detail: 'Section name corrected 2026-09-07 (there is no "Critical Units & Gotchas" section; the
+      speed notes live under "Summary" and the field descriptions in per-record tables). Page title
+      is "Cheat Sheet: Vehicle Properties".'
+  - id: cp2077.vehicles.entities.internal-speed-unit-conversion
+    claim: The game engine's internal vehicle speed unit "is about 2.4017577 mph (3.86525568 km/h)" — so
+      a dynamic-downforce `maxSpeed` of 100 is about 240 mph, or 386 km/h.
+    status: community
+    source: 'wiki.redmodding.org "Cheat Sheet: Vehicle Properties", section "Summary > Vehicle speed
+      units"'
+    tags:
+      - vehicle
+      - drive-model
+      - speed
+      - units
+    detail: "The section is labelled \"N.B. Original research.\" `maxSpeed` in
+      `gamedataDynamicDownforceHelper_Record` has a sample value of 40.0 and is described as \"(?)
+      The speed up to which the dynamic downforce graph stretches. Unit: engine's internal.\" Split
+      from a compound fact on 2026-09-07; see
+      cp2077.vehicles.entities.displayed-mph-is-double-actual for the separate display-side
+      conversion."
+  - id: cp2077.vehicles.entities.displayed-mph-is-double-actual
+    claim: Separately from the internal unit, "the originally displayed mph value in Cyberpunk 2077
+      vehicles is about double the actual mph speed. For example, when the game shows '200' mph,
+      that is about 100 mph (160.934 km/h)." One unit of in-game space is one meter.
+    status: community
+    source: 'wiki.redmodding.org "Cheat Sheet: Vehicle Properties", section "Summary > Vehicle speed
+      units"'
+    tags:
+      - vehicle
+      - drive-model
+      - speed
+      - units
+      - gotcha
+    detail: Split out on 2026-09-07. The previous combined fact claimed a `maxSpeed` of 100 "reads as
+      roughly 240 mph on the dashboard"; the page gives 240 mph / 386 km/h as a real conversion of
+      the internal unit, and separately says the dashboard reads about double the actual speed, so
+      the two corrections must not be conflated.
+  - id: cp2077.vehicles.entities.speed-breaker-needs-1-63-to-adjust
+    claim: "\"The game has a speed breaker, which resets the vehicle's speed to 0 if it hits a certain
+      threshold. This threshold is around or somewhat lower than 100 of the game engine's internal
+      speed units. It is possible to remove (or rescale?) this speed breaker threshold in version
+      1.63 of the game, e.g., with the LTBF mod.\""
+    status: community
+    source: 'wiki.redmodding.org "Cheat Sheet: Vehicle Properties", section "Summary > Speed
+      breaker/limiter"'
+    tags:
+      - vehicle
+      - drive-model
+      - speed-breaker
+      - version-floor
+      - gotcha
+    detail: "Corrected 2026-09-07: the page says \"in version 1.63 of the game\", not \"1.63 and later\"
+      as previously recorded, and hedges the rescale with a question mark. The section is labelled
+      \"N.B. Original research.\" 1.63 is the game's marketing version but is a claim about which
+      build the removal was done on, not an observation date, so it stays in the claim rather than
+      becoming `verified_on`."
+  - id: cp2077.vehicles.entities.drive-model-descriptions-are-trial-and-error
+    claim: Steering fields on `gamedataVehicleDriveModelData_Record` have sample values
+      `maxWheelTurnDeg` 45.0 ("Determines the maximum steering angle"), `wheelTurnMaxAddPerSecond`
+      100.0 ("The maximum speed of steering") and `wheelTurnMaxSubPerSecond` 130.0 ("The maximum
+      speed of the steering wheel/handles returning to the neutral position"). Motorcycles use a
+      separate `gamedataBikeDriveModelData_Record` whose `bikeMaxTilt` 38.0, `bikeTiltSpeed` 103.0
+      and `bikeTiltReturnSpeed` 103.0 descriptions all begin with "(?)", which the page's legend
+      defines as "needs verifying".
+    status: community
+    source: 'wiki.redmodding.org "Cheat Sheet: Vehicle Properties", sections "Summary" (legend and N.B.)
+      and "gamedataVehicleDriveModelData_Record" (including the motorcycle sub-table)'
+    tags:
+      - vehicle
+      - drive-model
+      - tuning
+      - unverified
+      - steering
+      - motorcycle
+    detail: "Renamed from cp2077.vehicles.entities.tuning-fields-flagged-as-community-typical and
+      corrected on 2026-09-07: the numbers are the reference's \"Sample Value\" column, not
+      \"community-observed typical values\"; the three steering fields are NOT flagged \"(?)\" while
+      all three bike fields are; and the previous claim omitted the 103.0 values. The page-level
+      caveat covers everything anyway: \"Descriptions of the properties are conclusions of multiple
+      contributors' trial and error process... there is no guarantee of it being so.\""

package/knowledge/cyberpunk2077/vehicles.wiring.yaml

@@ -0,0 +1,137 @@
+game: cyberpunk2077
+topic: vehicles.wiring
+title: How a vehicle's TweakDB record, entity files and appearance-mapping resolve together
+facts:
+  - id: cp2077.vehicles.wiring.tweak-name-from-ent-filename
+    claim: A vehicle's TweakDB record name is generated by taking its `.ent` filename and stripping the
+      trailing appearance/variant segment; the documented example is
+      `v_sportbike2_arch_nemesis_basic_01.ent` -> TweakDB record `Vehicle.v_sportbike2_arch_nemesis`
+      (the `_basic_01` suffix is dropped).
+    status: community
+    source: CDPR-Modding-Documentation/Cyberpunk-Modding-Docs
+      for-mod-creators-theory/references-lists-and-overviews/vehicles/vehicles.md, section "List of
+      vehicles"
+    tags:
+      - vehicles
+      - tweakdb
+      - naming-convention
+      - .ent
+  - id: cp2077.vehicles.wiring.entitytemplatepath-ties-record-to-resources
+    claim: The vehicle root TweakDB record's `entityTemplatePath` field (type `raRef:CResource`) is the
+      field that ties the TweakDB record to the actual resource files used for rendering the
+      vehicle; the vanilla template record `Vehicle.vehicle_template` points it at
+      `base\vehicles\common\gameplay\vehicle_template.ent`.
+    status: community
+    source: CDPR-Modding-Documentation/Cyberpunk-Modding-Docs
+      for-mod-creators-theory/references-lists-and-overviews/vehicles/vehicle-record.md, section
+      "Vehicle template" (hint above the yaml block, and the `entityTemplatePath` member)
+    tags:
+      - vehicles
+      - tweakdb
+      - entitytemplatepath
+      - entity-resource-link
+  - id: cp2077.vehicles.wiring.affiliation-and-driving-are-tweakdbid-refs
+    claim: In the vehicle root TweakDB record template, `affiliation` (default `Factions.Unaffiliated`)
+      and `driving` (default `Driving.Default_4w`) are `TweakDBID` references into other TweakDB
+      record groups (`Factions.*` and `Driving.*` respectively), not inline values — a new vehicle
+      record normally points these at existing vanilla sibling records rather than defining new
+      ones.
+    status: community
+    source: CDPR-Modding-Documentation/Cyberpunk-Modding-Docs
+      for-mod-creators-theory/references-lists-and-overviews/vehicles/vehicle-record.md, section
+      "Vehicle template" (yaml block, `affiliation` and `driving` members)
+    tags:
+      - vehicles
+      - tweakdb
+      - tweakdbid
+      - affiliation
+      - driving
+  - id: cp2077.vehicles.wiring.appearance-mappings-registers-vehicle-lookup-files
+    claim: "Historically (pre-ArchiveXL era), `base\\appearance_mappings.json` registered, for the
+      `Vehicle` entity type, the four supporting lookup files the game used to resolve a vehicle
+      .ent's category and parts: `base\\vehicles\\base_types_map.csv` (base type lookup),
+      `base\\vehicles\\categories.csv`, `base\\vehicles\\parts.csv` and
+      `base\\vehicles\\parts_categories.json`, plus a filename-parsing regex file
+      `base\\vehicles\\vehicle_filename_parsing.json`."
+    status: community
+    source: CDPR-Modding-Documentation/Cyberpunk-Modding-Docs
+      for-mod-creators-theory/references-lists-and-overviews/vehicles/archive/appearances-mappings.md
+      (key/value table)
+    tags:
+      - vehicles
+      - appearance-mappings
+      - legacy
+      - csv
+      - lookup
+    detail: This page is marked with the wiki's own "outdated info" banner image and titled "Archived:"
+      — treat as historical/legacy documentation of how vanilla resolves vehicle categories, not a
+      current authoring workflow; ArchiveXL's own manifest/factory mechanism
+      (cp2077.archivexl.manifest.resource-patch-key and siblings) is the current path for adding
+      vehicles as mods.
+  - id: cp2077.vehicles.wiring.filename-parsing-regex-has-known-gaps
+    claim: The (now-archived) vehicle filename-parsing regex
+      `(?:v_)?([a-zA-Z]+|av)\d?_([a-zA-Z]+)_(?:[a-zA-Z]+(?:_[a-zA-Z]+)*)__(?:int|ext)\d{2}_([a-zA-Z]+(?:_[a-zA-Z]+)*)_\d{2}.*\.ent`
+      does not match every vanilla vehicle filename — the page notes it fails for names containing
+      digits in the manufacturer group (e.g. "Type 66" or "911") because the regex's manufacturer
+      capture group disallows digits, and it is unknown whether this parsing is even still used by
+      the game.
+    status: community
+    source: CDPR-Modding-Documentation/Cyberpunk-Modding-Docs
+      for-mod-creators-theory/references-lists-and-overviews/vehicles/archive/vehicle-filename-parsing.md
+    tags:
+      - vehicles
+      - filename-parsing
+      - regex
+      - gap
+      - legacy
+    detail: Also archived/outdated-marked. Not useful as a validated naming rule for new vehicle files —
+      cited only for the documented gap, which is itself useful context for why naming ModWright's
+      own vehicle fixtures after this pattern is not guaranteed to round-trip through the legacy
+      resolver.
+  - id: cp2077.vehicles.wiring.parts-categories-three-groups
+    claim: "Vehicle part-name tokens used in `.mesh`/`.ent` filenames are grouped into three categories:
+      Interior (`base`, `steering_wheel`, `pedals`), Exterior (`base`, `bumper_f`, `bumper_b`,
+      `hood`, `trunk`, `door_fl`, `door_fr`, `door_bl`, `door_br`, `fuelcap`, `fuelport`) and Wheel
+      (`wheel`); `base` is shared between Interior and Exterior."
+    status: community
+    source: CDPR-Modding-Documentation/Cyberpunk-Modding-Docs
+      for-mod-creators-theory/references-lists-and-overviews/vehicles/archive/parts-and-parts-categories.md
+    tags:
+      - vehicles
+      - parts
+      - naming-convention
+      - legacy
+    detail: Also marked archived/outdated by the source wiki; kept as a cite-only naming reference for
+      part tokens, not a guarantee the list is exhaustive for the current game version.
+  - id: cp2077.vehicles.wiring.mounted-weapon-shot-raises-a-gunshot
+    claim: Each shot of a vehicle's mounted weapon is followed by a VehicleMountedWeaponShootEvent
+      (weapon and slot record ids) on the vehicle, and the vehicle component answers it with a
+      gunshot stimulus from the vehicle (50 m) and from the mounted player. The stimulus is raised
+      whether or not the shot's aim was ever set, so NPCs can turn on a vehicle whose shots are not
+      seen.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicles
+      - weapons
+      - mounted
+      - gunshot
+      - stimulus
+  - id: cp2077.vehicles.wiring.mounted-weapon-player-aim-gates
+    claim: An armed vehicle's weapons fire toward a target the vehicle holds at +0xB14. For a player
+      driver it is written by the armed car's aim update (vtable +0x3A0, fn_14698E4), which returns
+      without writing unless every active weapon's state (the object at weapon +0x278, field +0x68)
+      reads 100 and an aim source (a camera, +0x528) is held. The source's ray, cast forward, gives
+      the target. Without the target the fire tick still shoots from each weapon object's position
+      and raises its shoot event.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - vehicles
+      - weapons
+      - mounted
+      - aim
+      - native
+      - ghidra