Change id of core content pack from 'dda' to 'bn' #2115
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
SUMMARY: Infrastructure "Changed id of core content pack from 'dda' to 'bn'"
Purpose of change
At the moment, DDA and BN share the same core content pack id -
dda
. Because of that, any external DDA-compatible mod installed on BN will show up as compatible with BN in UI, but will throw arcane errors when attempting to load the world.Describe the solution
Migrate to new content pack id:
dda
mod, but with idbn
dda
into an empty obsolete mod that depends onbn
bn
This way:
Bright Nights
Bright Nights (wrapper)
, but will keep functioningbn
mod automagically loaded becausedda
now depends on itbn
, we can removedda
mod which will make all mods that depend ondda
(DDA mods) incompatible with BN.Describe alternatives you've considered
Hack it by adding
"is_compatible_with_bn": true
toMODINFO
object.Testing
Bright Nights (wrapper)
gets automatically added to mod listdda
in its mod list,Bright Nights
gets automatically loaded beforeBright Nights (wrapper)
, but save's mod list stays unchanged (expected behavior)dda
mod, addeddda
->bn
migration todata/mods/replacements.json
and tried to create new (or load existing) world. Result: mods that depend onbn
work as expected, mods that depend ondda
show missing dependency, saves that usedda
have their mod list updated to usebn