minecraft-data
minecraft-data copied to clipboard
Language independent module providing minecraft data for minecraft clients, servers and libraries.
There are several universal constant values that are just key-value mappings and have in common that they do not fit into any of the present formats. - [ ] QUICK_BAR_COUNT...
In particular it would explain that minecraft-data prefer array vs indexed data (to let the wrapper index how they want). Useful for new people adding data to mcdata.
There's some more data that I think can go from mineflayer to minecraft-data : - [ ] animationEvents / entityStatusEvents / spawnedObjectTypes / mobTypes https://github.com/andrewrk/mineflayer/blob/master/lib/plugins/entities.js#L10 https://github.com/andrewrk/mineflayer/issues/207 https://github.com/PrismarineJS/minecraft-data/issues/11 - [ ]...
Not having an index in json files makes it easier for users to index by what they need. That means the data doesn't have to change if one index or...
https://github.com/PrismarineJS/minecraft-data/blob/master/data/1.8/blocks.json#L1363 Since the wiki page indicates it's full, it might be simpler to just have a manual check in the extraction script or something like that ( http://minecraft.gamepedia.com/Redstone )
1 placed item can become multiple placed blocks. see http://minecraft.gamepedia.com/Door#ID That data is needed to implement placing blocks in a server. It would probably look like the recipes file (in...
Consider separating the drops in a new file. An other possibility would be putting the drops attribute in each variation, but it seems messy.
blocks.json and items.json already contain "simple variations" : only the metadata and the displayName changes (for example [stones](https://github.com/PrismarineJS/minecraft-data/blob/master/enums/blocks.json#L28)). But there is an other kind of variation : functional variations, examples...
something like http://wiki.vg/Protocol Or should it be like the table of packets at http://wiki.vg/Pre-release_protocol ?