Hi, is there a way to specify wich textures to use without the use of json files ?

personally writing tons of json files just don't makes any sense to me, if you could also put in in the [CustomBlock] method.

 

I was more thinking in the form of:

if( condition ){
	/* use [this] texture on [this face]*/
}

 

thanks in advance

Edited November 9, 20186 yr by goingcrowd9

47 minutes ago, goingcrowd9 said:

Hi, is there a way to specify wich textures to use without the use of json files ?

Nope.

14 hours ago, goingcrowd9 said:

personally writing tons of json files just don't makes any sense to me

Auto generate them?

do I also have to specify wich models to use in the blockstate json file or is it also possible to drirectly refer to the textures themselves in the file ?

like:

 

{
    "multipart": [
    
        {   "apply": {

                   "north": { "bm:normal_glass_middle" },
            }

        }
        
        {   
            "when": { "condition": "true" },
            { "apply": {

                    "north": { "texture": "modid:awsome_texture" },

                    "south": {  "texture": "modid:another_awsome_texture"
                }

            }

        }
         
    ]
}

Edited November 10, 20186 yr by goingcrowd9
tab == post ??

You will still need models. You may be able to define those models in the blockstate file though (I have no proof of this, and I think it’s unlikely, but MAY be possible).

You should take a look at Forge’s blockstate format. Personally I prefer vanilla because of its simplicity but Forge definitely has more features & potential.

https://mcforge.readthedocs.io/en/latest/models/blockstates/forgeBlockstates/

On 11/10/2018 at 10:44 AM, Cadiboo said:

Personally I prefer vanilla because of its simplicity but Forge definitely has more features & potential.

Forge states are good for things like Fences, which have 4 different on-off properties. Vanilla format has to list out each one (so, 16 entries) whereas with Forge you can list out 4 and Forge will do the heavy lifting.

 

For example, this block I have:

https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/resources/assets/expindustry/blockstates/machine_foundry.json#L18-L33

 

With a vanilla state file I'd have to list out all 8 combinations manually:

north {rotation}, lit {submodel}
north {rotation}, unlit
east {rotation}, lit {submodel}
east {rotation}, unlit
west {rotation}, lit {submodel}
west {rotation}, unlit
south {rotation}, lit {submodel}
south {rotation}, unlit

Look at how many times the {submodel} had to be retyped! And each rotation had to be specified twice as well.

On 11/12/2018 at 5:52 AM, Draco18s said:

Forge states are good for things like Fences, which have 4 different on-off properties. Vanilla format has to list out each one (so, 16 entries) whereas with Forge you can list out 4 and Forge will do the heavy lifting.

You could do it that way, but Vanilla provides "multipart", "when", "OR" & "AND" which you can use to achieve the same functionality

On 11/10/2018 at 4:11 AM, goingcrowd9 said:

do I also have to specify wich models to use in the blockstate json file or is it also possible to drirectly refer to the textures themselves in the file ?

like:

To answer this question you do and always have to specify a model, however you do not need to specify the textures within the model, that can be done in the blockstate file with the forge blockstate system. This allows for easy creation of basic blocks IE fully square ones. You only have to refer to the vanilla models and specify what texture(s) to use in the blockstate, allowing for simple blocks only needing one Json file. including the ItemBlock with the inventory variant.

12 hours ago, Cadiboo said:

You could do it that way, but Vanilla provides "multipart", "when", "OR" & "AND" which you can use to achieve the same functionality

That was the point of my post.