Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapping pack resources to target version #39

Open
nahkd123 opened this issue Jan 25, 2023 · 0 comments
Open

Mapping pack resources to target version #39

nahkd123 opened this issue Jan 25, 2023 · 0 comments
Labels
engine Issues & PR related to Multipacks Engine enhancement New feature or request

Comments

@nahkd123
Copy link
Contributor

Pack indexes now have sourceGameVersion field, which you can define the version that the pack was originally made for. To use the pack on future versions, there are 2 ways:

  • Just build the pack with targetGameVersion == sourceGameVersion and load it to client. It should work, but future game versions may choose to remove "fixers" for old version, just like what they have done in 1.19.3.
  • Let Multipacks remap resources to new version. This can be defined in either multipacks.modifiers.json or Bundler (targetGameVersion argument).
    • User can choose to define in multipacks.modifiers.json if they are migrating from old game version to new game version. sourceGameVersion must be the same as what is defined in multipacks.modifiers.json.
@nahkd123 nahkd123 added enhancement New feature or request engine Issues & PR related to Multipacks Engine labels Jan 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine Issues & PR related to Multipacks Engine enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant