Item Appearance

How to customize your item appearance?

The pack folder

This folder contains all your ResourcePack content. It's structure is the same as any normal resourcepack, but with a few tweaks. Textures and models can simply be dragged into pack/assets/minecraft/(models/textures) respectively, if you have individual files. If you have a full resourcepack, you can add it to pack/external_packs

Create a basic 2d item

Put the textures that you need in the textures directory of the pack folder. You can then reference the textures in your item & make Nexo generate the necessary model-file:

my_item:  
  Pack:
    generate_model: true
    parent_model: "item/handheld"
    textures:
      - example_image1.png #png extension is not needed
      - example_image2.png

The parent_model field is required by minecraft. It is mainly used to inherit certain rendering properties of models. Most items will use item/generated, but item/handheld is often used by tools and weapons.

You can also use an alternative way of declaring textures, especially nice when using block parent-models. This lets you specify the texture-ids to use specifically.

Pack:
  generate_model: true
  parent_model: "block/cube"
  textures:
    top: example_image.png
    side: example_image2.png

Use your own JSON Model

ALWAYS USE LOWER CASE FOR MODEL AND TEXTURE NAMES. Upper case is n longer supported by minecraft vanilla since 1.11 (even though it still works for users using optifine).

  Pack:
    generate_model: false
    model: example_model.json #json extension is not mandatory

⚠️ Pro tips when you use a json model!

Usually the templates you get place the textures in a folder, to make sure, open the json file and look at the first few lines, you should find something similar:

{
  "textures": {
    "particle": "custom/my_item",
    "texture": "custom/my_item",
    "bonesword_palette": "custom/my_item"
  }
}

As above shows the model is set to look for textures in custom/my_item The file should then be put inside Nexo/pack/assets/minecraft/textures/custom/my_item The normal structure for model & texture-paths are namespace:some/path, which is the same as pack/assets/namespace/(models/textures)/some/path(.png/.json)`

Use a blocking json model (for shield)

  Pack:
    generate_model: false
    model: example_shield.json #json extension is not mandatory
    blocking_model: example_shield_blocking.json #json extension is not mandatory

Use a pulling json model (for bows)

  Pack:
    generate_model: false
    model: default/combat_bow
    pulling_models:
      - default/combat_bow_pulling_0
      - default/combat_bow_pulling_1
      - default/combat_bow_pulling_2

This also works with pulling_textures if you only have texture files

Use charged_model json model (for Crossbows)

  Pack:
    generate_model: false
    model: default/custom_bow
    pulling_models:
      - default/custom_bow_pulling_0
      - default/custom_bow_pulling_1
      - default/custom_bow_pulling_2
    charged_model: default/custom_bow_pulling_2
    firework_model: default/custom_bow_charged #Optional

This also works with charged_texture & firework_texture if you only have texture files

Use cast_model json model (for fishing rods)

  Pack:
    generate_model: false
    model: default/fishing_rod
    cast_model: default/fishing_rod_cast

This also works with cast_texture if you only have texture files

Use damaged_model json model (for different durability levels)

Pack:
  generate_model: false
  model: default/diamond_sword
  damaged_models:
    - default/diamond_sword_damaged1
    - default/diamond_sword_damaged2
    - default/diamond_sword_damaged3

This also works with damaged_textures if you only have texture files