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

Add new legacy bedrock mappings #303

Merged

Conversation

Flonja
Copy link
Contributor

@Flonja Flonja commented Aug 18, 2023

I don't know if the submodule automatically gets updated or not...

@Flonja
Copy link
Contributor Author

Flonja commented Aug 18, 2023

Thanks

@@ -651,6 +651,16 @@ Example:
console.log(mcData.legacy.pc.blocks['171:15']) // Returns: 'minecraft:black_carpet'
```

### minecraftData.legacy.bedrock.blocks

Mapping from 1.2 block:metadata to 1.18.10 block names
Copy link
Member

Choose a reason for hiding this comment

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

This should explicitly mention 1.18.10 as 1.18 is ambiguous, given some blocks were changed in 1.18.* versions. I think it'd be better to map to the version immediately after flattening, but it's not a big deal right now. Other mapping data would need to be added also for other block renames/changes, but this can be done later to keep things simple for now.

@extremeheat extremeheat merged commit 15b9361 into PrismarineJS:master Aug 19, 2023
2 checks passed
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