Mod bundles stay in the game directory after removing the mod #29
Labels
No labels
ci
crate/dtmm
crate/dtmt
crate/sdk
crate/serde_sjson
kind
bug
kind
documentation
kind
enhancement
kind
feature
kind
question
kind
upstream
part/bundle
part/filetype
stage
actionable
stage
design
stage
proposal
status/duplicate
status/good first issue
status/help wanted
status/invalid
status
need-replicate
status/wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: bitsquid_dt/dtmt#29
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For now, this is an intentional simplification of the process. It keeps the process of removing a mod separate from deploying mods.
Once the next deployment generates the package files, the extraneous mod bundle won't be in them, and therefore never cared for by the game. It still exists and wastes space, but very little of it.
But there is very little gain from implementing complex systems to track deployments currently, as the planned virtual file system will make it obsolete.
With the VFS now being less of a priority, it would make sense to implement this after all. And since #35 also needs some form of storing data about an active deployment, I might as well add the list of bundles.