Custom block models [Easy to Implement]

[V2lsbGJsM3BpYw== 410]

So, in 1.8, they added 3D models in resource packs so that you can change the models of blocks. My idea is that when you open a resource pack, it will read the .json files of the models and use it. Luckily, the structure seems quite simple. Here is an example model (with comments):

{
    "__createdwith": "opl's Model Creator", //notneeded
    "ambientocclusion": false,              //ambient occlusion
    "textures": {                           //list of textures
        "tnt_side": "blocks/tnt_side",
        "tnt_top": "blocks/tnt_top",
        "tnt_bottom": "blocks/tnt_bottom",
        "particle": "blocks/tnt_side"
    },
    "elements": [                           //list of cubes
        {                                   //start of cube
            "from": [0,0,0],                //one corner
            "to": [16,16,16],               //opposite corner
            "faces": {                      //UV stuff
                "up": {
                    "uv": [0,0,16,16],
                    "texture": "#tnt_top"
                },
                "down": {
                    "texture": "#tnt_bottom"
                },
                "west": {
                    "texture": "#tnt_side"
                },
                "east": {
                    "texture": "#tnt_side"
                },
                "north": {
                    "texture": "#tnt_side"
                },
                "south": {
                    "texture": "#tnt_side"
                }
            }
        },
        {                                    //new cube
            "from": [-1,4,-1],               //one corner
            "to": [17,12,17],                //other corner
            "faces": {                       //UV stuff
                "up": {
                    "uv": [0,4,16,5],
                    "texture": "#tnt_side"
                },
                "down": {
                    "uv": [0,11,16,12],
                    "texture": "#tnt_side"
                },
                "west": {
                    "texture": "#tnt_side"
                },
                "east": {
                    "texture": "#tnt_side"
                },
                "north": {
                    "texture": "#tnt_side"
                },
                "south": {
                    "texture": "#tnt_side"
                }
            }
        }
    ]
}

 

The code is quite simple. It is some cubes with mapped textures. That is simply all it is. The 'from' and 'to' variables of each cube are the two opposite corners, and everything else is just saying what texture is mapped to which side.

 

 

HOW MINE-IMATOR WOULD DO IT:

 

CREATE FOLDER(BLOCK)

LOAD TEXTURES FROM FILE

CREATE CUBE("CUBE" + I)

I++

QUERY .JSON FILE FOR CORNERS

SCALE TO SIZE

MAP TEXTURE TO [CUBENAME]

PARENT TO [BLOCK]

 

In case you were interested, this code creates this block:

Edited June 12, 2015 by Willbl3pic

[Skjold 7.6k]

aka: a thing that will change rigs as we know it for all eternity..

[V2lsbGJsM3BpYw== 410]

aka: a thing that will change rigs as we know it for all eternity..

Didn't think of that

[Jmanbeatsminecraft 160]

that would make rigging WAY easier

[KicksBrickster 4.3k]

Now: imagine you take this, and make it possible to use these custom models on scenery. 3D grass, flowers, and blocks. MI goes from very decent to amazing.

[AbAppletic 446]

David will need to make a tutorial on how to do that. Not everyone knows what the heck that is

But I mean that code is very simple! I doubt anyone (except for a newbie) won't know how to do that.

Awesome suggestion!

[myluki2000 431]

David will need to make a tutorial on how to do that. Not everyone knows what the heck that is

But I mean that code is very simple! I doubt anyone (except for a newbie) won't know how to do that.

Awesome suggestion!

David doesn't need to make a tutorial, there are plenty already on the minecraftforums etc

[Charcoal Productions 176]

wtf is that pile of junk in that sppoiler

[V2lsbGJsM3BpYw== 410]

wtf is that pile of junk in that sppoiler

 

The code that makes the block at the end. It is explained, you know.

[flufffybuns 926]

wtf is that pile of junk in that sppoiler

You would understand if you knew code.

[V2lsbGJsM3BpYw== 410]

You would understand if you knew code.

You don't even need to 'understand code'. I explained everything.

