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

Request for Upgrade Guides for common issues #779

Open
Jbenisek opened this issue Dec 29, 2023 · 3 comments
Open

Request for Upgrade Guides for common issues #779

Jbenisek opened this issue Dec 29, 2023 · 3 comments
Assignees
Labels
CONTENT For wiki content itself, not the site. suggestion General suggestion, content or website.

Comments

@Jbenisek
Copy link

With so many name changes and component changes between exp and vanilla it would be helpful to have some guides covering those basic issues. Since so many are having them and will be over the next years as they upgrade from 1.16.100 and 1.19.0 to current.

thank you.

Main issues I've seen are item and world gen

@Jbenisek Jbenisek added the suggestion General suggestion, content or website. label Dec 29, 2023
@Jbenisek
Copy link
Author

image

Example

@SmokeyStack SmokeyStack added the CONTENT For wiki content itself, not the site. label Dec 29, 2023
@SmokeyStack SmokeyStack self-assigned this Dec 29, 2023
@QuazChick
Copy link
Collaborator

Hopefully #857 and #858 help with moving away from the deprecated JSON block/item events.

@QuazChick
Copy link
Collaborator

We now have a block format history page published at https://wiki.bedrock.dev/blocks/block-format-history. It should be useable as an upgrade guide if followed in reverse from the format version you're currently using. A similar page is planned for items.

@QuazChick QuazChick self-assigned this Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CONTENT For wiki content itself, not the site. suggestion General suggestion, content or website.
Projects
None yet
Development

No branches or pull requests

3 participants