Investigate non-bundled mod assets #113
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#113
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?
Since
dtmt.sjson
includes values that are relevant to both kinds of mods, the config file needs some kind ofloose = true
setting.Will have to find an elegant way to make the bundle-related settings optional (erroneous even, ideally) in that instance.
To keep complexity from exploding, it should still be an either/or decision. I.e. not mixing bundles for textures with loose Lua files.
Both DML and DMF need to know if a mod is bundled.
DML can probably get away with simply knowing how many packages it needs to load for the mod to be ready to run it's
run
callback, with 0 being a valid number for non-bundled mods.DMF needs to know it to be able to switch between
require
andio
loading for the files passed tonew_mod
.