[Kwazedilla 1.6k]

The only thing I understand would be the part where the textures are loaded and aligned against the block. But now I know how Hypixel - Warlords is done! But what language is that? This is an interesting concept. But I do believe that not a lot of people know how to implement 3d textures into Minecraft, let alone code to actually do this. Perhaps David can simplify this...

[V2lsbGJsM3BpYw== 410]

The only thing I understand would be the part where the textures are loaded and aligned against the block. But now I know how Hypixel - Warlords is done! But what language is that? This is an interesting concept. But I do believe that not a lot of people know how to implement 3d textures into Minecraft, let alone code to actually do this. Perhaps David can simplify this...

There are plenty of programs made to make that code. I used opl's model creator.

 

Here is an annotated version of the code:

 

 

{

"__createdwith": "opl's Model Creator",  Just saying what it was made with. Not necessary.

"ambientocclusion": false,                        I guess this bit toggles ambient occlusion on the block.

"textures": {                                               A list of textures and their paths in the resource pack.

"tnt_side": "blocks/tnt_side",

"tnt_top": "blocks/tnt_top",

"tnt_bottom": "blocks/tnt_bottom",

"particle": "blocks/tnt_side"

},

 

 

 

"elements": [       A list of cubes:

{

"from": [0,0,0],      One corner of the cube

"to": [16,16,16],    Second corner of the cube

"faces": {              List of faces and texture mappings. I'll skip this part as you said you know.

"up": {

"uv": [0,0,16,16],

"texture": "#tnt_top"

},

"down": {

"texture": "#tnt_bottom"

},

"west": {

"texture": "#tnt_side"

},

"east": {

"texture": "#tnt_side"

},

"north": {

"texture": "#tnt_side"

},

"south": {

"texture": "#tnt_side"

}

}

},

{                        Second cube

"from": [-1,4,-1],    One corner

"to": [17,12,17],     Other corner

"faces": {

"up": {

"uv": [0,4,16,5],

"texture": "#tnt_side"

},

"down": {

"uv": [0,11,16,12],

"texture": "#tnt_side"

},

"west": {

"texture": "#tnt_side"

},

"east": {

"texture": "#tnt_side"

},

"north": {

"texture": "#tnt_side"

},

"south": {

"texture": "#tnt_side"

}

}

}

]

}

[myluki2000 431]

The only thing I understand would be the part where the textures are loaded and aligned against the block. But now I know how Hypixel - Warlords is done! But what language is that? This is an interesting concept. But I do believe that not a lot of people know how to implement 3d textures into Minecraft, let alone code to actually do this. Perhaps David can simplify this...

 

It's called JSON - and it's not a programming language

Edited March 15, 2015 by myluki2000

[Kwazedilla 1.6k]

It's called JSON - and it's not a programming language

Then what is it?

[Aronanners 1.6k]

For clarification reasons: JSON (JavaScript Object Notation) is a lightweight data-interchange format.

[myluki2000 431]

Then what is it?

 

If you look at the JSON posted in the startpost:

{
    "__createdwith": "opl's Model Creator",
    "ambientocclusion": false,
    "textures": {
        "tnt_side": "blocks/tnt_side",
        "tnt_top": "blocks/tnt_top",
        "tnt_bottom": "blocks/tnt_bottom",
        "particle": "blocks/tnt_side"
    },
    "elements": [
        {
            "from": [0,0,0],
            "to": [16,16,16],
            "faces": {
                "up": {
                    "uv": [0,0,16,16],
                    "texture": "#tnt_top"
                },
                "down": {
                    "texture": "#tnt_bottom"
                },
                "west": {
                    "texture": "#tnt_side"
                },
                "east": {
                    "texture": "#tnt_side"
                },
                "north": {
                    "texture": "#tnt_side"
                },
                "south": {
                    "texture": "#tnt_side"
                }
            }
        },
        {
            "from": [-1,4,-1],
            "to": [17,12,17],
            "faces": {
                "up": {
                    "uv": [0,4,16,5],
                    "texture": "#tnt_side"
                },
                "down": {
                    "uv": [0,11,16,12],
                    "texture": "#tnt_side"
                },
                "west": {
                    "texture": "#tnt_side"
                },
                "east": {
                    "texture": "#tnt_side"
                },
                "north": {
                    "texture": "#tnt_side"
                },
                "south": {
                    "texture": "#tnt_side"
                }
            }
        }
    ]
}

