Improving entities data

[rom1504]

See http://minecraft.gamepedia.com/Alpha_Level_Format/Chunk_File_Format#ArmorStand
and http://wiki.vg/Entities#ArmorStand and #6 (comment)

[rom1504]

apparently wiki.vg is correct, non-unique ids

[Gjum]

also related to #11

[rom1504]

I finally checked with flying-squid : 61 is both blaze and snowball. mcwiki non-mobs ids are wrong (see http://minecraft.gamepedia.com/Talk:Data_values/Entity_IDs)
Concerning mcdata, I'm going to make an extractor taking its data from wiki.vg.

The type should be the same as the one in the mc protocol as this is what's useful (these ones https://github.com/PrismarineJS/prismarine-entity#entitytype) and I think it's okay to have non unique ids, we will just have to take that into account when building the indexer.

[Gjum]

What is the current state here? Are there plans on the JSON format/schema yet, especially entity metadata representation? Is the data on wiki.vg still completely valid?

[rom1504]

Still plan on extracting both from the mcwiki and wiki.vg to have both set of ids, but I haven gotten to do it yet. I guess I might do it soon.

[rom1504]

about entity metadata :
see http://wiki.vg/Pre-release_protocol#Entity_Metadata and http://wiki.vg/Entities#Entity_Metadata

I think the idea is something like

[
 { 
   "index":17,
   "type":"int",
   "meaning":"Shaking Power"
  }
]

For things with a bitmask, possible values could be there too.

What I'm really unsure about is the classes thing. Do we want to store the extend relationship in the .json file, should it be all in the same .json file or an other one ?

[Gjum]

Each entity metadata class can only extend one other class, so an optional extends field is fine. One other way would be to preprocess the extending, ie. each entry stores both the listed, "additional" items, and the inherited items, all in one json list.

Example: Ender Crystal extends Entity by adding index 8 to Entity's 0, 1, 4.
So Ender Crystal could be:

• using extension: "extends": "Entity", "metadata": [{"index": 8, ...}]
• preprocessed: "metadata": [{"index": 0, ...}, {"index": 1, ...}, {"index": 4, ...}, {"index": 8, ...}]

[rom1504]

so entities.json is done.

Remaining : entity metadata. Which will go in its own file, probably entities_metadata.json

[rom1504]

@Gjum I think the first format is probably the best.

And then X-minecraft-data or users (would it belong in X-minecraft-data ?) could have go through the extends to generate the whole available fields.

[Moondarker]

Seems like there are no reliable sources for entity metadata online (for versions 1.8 - 1.16 at least), and extracting this from game files will be a major pain - the way metadata handling is coded differs from entity to entity
However this will be needed very soon, for webclient and viewer
UPD: I will try to update burger-extractor to handle that