Hello guys this Json file I made is giving me crashes,

 

{
    "variants": {
        "variant=frozen_dirt_grassy": {
            "snowy=false": {
                "model": "mtaxspeo:block_frozen_dirt_grassy"
            },
            "snowy=true": {
                "model": "mtaxspeo:fixme_grass_snowed"
            }
        },

        "variant=dia_dim_dirt": {
            "model": "mtaxspeo:fixme_dirt"
        }
    }
}

Can't I have multiple variants with snowy condition? Or am I writing it wrong?

 

Thanks in Advance!

That is not the proper variant syntax.

http://mcforge.readthedocs.io/en/latest/blockstates/forgeBlockstates/

24 minutes ago, Draco18s said:

That is not the proper variant syntax.

http://mcforge.readthedocs.io/en/latest/blockstates/forgeBlockstates/

 

I didn't know Forge had a special Json syntax.

 

Anyway I didn't understand how am I supposed to write the json file for 2 blocks like I was trying to do. The examples you gave me are "single-block" examples. In my case i got the "frozen_dirt_grassy" block and the "dia_dim_dirt" block, the first has the snow condition and the second is a common dirt block.

 

I know that I could do something like this without the snow condition tho:

{
    "variants":
    {
        "variant=frozen_dirt_grassy": { "model": "mtaxspeo:block_frozen_dirt_grassy" },
        "variant=dia_dim_dirt": { "model": "mtaxspeo:fixme_dirt" }
    }
}

But I still didn't get it where should I add it.

Thanks

When it comes to block states, if one variant has an extra value all others do as well.

So you technically have a "variant=dia_dim_dirt,snowy=true" and "variant=dia_dim_dirt,snowy=false"

You just don't do anything with them.  But your JSON model still needs to specify them.

4 minutes ago, LexManos said:

When it comes to block states, if one variant has an extra value all others do as well.

So you technically have a "variant=dia_dim_dirt,snowy=true" and "variant=dia_dim_dirt,snowy=false"

You just don't do anything with them.  But your JSON model still needs to specify them.

{
    "variants": {
        "variant=frozen_dirt_grassy": {
            "snowy=false": {
                "model": "mtaxspeo:block_frozen_dirt_grassy"
            },
            "snowy=true": {
                "model": "mtaxspeo:fixme_grass_snowed"
            }
        },

        "variant=dia_dim_dirt": {
            "snowy=false": {
                "model": "mtaxspeo:fixme_dirt"
            },
            "snowy=true": {
                "model": "mtaxspeo:fixme_dirt"
            }
        }
    }
}

Thanks for your answer, shouldn't this work then? Sorry for the newbie questions and thanks

No you're hybridizing the Forge and Mojang JSON formats.

In the mojang version you have to specify all full variants. 

The point of Forge's json is to build the permutations for you.

So you can't nest them like that, you'd need:

{
    "variants": {
        "variant": {
            "frozen_dirt_grassy": {},
            "dia_dim_dirt": {}
        },
        "snowy": {
            "true": {},
            "false": {}
        }
    }
}

 

If you have a '=' ANYWHERE in your variant name it detects it as a normal Mojang variant and doesn't build the permutations for you.

So ya... read the docs, and either use the Forge version, or Mojang's version. Don't mix the two.

16 minutes ago, LexManos said:

No you're hybridizing the Forge and Mojang JSON formats.

In the mojang version you have to specify all full variants. 

The point of Forge's json is to build the permutations for you.

So you can't nest them like that, you'd need:

{
    "variants": {
        "variant": {
            "frozen_dirt_grassy": {},
            "dia_dim_dirt": {}
        },
        "snowy": {
            "true": {},
            "false": {}
        }
    }
}

 

If you have a '=' ANYWHERE in your variant name it detects it as a normal Mojang variant and doesn't build the permutations for you.

So ya... read the docs, and either use the Forge version, or Mojang's version. Don't mix the two.

Now I understand, Thank you for your help