Add block drops about minecraft-data HOT 12 CLOSED

I'm okay with that (it's even automatically extractable from the wiki : see drops in the infobox in http://minecraft.gamepedia.com/Stone).
The tool you need to use is an other field (harvestTools : https://github.com/PrismarineJS/minecraft-data/blob/master/enums/blocks.json#L20 : should probably be an array instead of a "id":true object).

Why minAmount and maxAmount though ? Isn't amount enough ?

from minecraft-data.

Glowstone, lapis, etc... both have random amount of drops.

from minecraft-data.

This could also be done for entities.

from minecraft-data.

Oh right, yeah.

from minecraft-data.

Tools drop all drop the same thing (or nothing) for one given block, except for tools with enchantments :

• silk : maybe store what you can harvest with silk in a silk.json
• fortune

Enchantments (http://minecraft.gamepedia.com/Enchant#Enchantments) should probably be handled separately.

from minecraft-data.

There is a lot of minCount: 1, maxCount: 1 - should we allow a simple count: 1 if min == max?

from minecraft-data.

Yeah I guess.
Oh and I took the "chance" from the wiki when it was available, so minCount can be a number from 0 to 1 (for exemple 0.3333 for 33.33%), I don't know if it that's a good idea.

from minecraft-data.

chance might be useful for servers to implement the dropping behavior ;)

from minecraft-data.

So : there are a lot of minCount: x, maxCount: y with x==y, we can add a count: field. Because often x==y==1, it might also be possible to not put a count at all for these ? (default : count = 1)

from minecraft-data.

Wouldn't it be better to keep data difference to a minimum ? I feel having either min/max OR count would make it harder to use the minecraft-data without really adding value.

from minecraft-data.

Yeah I agree.
What about having the default value for both these fields to 1 so in most cases they just wouln't be there ?

from minecraft-data.

Yeah, default values are perfectly fine.

from minecraft-data.