Implement mod dependencies #13
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#13
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?
I should probably only attempt this after Nexus is integrated.
Right now, modders would have to manually type out the mod ID in their config file, but that's not really something they know about other mods. And comparing by name doesn't sound right.
Whereas with Nexus, they get a nice UI to select dependencies on the website, and I still get a unique identifier via the API.
It seems like Nexus does not expose dependency information.
It shows the "make sure to download these as well, dialog" on the page, but the API doesn't seem to offer that information.
Plus, relying on Nexus would leave out non-Nexus mods, and Nexus wouldn't have an "after"-style dependency either.
So it does have to go through
dtmt.cfg
only. I guess I can make things slightly more ergonomic by adding the ID to the mod details view.Proposed config section: