For bedrock edition see bedrock.md
file name | auto? | how to get it | notes |
---|---|---|---|
protocol.json | No | Follow Pre-release Protocol | Always double check by looking at the Minecraft source files. |
blocks.json | Yes | Use minecraft-data-generator-server | |
items.json | Yes | Use minecraft-data-generator-server | |
entities.json | Yes | Use minecraft-data-generator-server and run extractPcEntityMetadata.js script in tools/js to generate entity metadata in entities.json and protocol.json |
|
recipes.json | Yes | Use Burger, then use burger-extractor | should eventually be changed to native data generators |
blockCollisionShapes.json | Yes | Use minecraft-data-generator-server | |
commands.json | No? | Use mc-data-command-generator | Link to jar files have to be manually added |
biomes.json | Yes | Use minecraft-data-generator-server | |
instruments | Yes | Use minecraft-data-generator-server | |
materials.json | Yes | Use minecraft-data-generator-server | |
windows.json | No | Look at wiki.vg inventories | |
version.json | No | Look at Protocol Versions | wiki.vg protocol numbers |
effects.json | Yes | Use minecraft-data-generator-server | |
enchantments.json | Yes | Use minecraft-data-generator-server | |
language.json | Yes | Use minecraft-data-generator-server | |
particles.json | Yes | Use minecraft-data-generator-server | |
blockLoot.json | No | Use minecraft-jar-extractor | Extractor can be very be tempermental at times |
entityLoot.json | No | Use minecraft-jar-extractor | Extractor can be very be tempermental at times |
mapIcons.json | No | Icons data can be found in the Minecraft source directly. Alternatively you might be able to look up the icons from the following page on the Minecraft wiki or from wiki.vg. | minecraft-data pr mapIcons |
loginPacket.json | Yes | Running tests on node-minecraft-protocol | |
sounds.json | Yes | Use minecraft-data-generator-server | Make sure to check the packets that use this and the friendlybytebuffer functions to check if an offset is needed in the generator code. |
foods.json | Yes | Use minecraft-data-generator-server | move file obtained with minecraft-data-generator-server to the correct location and run extractPcFoods.js script located in tools/js |
- All files that say Yes for auto can be gotten from minecraft-data-auto-updater (that uses minecraft-data-generator-server). This is the preferred way to extract the data.
- Note, there is a script inside the
tools/js
folder that can be run withnpm run version
with usage ofnpm run version <bedrock|pc> {version} {protocol_version}
to automatically copy over old data including the protocol in support for a new version and update entries in the dataPaths.json.
After generating and creating the new files for the version in its own directory, the version must be added to dataPaths.json in the data folder. Additionally in data/pc/common the versions.json file needs to be updated with the new version.
- See [protocol.md] for information on the protocol and how to update the data