[1.12 to 1.14.4] Separate logic for different block states

[Alex Sim]

Hello, I used to make mods for minecraft 1.7.10 and I'm getting back into it.

 

I haven't failed to notice the new XML JSON system (wannabe MVC compliant) sucks... a lot.

Haven't quite figured it out yet though, so my question is, can I separate what each blockstate for a single block does (ex: `facing` changes the rotation and `overworld` changes the base model) without having to write all combinations of states?

 

Example where i write all states combinations:

 

{
  "forge_marker": 1,
  "defaults" : {
    "model": "greenapple_glacia:block/glacial_berry"
  },
  "variants": {
    "facing=north,overworld=false" : {"y": 0},
    "facing=south,overworld=false": {"y": 180 },
    "facing=west,overworld=false":  {"y": 270 },
    "facing=east,overworld=false":  {"y": 90 },

    "facing=north,overworld=true" : {"model": "greenapple_glacia:block/glacial_berry_overworld", "y": 0},
    "facing=south,overworld=true": {"model": "greenapple_glacia:block/glacial_berry_overworld", "y": 180 },
    "facing=west,overworld=true":  {"model": "greenapple_glacia:block/glacial_berry_overworld", "y": 270 },
    "facing=east,overworld=true":  {"model": "greenapple_glacia:block/glacial_berry_overworld", "y": 90 }
  }
}

 

^ that is as much as i was able to trim it

I mean, if I used 4 states with 4 possible values each, I would have to write 4^4 = 256 stetes (?!)

Edited July 24, 2019 by Alex Sim

[Alex Sim]

16 minutes ago, diesieben07 said:

Wat?

 

Forge's blockstate format should help you here.

I'm dumb, I was trying to do something like this:

{
  "forge_marker": 1,
  "variants": {
    "facing" : {
      "north" : {"y": 0},
      "south" : {"y": 180},
      "west" : {"y": 270},
      "east" : {"y": 90}
    },
    "overworld" : {
      "true" : {"model": "greenapple_glacia:block/glacial_berry_overworld"},
      "false" : {"model": "greenapple_glacia:block/glacial_berry"}
    }
  }
}

 

But with normal syntax ("facing=north" : {...} ...)

This makes this XML JSON blockstates sytem not suck as much

 

Also thanks for answering again

Edited July 24, 2019 by Alex Sim

[Alex Sim]

3 minutes ago, diesieben07 said:

Nothing about this is XML.

ERR json ?, I need to sleep

Edited July 24, 2019 by Alex Sim

[Draco18s]

5 hours ago, Alex Sim said:

(wannabe MVC compliant)

Its not MVC (model-view-controller), its data-driven design.

[Alex Sim]

5 hours ago, diesieben07 said:

Wat?

 

Forge's blockstate format should help you here.

I've got another small issue, I don't know if that's just me messing it up again or an unimplemented/changed feature, but on 1.14.4 I'm not able to override textures inside a blockstate file, it just uses the model-associated texture (if present) or not-found texture otherwise

Here's an example of my blockstate

 

{
  "forge_marker": 1,
  "variants": {
    "examplestate": {
      "true": {
        "textures": {
          "side": "greenapple_glacia:blocks/test_bedrock",
          "end": "greenapple_glacia:blocks/test_bedrock"
        },
        "model": "greenapple_glacia:block/glacia_column_mono"
      },
      "false": {
        "textures": {
          "side": "greenapple_glacia:blocks/test_stone",
          "end": "greenapple_glacia:blocks/test_stone"
        },
        "model": "greenapple_glacia:block/glacia_column_top"
      }
    }
  }
}

 

But I have many tried different ways with the same result

Edited July 24, 2019 by Alex Sim

[Draco18s]

4 minutes ago, Alex Sim said:

1.14.4 I'm not able to override textures inside a blockstate file, it just uses the model-associated texture (if present) or not-found texture otherwise

https://github.com/MinecraftForge/MinecraftForge/issues/5615

[Alex Sim]

4 minutes ago, Draco18s said:

https://github.com/MinecraftForge/MinecraftForge/issues/5615

Oh well, atleast I did not mess this one up, thanks Draco