skyrimvr-claude-toolkit: Skill for Claude Code

Port SSE Mod to VR

Systematically check the mod the user named ($ARGUMENTS in Claude Code) against every known VR incompatibility. Consult KNOWLEDGEBASE.md for full details on each item.

Step 1: SKSE Dependency Check

• Does the mod require SKSE64? → Needs SKSEVR equivalent
• Check for address library dependencies → VR address library is entirely different
• Look for DLL plugins in Data/SKSE/Plugins/ → must be compiled against SKSEVR
• Check if CommonLibSSE-NG versions exist (supports SE + AE + VR in one build)

Step 2: Papyrus Script Audit

Decompile all .pex files and check for:

• PlayIdle() on player → fails in VR (VRIK overrides skeleton IK). Replace with timed Papyrus scripts.
• DisablePlayerControls() alone → doesn't stop VR thumbstick movement. Add SetDontMove(true).
• SetVehicle() → causes HMD desync in VR. Must be removed entirely.
• ForceThirdPerson() / ForceFirstPerson() → can't control VR camera.
• Input.GetMappedKey() → returns -1 for VR controllers. Use VRIK API.
• Game.ShakeCamera() → mostly inert in VR, leave in but document.
• SetAngle() on player → doesn't control HMD orientation.

Step 3: Skeleton Compatibility

• Check for custom skeleton nodes → PreWEAPON and PreSHIELD nodes cause CTD in VR
• Verify XP32 compatibility → need "XP32 First Person Skeleton CTD Bugfix" for VR
• Any .hkx behavior files → Havok behaviors work but test with VRIK IK overlay

Step 4: Physics and Combat

• Havok physics tuned for 60Hz? → VR runs at 90Hz, needs fMaxTime INI adjustment
• Player collision assumptions → VR uses capsule vs ragdoll (not capsule vs capsule)
• Melee hit detection → in VR it is layered (HIGGS, optional collision mods, then vanilla). An SSE collision mod such as Precision lists SE/AE support on its Nexus page; check for a VR build before assuming it applies. Find out which layer the mod assumes and test against the user's actual stack.
• Weapon reach values → verify against the VR hit-detection stack, not SSE numbers