modwright 0.1.0

package/knowledge/cyberpunk2077/drones.control.yaml

@@ -0,0 +1,552 @@
+game: cyberpunk2077
+topic: drones.control
+title: Drones as script sees them - type, component, locomotion, altitude, ground and geometry queries
+facts:
+  - id: cp2077.drones.control.npctype-enum
+    claim: gamedataNPCType is Android 0, Any 1, Cerberus 2, Chimera 3, Device 4, Drone 5, Human 6, Mech
+      7, Spiderbot 8, Count 9. ScriptedPuppet.IsDrone() is GetNPCType() == Drone; IsMechanical() is
+      Android, Drone or Mech, or the Ability.IsMechanical gameplay ability.
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 orphans.swift:4928;
+      cyberpunk/puppet/scriptedPuppet.swift:1147, :1332
+    tags:
+      - drone
+      - npctype
+      - ismechanical
+      - scriptedpuppet
+  - id: cp2077.drones.control.same-ai-controller-as-humans
+    claim: "Every ScriptedPuppet, drones included, carries one AI controller field `m_aiController:
+      ref<AIHumanComponent>` returned by GetAIControllerComponent(); there is no drone-specific AI
+      component class in the scripts. A script lever that toggles that component (the mod's
+      mover-defeat) or reads its movement parameters therefore applies to a drone unchanged."
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 cyberpunk/puppet/scriptedPuppet.swift:137, :1018;
+      core/components/aiComponent.swift:252
+    tags:
+      - drone
+      - aihumancomponent
+      - ai-controller
+      - mover-defeat
+  - id: cp2077.drones.control.dronecomponent-components
+    claim: 'DroneComponent (a ScriptableComponent) resolves three components by name on its owner:
+      "Senses" (SenseComponent), "npcCollision" and "playerOnlyCollision" (SimpleColliderComponent);
+      the player-only collider is toggled off on game attach and back on only for a dead body whose
+      record sets `.keepColliderOnDeath`.'
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      core/components/scriptComponents/droneComponent.swift:26-46, :81-85
+    tags:
+      - drone
+      - dronecomponent
+      - senses
+      - collider
+  - id: cp2077.drones.control.locomotion-wrappers
+    claim: "A drone's movement animation is chosen by anim wrapper weights named DroneLocomotion_Walk,
+      DroneLocomotion_Run and DroneLocomotion_Sprint (the others zeroed, the chosen one set to 1).
+      The public static DroneComponent.SetLocomotionWrappers(owner, movementType: CName) queues an
+      ApplyDroneLocomotionWrapperEvent that applies them, so a script can pick the flight animation
+      without the AI."
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      core/components/scriptComponents/droneComponent.swift:168-188
+    tags:
+      - drone
+      - animation
+      - wrapper
+      - locomotion
+  - id: cp2077.drones.control.move-commands-force-walk
+    claim: The AI move command handlers (move-to, move-on-spline, the patrol task) force a drone's
+      movementType to moveMovementType.Walk and only switch the locomotion wrapper to the requested
+      type, so a drone's one effective movement parameter set is its Walk one
+      (GetMovementParams(Walk)); "Run" and "Sprint" are animation wrappers on a drone, not speeds.
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      cyberpunk/ai/commands/aiMoveToCommandHandler.swift:52-55, :112-115, :330-333;
+      cyberpunk/ai/Tasks/PatrolControllerTask.swift:55
+    tags:
+      - drone
+      - movement
+      - movementparameters
+      - walk
+  - id: cp2077.drones.control.movementparameters-struct
+    claim: MovementParameters is a native struct with type (moveMovementType), maxSpeed, acceleration,
+      deceleration and rotationSpeed; the AI component's GetMovementParams(type) returns it and
+      reads fine with the component toggled off (the mod measured 1.532 m/s on an android with the
+      AI off).
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 orphans.swift:49289;
+      core/components/aiComponent.swift:252
+    tags:
+      - movementparameters
+      - rotationspeed
+      - aicomponent
+  - id: cp2077.drones.control.altitude-is-an-anim-feature
+    claim: "A vanilla drone's altitude change is an animation feature, not a mover write:
+      AISubActionDroneModifyAltitude applies AnimFeature_DroneActionAltitudeOffset.desiredOffset
+      (default 0) on the animgraph input \"ActionAltitudeOffset\" through
+      AnimationControllerComponent.ApplyFeatureToReplicate, after the record's Delay, and resets it
+      to 0 on deactivate. A script can send the same feature to lift or lower the body relative to
+      where the mover holds it."
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 core/ai/actions/tweakAISubActions.swift:6185-6212;
+      orphans.swift:48807; core/components/animationControllerComponent.swift:43
+    tags:
+      - drone
+      - altitude
+      - animfeature
+      - applyfeaturetoreplicate
+  - id: cp2077.drones.control.procedural-feature-from-record
+    claim: "On attach, DroneComponent reads the drone's Character record floats .mass, .sizeFront,
+      .sizeBack, .sizeLeft, .sizeRight, .walkTiltCoefficient, .massNormalizedCoefficient,
+      .tiltAngleOnSpeed, .speedIdleThreshold, .startingRecoveryBalance, .pseudoAcceleration,
+      .turnInertiaDamping and .combatDefaultZOffset into an AnimFeature_DroneProcedural applied 0.2
+      s later on the input \"DroneProcedural\" (class defaults: mass 100, size front 1.5 / back -1.5
+      / left 1.2 / right -1.2, tilt angle on speed 40). The hover bob and the tilt on speed are the
+      animgraph's, driven by these."
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      core/components/scriptComponents/droneComponent.swift:136-166; orphans.swift:46700-46740
+    tags:
+      - drone
+      - animfeature
+      - procedural
+      - tweakdb
+    detail: The size floats describe the animated hull, not a collider; a collision test should not
+      trust them for more than an order of magnitude.
+  - id: cp2077.drones.control.poses-by-high-level-state
+    claim: DroneComponent applies DronePose.Combat (1) when the high-level state becomes Combat or
+      Alerted and DronePose.Relaxed (0) otherwise, as AnimFeature_DroneStateAnimationData.statePose
+      on the input "DroneStateAnimationData"; the AI events "CombatPose" / "RelaxedPose" do the
+      same. Alerted also re-applies the Walk wrapper.
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      core/components/scriptComponents/droneComponent.swift:57-79; orphans.swift:343
+    tags:
+      - drone
+      - pose
+      - highlevelstate
+  - id: cp2077.drones.control.isonground-geometry-query
+    claim: "NavigationSystem.IsOnGround(target, opt queryLength) is a static-geometry probe, not a
+      navmesh test: a GeometryDescriptionQuery with refPosition 0.1 m above the body along its up
+      vector, refDirection (0,0,-1), the filter QueryFilter.AddGroup(n\"Static\"),
+      primitiveDimension (0.1, 0.1, queryLength) with queryLength 0.2 when 0, run through
+      GameInstance.GetSpatialQueriesSystem(game).GetGeometryDescriptionSystem().QueryExtents; true
+      when the result's queryStatus is worldgeometryDescriptionQueryStatus.OK."
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 core/systems/navigationSystem.swift:41-58;
+      orphans.swift:7370
+    tags:
+      - navigation
+      - isonground
+      - geometry-query
+      - spatial-queries
+    detail: The same query along a movement direction is a 3-D wall or ceiling test that a flying body
+      can use where the navmesh calls (GetNearestNavmeshPointBelow, FindWallInLineForCharacter) do
+      not apply.
+  - id: cp2077.drones.control.geometry-query-api
+    claim: GeometryDescriptionQuery (native class) has refPosition, refDirection, refUp,
+      primitiveDimension, primitiveRotation, maxDistance, maxExtent, raycastStartDistance,
+      probingPrecision, probingMaxDistanceDiff, probingMaxHeight, maxProbes and filter (QueryFilter;
+      ALL(), ZERO(), AddGroup(out filter, group)); GeometryDescriptionResult carries queryStatus
+      (OK, NoGeometry, UpVectorSameAsDirection), collisionNormal, distanceVector,
+      topPoint/topNormal, behindPoint/behindNormal, obstacleDepth and up/down/top extents.
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 core/world/geomDescription.swift:2-26;
+      orphans.swift:27612-27700, :7370
+    tags:
+      - geometry-query
+      - spatial-queries
+      - collision
+  - id: cp2077.drones.control.aerial-death-ragdoll
+    claim: When a drone is incapacitated while NavigationSystem.IsOnGround(this) is false, NPCPuppet
+      sets ragdollNoGroundThreshold -1 on its uncontrolled movement event and delays a forced
+      ragdoll by the record's .airDeathRagdollDelay (default 1.0 s); DroneComponent's own OnDeath
+      starts uncontrolled movement with ragdollOnCollision true and switches the appearance to
+      "drone_destroyed".
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 cyberpunk/NPC/NPCPuppet.swift:3298-3301;
+      core/components/scriptComponents/droneComponent.swift:99-121
+    tags:
+      - drone
+      - death
+      - ragdoll
+  - id: cp2077.drones.control.background-combat-destinations
+    claim: In the background combat command's ChangeCover step a drone is given a desired destination
+      where a human is given a desired cover; drones do not take covers.
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3
+      cyberpunk/ai/commands/aiBackgroundCombatCommand.swift:262-268
+    tags:
+      - drone
+      - combat
+      - cover
+  - id: cp2077.drones.control.hud-drone-widget
+    claim: hudDroneController (an inkHUDGameController in hud_drone.swift) fills a date, a timer and the
+      camera-HUD camera-id localization string and listens to PlayerStateMachine.ZoomLevel; no
+      script in the tree instantiates or references it, so it is a camera-HUD frame available to a
+      widget, not a mechanism.
+    status: verified
+    verified_on: "2.31"
+    source: codeberg adamsmasher/cyberpunk@a2e6bb3 cyberpunk/UI/hud/custom/hud_drone.swift
+    tags:
+      - drone
+      - hud
+      - ink
+  - id: cp2077.drones.control.nojump-checked-in-psm
+    claim: GameplayRestriction.NoJump is enforced inside the player state machine's transition
+      conditions (a status-effect tag check in defaultTransition), not by filtering input; the Jump
+      action itself is still dispatched to input listeners, the way MoveY reaches them under
+      NoMovement.
+    status: inferred
+    verified_on: "2.31"
+    source: ModWright research
+    tags:
+      - input
+      - restriction
+      - nojump
+      - listener
+    detail: To be confirmed by an input-listener probe listing "Jump" and "Crouch" while the player is
+      held under the restriction; if they do not arrive, Input Loader's custom actions are the
+      fallback (the route Let There Be Flight uses for its six-axis mode).
+  - id: cp2077.drones.control.records-in-amm-list
+    claim: "Appearance Menu Mod's public TweakDB record list names these drone and mech Character
+      records: Character.arasaka_base_drone_octant, Character.sts_wat_kab_101_drone_security,
+      Character.q112_camera_drone, Character.sq025_delamain_drone_bombus_speaker,
+      Character.q104_pp_drones, Character.q104_arasaka_av_droid,
+      Character.q115_arasaka_jungle_droid_rifle; mechs Character.ncpd_minotaur,
+      Character.q003_militech_mech, Character.q114_arasaka_netnest_mech_friendly_quest. The list is
+      partial (no Wyvern or Griffin entry by that name)."
+    status: community
+    source: MaximiliumM/appearancemenumod Resources/TweakDB Records.html (main, read 2026-09-21)
+    tags:
+      - drone
+      - mech
+      - tweakdb
+      - character-record
+      - amm
+    detail: Superseded in scope by cp2077.drones.control.record-trees (the full list from a local
+      vanilla index, 2026-09-22); kept as the public source a cloud session can read without an
+      install.
+    related:
+      - cp2077.drones.control.record-trees
+      - cp2077.drones.control.template-paths
+  - id: cp2077.drones.control.record-trees
+    claim: In the 2.31 TweakDB, Character.Drone_NPC_Base has 235 descendants and Character.Mech_NPC_Base
+      50, both under Character.Mechanical_NPC_Base (399 descendants in all, androids included). The
+      four chassis bases are Character.Drone_Octant_Base (actionMap DroneOctantArchetype.Map, mass
+      120, sizeFront/Back ±1.5, sizeLeft/Right ±1.2, tiltAngleOnSpeed 10),
+      Character.Drone_Wyvern_Base (DroneArchetype.Map, mass 20, ±0.75 × ±0.5, combatDefaultZOffset
+      -0.15), Character.Drone_Griffin_Base (DroneGriffinArchetype.Map, mass 2, 0.33/-0.66 × ±1) and
+      Character.Drone_Bombus_Base (DroneBombusArchetype.Map, mass 70, 0.2/-0.33 × ±0.33,
+      reactionPreset Mechanical_NonCombat); every faction drone record derives from one of them
+      (arasaka_base_drone_octant, militech_drone_wyvern_hard, kangtao_drone_griffin_medium,
+      ncpd_drone_bombus_medium, ...). Character.Drone_NPC_Base_Old has one child,
+      Character.e3_2019_scene_drone (archetype drone_deprecated).
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - drone
+      - mech
+      - tweakdb
+      - character-record
+      - inheritance
+  - id: cp2077.drones.control.objectactions-inherited-from-mechanical-base
+    claim: "No drone record in the Drone_NPC_Base tree declares its own objectActions: Drone_NPC_Base
+      and the four chassis bases inherit the 36-entry list of Character.Mechanical_NPC_Base
+      unchanged, so an !append on Mechanical_NPC_Base reaches all 235 drones.
+      Character.Mech_NPC_Base and Character.Android_NPC_Base each add two takedown entries as an
+      append (contributors Mechanical_NPC_Base then the base itself), not a re-declaration. The only
+      mechanicals that re-declare the list are Character.q110_boxing_robot,
+      Character.ep1_combat_zone_non_combat_droid, Character.q304_market_minotaur and
+      Character.q306_black_ops_chopper."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - drone
+      - mech
+      - objectactions
+      - quickhack
+      - tweakdb
+  - id: cp2077.drones.control.template-paths
+    claim: The drone and mech Character records' entityTemplatePath values are
+      ep1\vehicles\special\av_zetatech_octant__basic_01_ep1.ent (Octant base and every faction
+      Octant), ep1\vehicles\special\av_militech_wyvern__basic_01_ep1.ent (Wyvern base),
+      ep1\vehicles\special\av_militech_griffin__basic_01_ep1.ent (Griffin base),
+      base\vehicles\special\av_zetatech_bombus__basic.ent (Bombus base),
+      ep1\vehicles\special\av_ep1_bombus__basic.ent and av_ep1_wyvern__basic_01.ent (Kurtz and
+      friendly open-world variants), ep1\vehicles\special\av_nusa_griffin__basic_01.ent (q301),
+      ep1\mechanical\mech\mch_003__minotaur_ep1.ent (Mech base) and
+      ep1\mechanical\ep1_mch_003__minotaur.ent (Kurtz and Dogtown prevention), plus one-off quest
+      templates. All eight ep1 files live in archive\pc\ep1\ep1_2_gamedata.archive (not the
+      nightcity archive); the base-game copies
+      (base\vehicles\special\av_zetatech_octant__basic_01.ent, av_militech_wyvern__basic_01.ent,
+      av_militech_griffin__basic_01.ent, base\mechanical\mech\mch_003__minotaur.ent) are in
+      basegame_4_appearance.archive and referenced by a few quest records.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - drone
+      - mech
+      - entity-template
+      - archive
+      - archivexl
+      - patch-list
+    detail: ModWright's index lists resources from archive\pc\content only (32 archives); archive\pc\ep1
+      is not indexed, so lookup kind=resource answers 0 for every ep1 path. Indexing archive\pc\ep1
+      is open work for ModWright.
+  - id: cp2077.drones.control.templates-have-head-slot-on-base
+    claim: The drone chassis templates (Octant, Wyvern, Griffin, both Bombus) each carry an
+      entSlotComponent named Item_Attachment_Slot whose slots include Head, Center, Perception,
+      Chest, RightHand and ScannerRoot on the root bone "base" (WeaponRight/WeaponLeft on the gun or
+      wing bones); the Minotaur templates carry the humanoid slot set with Head on upper_body_01. An
+      entHardTransformBinding to Item_Attachment_Slot / Head therefore has a target on every drone
+      and mech, at the hull's origin in the hull's own frame.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - drone
+      - mech
+      - entity-template
+      - slot
+      - item_attachment_slot
+      - camera-patch
+    detail: This contradicts an earlier (2026-09-21) assumption that a drone lacks the slot; a mod's
+      existing camera patch binds on a drone as is, so extending the XL patch list suffices instead
+      of adding a root-relative second entity.
+  - id: cp2077.drones.control.templates-components
+    claim: Every drone chassis template carries DroneComponent, a moveDroneMotionPlannerComponent with
+      snapToGround false (the Minotaur has the plain moveMotionPlannerComponent with snapToGround
+      true), moveComponent, movePoliciesComponent, AIHumanComponent, a gameHumanoidBody (baseHeight
+      1.8, basePersonalSpace 1.2 on the Octant, 0.35 on the Wyvern) and an npcCollision collider.
+      The second collider is named playerOnlyCollision only on the Octant; the Wyvern and both
+      Bombus templates name it playerCollision and the Griffin has none, so DroneComponent's lookup
+      of "playerOnlyCollision" resolves nothing on three of the four chassis.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - drone
+      - mech
+      - entity-template
+      - dronecomponent
+      - collider
+      - motion-planner
+    related:
+      - cp2077.drones.control.dronecomponent-components
+  - id: cp2077.drones.control.dcr-spawner-and-follow
+    claim: "Drone Companions (Revamp) 0.5.0 spawns every companion as a gamedataSubCharacter_Record
+      filled with flats copied from a vanilla base (Character.Drone_Octant_Base, Drone_Wyvern_Base,
+      Drone_Griffin_Base, Drone_Bombus_Base; all three mechs from Character.Mech_NPC_Base; androids
+      from Character.wraiths_base_android with the mod's own .ent) through
+      Game.GetCompanionSystem():SpawnSubcharacterOnPosition. Following is the vanilla AI under an
+      AIFollowerRole whose followerRef is \"#player\" (GetAIControllerComponent():SetAIRole) plus
+      TweakDB edits to the vanilla follower records; script movement is AITeleportCommand with
+      doNavTest false (elevators, vehicles: drones go to a point 2 m up; fast travel) followed by a
+      ForceRagdollTask event. No altitude feature, no SetWorldTransform, no camera, no input
+      listeners, and the AI controller is never toggled."
+    status: community
+    source: "Nexus 23980 Drone Companions (Revamp) 0.5.0: bin/x64/plugins/cyber_engine_tweaks/mods/Drone
+      Companions (Revamp)/Modules/Base Drones.lua:40-58, :174, :189-203; Modules/Drone
+      Spawning.lua:203-212, :390-397; init.lua:25, :172-186; DroneLogic/Drone AI -
+      Combat.lua:137-145, :175; DroneLogic/Drone AI - Flying.lua:5-8; r6/scripts/DCO
+      Modules/DCO_Codeware.reds:24-31 (a DynamicEntitySystem path nothing raises)"
+    tags:
+      - drone
+      - community-mod
+      - companion
+      - spawner
+      - aifollowerrole
+      - teleport
+  - id: cp2077.drones.control.dc-spawner-and-follow
+    claim: "Drone Companion 5.7.0 (Nexus 32572) builds one gamedataSubCharacter_Record per chassis,
+      faction and instance from a vanilla faction base (Octant:
+      militech/arasaka/kangtao/trauma_team_base_drone_octant, prevention_unit_octant_drone,
+      max_border_drone_octant; Wyvern: eight *_base_drone_wyvern records; Griffin:
+      militech/kangtao/maelstrom_base_drone_griffin, q301_shuttle_fs_griffin,
+      sts_ep1_12_voodooboy_base_drone_griffin; Bombus: five *_base_drone_bombus plus
+      cvi_netwatch_drone_bombus_medium and sq025_delamain_drone_bombus; Minotaur:
+      militech/arasaka/ncpd/kurtz_base_minotaur) and spawns it with
+      CompanionSystem:SpawnSubcharacterOnPosition; Wyvern, Griffin and Android get the mod's own
+      .ent via entityTemplatePath. Following is an AIFollowerRole (AIHumanComponent.SetCurrentRole),
+      a once-a-second AITeleportCommand leash, AIFollowTargetCommand (desiredDistance 6, teleport
+      true) to resume, AIHoldPositionCommand (duration -1) to hold; ordered flyers are teleported to
+      the destination +2.5 m and held, never move-commanded. No altitude feature, no
+      SetWorldTransform, no AI toggle."
+    status: community
+    source: "Nexus 32572 Drone Companion 5.7.0:
+      bin/x64/plugins/cyber_engine_tweaks/mods/DroneCompanion/init.lua:16-122; records.lua:76-80,
+      :478-511, :677-682; companion.lua:456-466, :609-617, :910-920, :1585-1591, :1613-1617;
+      hacks.lua:287-290; orders.lua:157-159"
+    tags:
+      - drone
+      - community-mod
+      - companion
+      - spawner
+      - aifollowerrole
+      - teleport
+  - id: cp2077.drones.control.dc-drone-camera-is-a-free-camera
+    claim: "Drone Companion 5.7.0's \"drone camera\" is not bound to the drone: it spawns
+      base\\entities\\cameras\\simple_free_camera.ent with exEntitySpawner.Spawn, activates its
+      \"camera\" component (Activate(0.4, false)) and teleports the camera entity every frame with
+      TeleportationFacility:Teleport; V gets GameplayRestriction.NoMovement, NoCameraControl,
+      NoZooming, NoWeapons and NoDriving. For a flyer the camera is the pilot (12 m/s planar, 6 m/s
+      vertical from the inputs; a SyncRaycastByCollisionGroup \"Static\" ray refuses a blocked step)
+      and every 0.25 s the drone body is teleported by AITeleportCommand (doNavTest false) to a
+      chase offset behind and below the camera (Octant 2.2 back / 2.5 up, Wyvern 2.5 / 1.5, Griffin
+      3.0 / 2.0, Bombus 1.5 / 0.8) with the AI on; ground units are driven with AIMoveToCommand hops
+      of 8 m every 0.4 s. Exit deactivates the free camera, activates V's FPP camera component and
+      disposes the entity after 0.5 s. There is no HUD for the view."
+    status: community
+    source: "Nexus 32572 Drone Companion 5.7.0:
+      bin/x64/plugins/cyber_engine_tweaks/mods/DroneCompanion/dronecam.lua:5, :14-17, :27-33,
+      :44-52, :198-203, :240-247, :316, :337, :351, :364-402, :466-467, :500-508, :514, :527-539,
+      :547-549"
+    tags:
+      - drone
+      - community-mod
+      - camera
+      - free-camera
+      - teleport
+      - restriction
+    detail: "The fallback behind the head-slot patch: a view with no archive patch, at the cost of the
+      body chasing the camera."
+  - id: cp2077.drones.control.dc-vertical-actions-arrive-under-restrictions
+    claim: 'Drone Companion 5.7.0 reads its flight input from an Override of PlayerPuppet.OnAction while
+      V is under NoMovement and NoCameraControl: "Jump" is up; "ToggleCrouch", "Dodge" and "Crouch"
+      are down; "MoveX"/"MoveY" and "Forward"/"Back"/"Left"/"Right" the plane;
+      "CameraMouseX"/"CameraMouseY" (relative) and "CameraX"/"CameraY" (stick) the look. The mod
+      ships no inputs.xml and does not need Input Loader; its own hotkeys are Codeware Input/Key
+      callbacks (F-keys) and one CET registerHotkey.'
+    status: community
+    source: "Nexus 32572 Drone Companion 5.7.0:
+      bin/x64/plugins/cyber_engine_tweaks/mods/DroneCompanion/input.lua:125-131, :141-143;
+      dronecam.lua:404-428; r6/scripts/DroneCompanion/DroneSettings.reds:404-424; hijack.lua:257"
+    tags:
+      - input
+      - jump
+      - crouch
+      - dodge
+      - restriction
+      - listener
+      - community-mod
+    related:
+      - cp2077.drones.control.nojump-checked-in-psm
+    detail: Community evidence for the nojump-checked-in-psm inference; a quickhack mod's own listener
+      (registered differently) still has to be read with its own input-listener probe.
+  - id: cp2077.drones.control.ltbf-drone-mode-inputs
+    claim: "Let There Be Flight 0.3.18's \"Drone\" flight mode (FlightModeDrone; the readme's
+      Drone/Acrobat) reads six scalars — lift, surge, sway as force and pitch, roll, yaw as torque —
+      from input listeners Pitch, Sway, Roll, SurgePos, Lift, Yaw, SurgeNeg registered on the player
+      while flight is active. Its inputs.xml defaults: Flight_Lift = IK_Pad_LeftAxisY, IK_Space +1,
+      IK_LControl -1; Flight_Yaw = IK_Pad_LeftAxisX, IK_D +1, IK_A -1; Flight_Pitch =
+      IK_Pad_RightAxisY, IK_L +1, IK_Period -1; Flight_Roll = IK_Pad_RightAxisX, IK_Slash +1,
+      IK_Comma -1; Flight_Sway = the arrow keys only; surge = the vanilla Acceleration_Axis /
+      Deceleration_Axis plus HOTAS sliders. The actions live in a new context BaseVehicleFlight;
+      only the toggle and the paraglider are appended to vanilla contexts. Input Loader is a hard
+      dependency; the file is one <bindings> root holding <context> and <mapping>/<pairedAxes>
+      elements in the vanilla syntax, append=\"true\" extending a vanilla context."
+    status: community
+    source: "Nexus 5208 Let There Be Flight 0.3.18: red4ext/plugins/let_there_be_flight/inputs.xml:5-6,
+      :20-44, :174-175, :250-257, :262-288; packed.reds:3494-3500, :4284, :4385-4399;
+      readme.md:20-27"
+    tags:
+      - input
+      - input-loader
+      - inputs-xml
+      - flight
+      - community-mod
+      - keybinding
+  - id: cp2077.drones.control.ltbf-physics-and-camera
+    claim: "Let There Be Flight flies V's vehicle through a native RED4ext plugin: the script computes a
+      force and a torque per frame and accumulates them into native fields of a native
+      FlightComponent, which the DLL applies in the vehicle physics tick; no SetWorldTransform, no
+      teleport, no geometry-description query (collision is a reactive recovery timer after an
+      impact; the only spatial queries are four SyncRaycastByQueryFilter rays down from the tyres
+      for the hover modes). It has no code for NPC drones (the one ScriptedPuppet reference is
+      oxygen consumption). Its camera is the stock vehicle perspectives via
+      vehicleRequestCameraPerspectiveEvent, plus one custom view that moves V's own FPP camera
+      component to a CustomFlightCamera slot; it never spawns or binds a camera component."
+    status: community
+    source: "Nexus 5208 Let There Be Flight 0.3.18: red4ext/plugins/let_there_be_flight/packed.reds:620,
+      :1746-1760, :2429-2431, :2503-2510, :2774-2775, :2920-2924, :6072-6084, :6113-6125"
+    tags:
+      - flight
+      - physics
+      - red4ext
+      - camera
+      - community-mod
+  - id: cp2077.drones.control.movecomponent-reasserts-its-own-transform
+    claim: "A drone's moveComponent keeps a world transform of its own and puts the drone back to it
+      whenever script stops writing: with the AI off a single SetWorldTransform snaps back in the
+      same frame; with the component toggled off the write holds; toggled on again the drone snaps
+      back to the old spot. The drone motion planner plays no part. While a drone is flown by script
+      the component's transform stays put (13.8 m from the root in one in-game run)."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - drone
+      - mover
+      - movecomponent
+      - cache
+      - stop
+  - id: cp2077.drones.control.teleport-proxy-moves-the-cache-only-unfrozen
+    claim: "The action teleport proxy moves the moveComponent's own transform when the drone's AI is off
+      and the drone is not frozen: later writes snap back to the proxy's spot. In a script take that
+      freezes the drone (individual time dilation) the proxy reports STATUS_COMPLETE and moves
+      nothing. The slide proxy never answered."
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - drone
+      - proxy
+      - teleport
+      - frozen
+      - cache
+  - id: cp2077.drones.control.dithered-idle-holds-a-stop
+    claim: A script-flown drone's stop strobes when the idle stops writing (the moveComponent re-asserts
+      its transform) or writes the same transform each tick. Writing the last flown transform every
+      idle tick with the height alternately offset by +/-0.5 mm holds the drone still where it
+      stopped, on the Octant and the Wyvern; the idle animation's hover bob stays. The same writes
+      keep the hull's pitch, so no return to level is needed.
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - drone
+      - idle
+      - dither
+      - stop
+      - strobe
+    related:
+      - cp2077.drones.control.movecomponent-reasserts-its-own-transform
+  - id: cp2077.drones.control.chase-camera-shows-a-quarter-of-the-pitch
+    claim: In a quickhack mod's chase camera the active camera pitched -9 to -13 degrees while the flown
+      hull pitched -41.5, so screen centre is not where the drone points; a drone camera component's
+      local-to-world matrix did not carry the pitch either (a shot aimed along it levelled out).
+    status: verified
+    verified_on: "2.31"
+    source: ModWright field verification
+    tags:
+      - drone
+      - camera
+      - pitch
+      - aim