[Bug]: SpaceWarp does not extract the BepInEx/patchers directory
arthomnix opened this issue · 3 comments
Is there an existing issue for this?
- I have searched the existing issues
Operating System
Windows 11
CKAN Version
1.32.0
KSP Version
KSP2 0.1.1.0
Did you make manual changes?
Yes
Describe the bug
The metadata for SpaceWarp was designed for older versions of SpaceWarp, and does not extract the BepInEx/patchers directory. It also depends on BepInEx despite SpaceWarp now including BepInEx. This results in KSP2 not being able to start as it cannot find the SpaceWarp patcher.
see also: #15
Old:
New:
Steps to reproduce
- Install SpaceWarp via CKAN
- Launch KSP2
- Game cannot start correctly
Relevant log output
No response
Thanks for the report!
FYI, I have an unrelated fire to put out in some of the back-end Python code right now (mods submitted from SpaceDock with co-authors throw exceptions), but I'll come back to this after that is resolved.
(carrying on from #15) It doesn't really look like the BepInEx for KSP2 spacedock page is being maintained anymore (it still hasn't been updated to say it supports 0.1.1.0), and SpaceWarp packages BepInEx now, so could we just get rid of standalone BepInEx entirely (or set it as replaced-by SpaceWarp)?
A note on SpaceWarp's provision of BepInEx, SpaceWarp also provides a patched configuration for BepInEx that is necessary for KSP2 that was not provided in the old BepInEx pacakge