Open malicean opened 3 years ago
Additionally, there should be separate categories of mutable mod data. One should be data that can be safely deleted, such as autogenerated or frequently changing information, and the other should be data that cannot be safely deleted, such as progression or key information. This should be done so users can transfer and backup all mod data without any unnecessary garbage. Possible names could be cache
and data
, but data
is a little generic.
Mods should have some form of IO that supports CRUD operations (i.e. mutable) to save player progression or customization that could not be done via a config.
This should most certainly not mutate the existing mod, but instead operate on a different path that the mod owns. Ideally, this would implement the immutable IO (the current IO) code, so all IO is simplified into one system with just permission changes.
This should wait on #15, as it would provide a good starting point to make a traversable file system.