pmmp / bedrockdata Goto Github PK

We currently have no way of knowing exactly which items/blocks belong to a particular tag. This is a problem because tags are beginning to be used in crafting recipes on the wire.

Experimental gameplay is no longer enabled by a single flag in 1.16.100+.

• Required blockstates table for a given version (all are needed because the client cries if any are missing, very pointless system)
• Mapping of legacy block IDs <=> MCPE stringy IDs
• Mapping of legacy item IDs <=> MCPE stringy IDs

This garbage makes the data difficult for humans to understand. It's possible we could use a pseudo stringy ID system and then provide mappings from such system to the MCPE garbage.

Hello can I ask about a tutorial to use this?

This may use for UnlockedRecipesPacket in 1.20

item 166 not found

Hi!

I am curious about the content of required_item_list.json. What does the data inside them mean?

It would be great if we can have a short explanation of it in the README.md

I have tried looking for explanations in the commit history, any references in this repo or bds-mod-mapping but couldn't find any.

Thanks in advance!

recipes.json is mostly crafting-focused, but it has some other things mixed in, like furnace recipes, which it might be desirable to load separately. In addition, there are network potion recipes in 1.13 which probably don't belong in this file.

Some Items (Amethyst and The Chain Item (Not Block)) are missing from the resources. Those are the only ones I have found so far.

Chain Item = -503 [255 - 758] https://minecraft.fandom.com/wiki/Chain#ID
Amethyst = -327 [255 - 582] https://minecraft.fandom.com/wiki/Block_of_Amethyst#ID

Is there a reason some of these items are not added or is it because they were forgotten?

Since Mojang can never do anything consistently, it's necessary to account for various clusterfucks they've made over the years, such as using translation keys as IDs, mixed ID formats for entities, and more. The current 1:1 mapping tables are insufficient for loading data from disk.

• entity network identifiers
• biome definitions

These will be easier to generate in this fashion, as well as being more accessible.

r12 map does not implement the dead variants of coral (8-12).