you can see that you don't "tell" Minecraft what to do, for example this line:

"tnt_bottom": "blocks/tnt_bottom"

It tells Minecraft where the file for the bottom block texture is located, it's not code that makes Minecraft do something with the texture. It's not "executing" something, it just gives information to Minecraft so Minecraft can process it.

 

I hope you understand now, I suck at explaining and normally I would use a generic example for my explanations but I can't think of one right now

[Kwazedilla 1.6k]

If you look at the JSON posted in the startpost:

{
    "__createdwith": "opl's Model Creator",
    "ambientocclusion": false,
    "textures": {
        "tnt_side": "blocks/tnt_side",
        "tnt_top": "blocks/tnt_top",
        "tnt_bottom": "blocks/tnt_bottom",
        "particle": "blocks/tnt_side"
    },
    "elements": [
        {
            "from": [0,0,0],
            "to": [16,16,16],
            "faces": {
                "up": {
                    "uv": [0,0,16,16],
                    "texture": "#tnt_top"
                },
                "down": {
                    "texture": "#tnt_bottom"
                },
                "west": {
                    "texture": "#tnt_side"
                },
                "east": {
                    "texture": "#tnt_side"
                },
                "north": {
                    "texture": "#tnt_side"
                },
                "south": {
                    "texture": "#tnt_side"
                }
            }
        },
        {
            "from": [-1,4,-1],
            "to": [17,12,17],
            "faces": {
                "up": {
                    "uv": [0,4,16,5],
                    "texture": "#tnt_side"
                },
                "down": {
                    "uv": [0,11,16,12],
                    "texture": "#tnt_side"
                },
                "west": {
                    "texture": "#tnt_side"
                },
                "east": {
                    "texture": "#tnt_side"
                },
                "north": {
                    "texture": "#tnt_side"
                },
                "south": {
                    "texture": "#tnt_side"
                }
            }
        }
    ]
}

you can see that you don't "tell" Minecraft what to do, for example this line:

"tnt_bottom": "blocks/tnt_bottom"

It tells Minecraft where the file for the bottom block texture is located, it's not code that makes Minecraft do something with the texture. It's not "executing" something, it just gives information to Minecraft so Minecraft can process it.

 

I hope you understand now, I suck at explaining and normally I would use a generic example for my explanations but I can't think of one right now

I can say, that was very detailed. Thank you for your explanation.

[Joshdotmp4 2.8k]

It doesn't seem like it'd be too difficult to implement, but then again, I don't code :\

Anyways, I was just about to suggest this myself. Ever since 1.8, I've been infatuated with 3D models, and have made some of my own. Being able to import that work into MI would be totally DANK

[V2lsbGJsM3BpYw== 410]

It doesn't seem like it'd be too difficult to implement, but then again, I don't code :\

Anyways, I was just about to suggest this myself. Ever since 1.8, I've been infatuated with 3D models, and have made some of my own. Being able to import that work into MI would be totally DANK

lol i love 3d models too

[V2lsbGJsM3BpYw== 410]

Bumped due to new info in OP.

[MineRocker Animations 1.4k]

That would be so amazing to have in MI.

Minecraft can already do it so we could create resourcepacks with this and use those as rigs.

That would awesome.

I hope David sees this.

Edited July 8, 2015 by MineRocker Animations

[Littleman9Mew2 206]

This could also add the "Entity Models" that 1.9+ would implement as well, this could create custom mobs with the aid of RP's

[LightStrikeBoom 5]

Just saying in the devlog(for 1.0.0 or 1.0.0 demo 6) you can import models from blender which works better