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

documentation: for addon install, no need to touch known_valid_known_packs.json #423

Merged
merged 1 commit into from
Jun 21, 2024

Conversation

breakersun
Copy link
Contributor

No description provided.

Copy link
Owner

@itzg itzg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That sounds great to have one last step. Since I have never been able to do the procedure myself, how certain are you the step isn't needed? Is there a reference you could link there?

@breakersun
Copy link
Contributor Author

I just tried it by myself but sorry I don't have a reference for this.

Also, we can do this to make packs bonded to just one world:

  • create resouce_packs & behavior_packs under worlds/Bedrock level,
  • Upload addons files to each directory
  • and then create world_resouce_packs.json & world_behavior_packs.json, put UUIDs/Version in each JSON file

@breakersun
Copy link
Contributor Author

I found known_valid_known_packs.json just gets updated by mcpe-server application itself every time it sees some new directory under resource_packs & behavior_packs.

@itzg
Copy link
Owner

itzg commented Jun 21, 2024

I just tried it by myself but sorry I don't have a reference for this.

Thanks, just thought I'd double check.

@itzg itzg merged commit f3734a0 into itzg:master Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants