Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New blocks data #83

Open
rom1504 opened this issue Nov 14, 2015 · 5 comments
Open

New blocks data #83

rom1504 opened this issue Nov 14, 2015 · 5 comments
Labels

Comments

@rom1504
Copy link
Member

rom1504 commented Nov 14, 2015

  • durability
  • transparency
  • blast resistance

see PrismarineJS/node-minecraft-data#3

Related to #52

@Gjum
Copy link
Member

Gjum commented Jan 29, 2016

What about a flag that indicates if a block has related Block Entity Data?

@phase
Copy link
Contributor

phase commented Feb 20, 2016

Whether or not a pickaxe can break a block would be nice data. Currently I have it stored in a big list and it's super ugly. Gamepedia has some data on it, though I think the hardness is already in minecraft_data. Really I'm just looking for a way to condense this:

    @Getter private static final List<String> level0Stones = Arrays
            .asList(new String[] { "stone", "cobblestone", "double_stone_slab", "stone_slab", "mossy_cobblestone",
                    "stone_stairs", "monster_egg", "cobblestone_wall", "sandstone", "stone_pressure_plate", "glowstone",
                    "stonebrick", "stone_brick_stairs", "sandstone_stairs", "cobblestone_wall", "redstone_block",
                    "quartz_block", "red_sandstone", "red_sandstone_stairs", "double_stone_slab2", "stone_slab2" });

    @Getter private static final List<String> level1Stones = Arrays
            .asList(new String[] { "iron_ore", "iron_block", "lapis_ore", "lapis_block" });

    @Getter private static final List<String> level2Stones = Arrays.asList(new String[] { "diamond_ore",
            "diamond_block", "gold_ore", "gold_block", "redstone_ore", "lit_redstone_ore" });

    @Getter private static final List<String> level3Stones = Arrays.asList(new String[] { "obsidian" });

    @Getter private static final List<String> level0Picks = Arrays.asList(
            new String[] { "wood_pickaxe", "gold_pickaxe", "stone_pickaxe", "iron_pickaxe", "diamond_pickaxe" });

    @Getter private static final List<String> level1Picks = Arrays
            .asList(new String[] { "stone_pickaxe", "iron_pickaxe", "diamond_pickaxe" });

    @Getter private static final List<String> level2Picks = Arrays
            .asList(new String[] { "iron_pickaxe", "diamond_pickaxe" });

    @Getter private static final List<String> level3Picks = Arrays.asList(new String[] { "diamond_pickaxe" });

This has each stone (or stonelike block) organized by "pick level". Each pick level contains what picks can break the blocks in that level. Putting this kind of data in minecraft_data would help everyone (or maybe just me) a lot.

@Gjum
Copy link
Member

Gjum commented Feb 20, 2016

@phase there is the harvestTools field, maybe that combined with the hardness is enough to determine the tool for you.

Example:

{
    "id": 1,
    "displayName": "Stone",
    "name": "stone",
    "hardness": 1.5,
    "harvestTools": {
      "257": true,
      "270": true,
      "274": true,
      "278": true,
      "285": true
    },
    "...": "..."
},

@sefirosweb
Copy link
Contributor

harvestTools no appears in dirt, is it a bug?
image

@nickelpro
Copy link
Member

No.

harvestTools is not a required field for blocks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants