Add BeatMods parsing and userdata restore
This commit is contained in:
+7
-1
@@ -15,7 +15,13 @@ The initial tool should stay conservative:
|
||||
- Mutating operations apply an explicit plan and record exact file hashes.
|
||||
- Nix packages `plugin-helper`, but does not directly manage the mutable Beat Saber tree.
|
||||
|
||||
This works well while Beat Saber is still launched from a Windows install or a mounted Windows filesystem.
|
||||
This works well while Beat Saber is launched from either the local Linux
|
||||
BSManager install or a mounted Windows BSManager filesystem.
|
||||
|
||||
For the near term, the Python state model should treat target roots as distinct
|
||||
installations even when they share an instance name. Lockfiles can stay keyed by
|
||||
Beat Saber version, but bootstrap state, generated plans, backups, and
|
||||
`installed.json` need to stay target-specific.
|
||||
|
||||
## Future: Nix-Orchestrated Plugin Sets
|
||||
|
||||
|
||||
Reference in New Issue
Block a user