Search the Forums BEFORE making a new post.

MC 1.10+ Custom wall JSON issue

Posted October 23, 20168 yr

I have created my own wall class and everything is working fine.

But there is something not right with the json file i think.

While my walls behave like it should be and they are rendered correctly in the world and in my inventory, there is something weird when i break them.

If you break a block, you see "breaking" particles wich is normal.

If i break my wall i see those particles without the right texture.

I see those particles in black/pink

Here is the json:

{
    "forge_marker": 1,
    "defaults": {
        "model": "builtin/generated"
        },
    "variants": {
        "up": {
            "true": {
                "submodel": {"wall_up": {"model": "wall_post"}}
            },
            "false": {}
        },
        "north": {
            "true": {
                "submodel": {"wall_north": {"model": "wall_side","uvlock": true}}
            },
            "false": {}
        },
        "east": {
            "true": {
                "submodel": {"wall_east": {"model": "wall_side","y": 90,"uvlock": true}}
            },
            "false": {}
        },
        "south": {
            "true": {
                "submodel": {"wall_south": {"model": "wall_side","y": 180,"uvlock": true}}
            },
            "false": {}
        },
        "west": {
            "true": {
                "submodel": {"wall_west": {"model": "wall_side","y": 270,"uvlock": true}}
            },
            "false": {}
        },
        
        "type": {
            "raw": {
                "textures": {
                    "wall": "tem:blocks/chalkstone"
                }
            },
            "smooth": {
                "textures": {
                    "wall": "tem:blocks/smooth_chalkstone"
                }
            },
            "bricked": {
                "textures": {
                    "wall": "tem:blocks/bricked_chalkstone"
                }
            }
        },
        "type=raw": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/chalkstone"
            }
        },
        "type=smooth": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/smooth_chalkstone"
            }
        
        },
        "type=bricked": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/bricked_chalkstone"
            }
        }
    }
}

I figured out that removing this from the json:

 "defaults": {
        "model": "builtin/generated"
        },

fixes it more or less but then i see this in the console:

[23:56:47] [Client thread/ERROR] [FML]: MultiModel minecraft:builtin/missing is empty (no base model or parts were provided/resolved)

[23:56:48] [Client thread/ERROR] [FML]: MultiModel minecraft:builtin/missing is empty (no base model or parts were provided/resolved)

The particles are mostly normal then, except for 1.

So i still see the black/pink particles but it's like just 1 out of 10.

How can i fix this?

Everything is working good, just this particle thing is really ennoying!

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

October 23, 20168 yr

It's an amazing coincidence that I am also running into a json issue with custom walls today. Maybe we can converge on a solution that works for both of our mods.

I took a different approach to the blockstates file, attempting to separate the texture from the other properties in an advanced Forge blockstate file and then copy the multipart json from vanilla. Unfortunately, I get a slew of MissingVariantException, so either I wrote it wrong, or it's not possible to do what I have attempted.

What do you think of this blockstates file (is it salvageable?):

{
  "forge_marker": 1,
  "variants": {
    "multipart": [
        {   "when": { "up": "true" },
            "apply": { "model": "wall_post" }
        },
        {   "when": { "north": "true" },
            "apply": { "model": "wall_side", "uvlock": true }
        },
        {   "when": { "east": "true" },
            "apply": { "model": "wall_side", "y": 90, "uvlock": true }
        },
        {   "when": { "south": "true" },
            "apply": { "model": "wall_side", "y": 180, "uvlock": true }
        },
        {   "when": { "west": "true" },
            "apply": { "model": "wall_side", "y": 270, "uvlock": true }
        }
    ],
    "skin": {
        "0":  { "textures": { "wall": "minecraft:blocks/cobblestone" }},
        "1":  { "textures": { "wall": "minecraft:blocks/cobblestone_mossy" }},
        "2":  { "textures": { "wall": "minecraft:blocks/hay_block_side" }},
        "3":  { "textures": { "wall": "minecraft:blocks/prismarine_dark" }},
        "4":  { "textures": { "wall": "minecraft:blocks/prismarine_bricks" }},
        "5":  { "textures": { "wall": "minecraft:blocks/lapis_block" }},
        "6":  { "textures": { "wall": "minecraft:blocks/quartz_ore" }},
        "7":  { "textures": { "wall": "minecraft:blocks/quartz_block_lines" }},
        "8":  { "textures": { "wall": "minecraft:blocks/iron_block" }},
        "9":  { "textures": { "wall": "minecraft:blocks/red_sandstone_normal" }},
        "10": { "textures": { "wall": "minecraft:blocks/red_sandstone_carved" }},
        "11": { "textures": { "wall": "minecraft:blocks/glass" }},
        "12": { "textures": { "wall": "minecraft:blocks/glowstone" }},
        "13": { "textures": { "wall": "minecraft:blocks/sea_lantern" }},
        "14": { "textures": { "wall": "minecraft:blocks/diamond_block" }},
        "15": { "textures": { "wall": "minecraft:blocks/emerald_block" }}
    }
  }
}

Maybe I need to continue the multipart to "apply" each of the skins? would such a solution work for your custom walls also?

The debugger is a powerful and necessary tool in any IDE, so learn how to use it. You'll be able to tell us more and get better help here if you investigate your runtime problems in the debugger before posting.

Quote

October 24, 20168 yr

I tried continuing the multipart:

{
  "variants": {
    "multipart": [
        {   "when": { "up": "true" },
            "apply": { "model": "wall_post" }
        },
        {   "when": { "north": "true" },
            "apply": { "model": "wall_side", "uvlock": true }
        },
        {   "when": { "east": "true" },
            "apply": { "model": "wall_side", "y": 90, "uvlock": true }
        },
        {   "when": { "south": "true" },
            "apply": { "model": "wall_side", "y": 180, "uvlock": true }
        },
        {   "when": { "west": "true" },
            "apply": { "model": "wall_side", "y": 270, "uvlock": true }
        },

        {   "when": { "skin": "0" },
            "apply": { "textures": {"wall": "minecraft:blocks/cobblestone"} }
        },
        {   "when": { "skin": "1" },
            "apply": { "textures": {"wall": "minecraft:blocks/cobblestone_mossy"} }
        },
        {   "when": { "skin": "2" },
            "apply": { "textures": {"wall": "minecraft:blocks/hay_block_side"} }
        },
        {   "when": { "skin": "3" },
            "apply": { "textures": {"wall": "minecraft:blocks/prismarine_dark"} }
        },
        {   "when": { "skin": "4" },
            "apply": { "textures": {"wall": "minecraft:blocks/prismarine_bricks"} }
        },
        {   "when": { "skin": "5" },
            "apply": { "textures": {"wall": "minecraft:blocks/lapis_block"} }
        },
        {   "when": { "skin": "6" },
            "apply": { "textures": {"wall": "minecraft:blocks/quartz_ore"} }
        },
        {   "when": { "skin": "7" },
            "apply": { "textures": {"wall": "minecraft:blocks/quartz_block_lines"} }
        },
        {   "when": { "skin": "8" },
            "apply": { "textures": {"wall": "minecraft:blocks/iron_block"} }
        },
        {   "when": { "skin": "9" },
            "apply": { "textures": {"wall": "minecraft:blocks/red_sandstone_normal"} }
        },
        {   "when": { "skin": "10" },
            "apply": { "textures": {"wall": "minecraft:blocks/red_sandstone_carved"} }
        },
        {   "when": { "skin": "11" },
            "apply": { "textures": {"wall": "minecraft:blocks/glass"} }
        },
        {   "when": { "skin": "12" },
            "apply": { "textures": {"wall": "minecraft:blocks/glowstone"} }
        },
        {   "when": { "skin": "13" },
            "apply": { "textures": {"wall": "minecraft:blocks/sea_lantern"} }
        },
        {   "when": { "skin": "14" },
            "apply": { "textures": {"wall": "minecraft:blocks/diamond_block"} }
        },
        {   "when": { "skin": "15" },
            "apply": { "textures": {"wall": "minecraft:blocks/emerald_block"} }
        }
    ]
  }
}

But I still get only a huge number of MissingVariantException. It's as if the multipart is completely ignored. I checked it with json lint, so syntax is okay. Is there an explanation of multipart out there somewhere? Or, is it the wrong tool to use when separating tesxture assignment from model assignment?

PS: If my problem is really different from the OP, let me know so I can start a separate thread.

Quote

October 24, 20168 yr

@Winnetrie

Use the model "block/wall_post" as a parent instead of "builtin/generated"

@jeffryfisher

I might be wrong, but I believe that Forge's blockstate files make use of submodels not multiparts.

Also previously known as eAndPi.

"Pi, is there a station coming up where we can board your train of thought?" -Kronnn

Published Mods: Underworld

Handy links: Vic_'s Forge events Own WIP Tutorials.

Quote

October 24, 20168 yr

Forge's own blockstate is confusing as heck and has zero documentation. Only a select few people know how to use it 100%.

Essentially to get it working you need to do so many extra steps.

Multipart in forge submodel looks like this

 "forge_marker": 1,
    "defaults": {
        "model": "technorcery:depositsVat"
    },
    "variants": {
        "north": {
            "true": {
                "submodel": {
                    "spout_north" : {
                     "model": "technorcery:depositsVat_spout",
                    "uvlock": true
                    }
                }
            },
            "false": {}
        },
...etc

Also you need to register it as whatever the main node is in this case "variants" If you would call it "bigscarymain" then you register as that.

Also notice how each submodel is named . I don't know if the naming matters what it is but without it it won't work.

I recommend going vanilla json and forget about forge blockstates.

Disclaimer: I been told to keep my opinions to myself, to shut up and that I am spreading lies and misinformation or even that my methods are unorthodox and or too irregular. Here are my suggestions take it or leave it.

Quote

October 24, 20168 yr

Author

@Jeffreyfisher

I tried that approach first too with the multiparts, but i found out it was completely ignored (i think so)

It gave me those variant exception errors, so i tried another way. Like i posted in the first post.

This was working fine for except a small issue with the black/purple particles.

I don't mind if you post your problem with your walls here too, but a moderator could see this as a thread hijack

You have helped me alot already with other things, so np for me.

@Matryoshika

My first thoughts was also using wall_post, but that creates now a wall post in every wall piece. That's not how it should look like.

I found some small documentation about forge blockstates, there in a small example too they use submodels.

So i also believe we need to make use of submodels and not multiparts.

@trollworkout

Forge's own blockstate is confusing as heck and has zero documentation. Only a select few people know how to use it 100%.

It is only confusing if you don't understand it. It becomes more clear if you dig deeper in it. Perhaps you are right and only a few people know about this 100%, but isn't the purpose of this forum to share information and help others?

Essentially to get it working you need to do so many extra steps.

That's not true, in my opinion it takes less work.

The example you give is just the same as i did

I recommend going vanilla json and forget about forge blockstates.

The forge team is working very hard to give us all these things, yet you recommend people not to use an improvement?

The forge blockstates json is a great improvement and you better start learning how to use it.

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

October 24, 20168 yr

Author

Removing the entry from default gives me the best option for now, but it's not good enough for me.

I still see some wrong particles (black/pink). I have no clue why.

Does anyone know how to solve this?

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

October 24, 20168 yr

The "particle" texture is unspecified/missing.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable. If you think this is the case, JUST REPORT ME. Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

DO NOT PM ME WITH PROBLEMS. No help will be given.

Quote

October 24, 20168 yr

Author

The "particle" texture is unspecified/missing.

Most of the particles are normal, just a few (1-3) are not correct.

Does your solution still applies for this?

How would i add this in the json file.

here a screenshot 0ynrlb0

It was hard to capture it, but you see the wrong particles

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

October 24, 20168 yr

Forge's own blockstate ... has zero documentation.

mcforge.readthedocs.io has a detailed documentation of the Forge blockstate system. It also has documentation for other systems. You might want to check this out before complaining.

Don't PM me with questions. They will be ignored! Make a thread on the appropriate board for support.

1.12 -> 1.13 primer by williewillus.

1.7.10 and older versions of Minecraft are no longer supported due to it's age! Update to the latest version for support.

http://www.howoldisminecraft1710.today/

Quote

October 24, 20168 yr

Author

I managed to get a better screenshot of the problem i have:

009u188

You can see i have "normal" particles and untextured particles.

this is my blockstate file:

{
    "forge_marker": 1,
    "defaults": {
        
        },
    
    "variants": {
        "up": {
            "true": {
                "submodel": {"wall_up": {"model": "wall_post"}}
            },
            "false": {}
        },
        "north": {
            "true": {
                "submodel": {"wall_north": {"model": "wall_side","uvlock": true}}
            },
            "false": {}
        },
        "east": {
            "true": {
                "submodel": {"wall_east": {"model": "wall_side","y": 90,"uvlock": true}}
            },
            "false": {}
        },
        "south": {
            "true": {
                "submodel": {"wall_south": {"model": "wall_side","y": 180,"uvlock": true}}
            },
            "false": {}
        },
        "west": {
            "true": {
                "submodel": {"wall_west": {"model": "wall_side","y": 270,"uvlock": true}}
            },
            "false": {}
        },
        
        "type": {
            "raw": {
                "textures": {
                    "wall": "tem:blocks/chalkstone"
                    
                    
                }
            },
            "smooth": {
                "textures": {
                    "wall": "tem:blocks/smooth_chalkstone"
                    
                }
            },
            "bricked": {
                "textures": {
                    "wall": "tem:blocks/bricked_chalkstone"
                    
                }
            }
        },
        "type=raw": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/chalkstone"
                
            }
        },
        "type=smooth": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/smooth_chalkstone"
                
            }
        
        },
        "type=bricked": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/bricked_chalkstone"
                
            }
        }
    }
}

I hope someone can help me with this.

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

October 24, 20168 yr

If you have a missing texture, there has to be an error in the logs. Post them for help.

Don't PM me with questions. They will be ignored! Make a thread on the appropriate board for support.

1.12 -> 1.13 primer by williewillus.

1.7.10 and older versions of Minecraft are no longer supported due to it's age! Update to the latest version for support.

http://www.howoldisminecraft1710.today/

Quote

October 24, 20168 yr

Author

-- System Details --

Details:

Minecraft Version: 1.10.2

Operating System: Windows 10 (amd64) version 10.0

Java Version: 1.8.0_73, Oracle Corporation

Java VM Version: Java HotSpot 64-Bit Server VM (mixed mode), Oracle Corporation

Memory: 700684600 bytes (668 MB) / 1037959168 bytes (989 MB) up to 1037959168 bytes (989 MB)

JVM Flags: 3 total; -Xincgc -Xmx1024M -Xms1024M

IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0

FML:

Loaded coremods (and transformers):

GL info: ' Vendor: 'NVIDIA Corporation' Version: '4.5.0 NVIDIA 372.70' Renderer: 'GeForce GTX 960/PCIe/SSE2'

[20:56:37] [Client thread/INFO] [FML]: MinecraftForge v12.18.2.2099 Initialized

[20:56:37] [Client thread/INFO] [FML]: Replaced 232 ore recipes

[20:56:37] [Client thread/INFO] [FML]: Found 0 mods from the command line. Injecting into mod discoverer

[20:56:37] [Client thread/INFO] [FML]: Searching C:\Users\Timmy\Desktop\workspace1.10\run\mods for mods

[20:56:39] [Client thread/INFO] [FML]: Forge Mod Loader has identified 4 mods to load

[20:56:39] [Client thread/INFO] [FML]: Attempting connection with missing mods [mcp, FML, Forge, tem] at CLIENT

[20:56:39] [Client thread/INFO] [FML]: Attempting connection with missing mods [mcp, FML, Forge, tem] at SERVER

[20:56:39] [Client thread/INFO]: Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge, FMLFileResourcePack:Tim's Expansion Mod

[20:56:39] [Client thread/INFO] [FML]: Processing ObjectHolder annotations

[20:56:40] [Client thread/INFO] [FML]: Found 423 ObjectHolder annotations

[20:56:40] [Client thread/INFO] [FML]: Identifying ItemStackHolder annotations

[20:56:40] [Client thread/INFO] [FML]: Found 0 ItemStackHolder annotations

[20:56:40] [Client thread/INFO] [FML]: Applying holder lookups

[20:56:40] [Client thread/INFO] [FML]: Holder lookups applied

[20:56:40] [Client thread/INFO] [FML]: Applying holder lookups

[20:56:40] [Client thread/INFO] [FML]: Holder lookups applied

[20:56:40] [Client thread/INFO] [FML]: Applying holder lookups

[20:56:40] [Client thread/INFO] [FML]: Holder lookups applied

[20:56:40] [Client thread/INFO] [FML]: Configured a dormant chunk cache size of 0

[20:56:40] [Forge Version Check/INFO] [ForgeVersionCheck]: [Forge] Starting version check at http://files.minecraftforge.net/maven/net/minecraftforge/forge/promotions_slim.json

[20:56:40] [Forge Version Check/INFO] [ForgeVersionCheck]: [Forge] Found status: UP_TO_DATE Target: null

[20:56:40] [Client thread/INFO] [sTDOUT]: [winnetrie.tem.proxy.ClientProxy:preInit:21]: renders have been registered

[20:56:40] [Client thread/INFO] [FML]: Applying holder lookups

[20:56:40] [Client thread/INFO] [FML]: Holder lookups applied

[20:56:40] [Client thread/INFO] [FML]: Injecting itemstacks

[20:56:40] [Client thread/INFO] [FML]: Itemstack injection complete

[20:56:43] [sound Library Loader/INFO]: Starting up SoundSystem...

[20:56:43] [Thread-8/INFO]: Initializing LWJGL OpenAL

[20:56:43] [Thread-8/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)

[20:56:43] [Thread-8/INFO]: OpenAL initialized.

[20:56:43] [sound Library Loader/INFO]: Sound engine started

[20:56:47] [Client thread/INFO] [FML]: Max texture size: 16384

[20:56:47] [Client thread/INFO]: Created: 16x16 textures-atlas

[20:56:48] [Client thread/ERROR] [FML]: MultiModel minecraft:builtin/missing is empty (no base model or parts were provided/resolved)

[20:56:49] [Client thread/ERROR] [FML]: MultiModel minecraft:builtin/missing is empty (no base model or parts were provided/resolved)

[20:56:49] [Client thread/INFO] [FML]: Injecting itemstacks

[20:56:49] [Client thread/INFO] [FML]: Itemstack injection complete

[20:56:49] [Client thread/INFO] [FML]: Forge Mod Loader has successfully loaded 4 mods

[20:56:49] [Client thread/INFO]: Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge, FMLFileResourcePack:Tim's Expansion Mod

[20:56:52] [Client thread/INFO]: SoundSystem shutting down...

[20:56:52] [Client thread/WARN]: Author: Paul Lamb, www.paulscode.com

[20:56:52] [sound Library Loader/INFO]: Starting up SoundSystem...

[20:56:52] [Thread-10/INFO]: Initializing LWJGL OpenAL

[20:56:52] [Thread-10/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)

[20:56:52] [Thread-10/INFO]: OpenAL initialized.

[20:56:53] [sound Library Loader/INFO]: Sound engine started

[20:56:56] [Client thread/INFO] [FML]: Max texture size: 16384

[20:56:56] [Client thread/INFO]: Created: 1024x512 textures-atlas

[20:56:57] [Client thread/ERROR] [FML]: MultiModel minecraft:builtin/missing is empty (no base model or parts were provided/resolved)

[20:56:57] [Client thread/WARN]: Skipping bad option: lastServer:

[20:56:58] [Realms Notification Availability checker #1/INFO]: Could not authorize you against Realms server: Invalid session id

this: [Client thread/ERROR] [FML]: MultiModel minecraft:builtin/missing is empty (no base model or parts were provided/resolved)

comes up 6 times. If i provide a model in the default section of the blockstate file this error is gone, but the problem persists

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

October 24, 20168 yr

"type=raw": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/chalkstone"
                
            }
        },

"type=raw" doesn't work that way, you have to do it just like the other variants.

Also, you can specify your main model in de default section, instead of 3 times in the type variant.

Don't PM me with questions. They will be ignored! Make a thread on the appropriate board for support.

1.12 -> 1.13 primer by williewillus.

1.7.10 and older versions of Minecraft are no longer supported due to it's age! Update to the latest version for support.

http://www.howoldisminecraft1710.today/

Quote

October 24, 20168 yr

Author

The piece you show is to create my item models wich are working fine.

If this isn't the proper way how to do it then?

How do i specify my main model in the default section?

What is the main model anyway?

EDIT:

I tried many things now and it only makes it worse.

If i set a main model in my default section all my walls look like that.

I also need it 3 times because i need 3 different textures for the items.

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

October 25, 20168 yr

My custom walls are working now. I had item model files left over from mc 1.8, so I gave up trying to teach the blockstates json to do inventory. Here's one of my blockstates files that handles blocks only:

{
  "forge_marker": 1,
  "variants": {
      "up" : {
	"true"	: {"submodel": {"wall_up"    : {"model": "wall_post" }}},
	"false"	: {}
      },
      "north" : {
	"true"	: {"submodel": {"wall_north" : {"model": "wall_side", "uvlock": true }}},
	"false"	: {}
      },
      "east" : {
	"true"	: {"submodel": {"wall_east"  : {"model": "wall_side", "uvlock": true, "y": 90 }}},
	"false"	: {}
      },
      "south" : {
	"true"	: {"submodel": {"wall_south" : {"model": "wall_side", "uvlock": true, "y": 180 }}},
	"false"	: {}
      },
      "west" : {
	"true"	: {"submodel": {"wall_west"  : {"model": "wall_side", "uvlock": true, "y": 270 }}},
	"false"	: {}
      },
      "skin" : {
        "0":  { "textures": { "wall": "blocks/stonebrick" }},
        "1":  { "textures": { "wall": "blocks/stonebrick_mossy" }},
        "2":  { "textures": { "wall": "blocks/stonebrick_cracked" }},
        "3":  { "textures": { "wall": "blocks/stonebrick_carved" }},
        "4":  { "textures": { "wall": "blocks/brick" }},
        "5":  { "textures": { "wall": "blocks/hardened_clay" }},
        "6":  { "textures": { "wall": "blocks/netherrack" }},
        "7":  { "textures": { "wall": "blocks/quartz_block_chiseled" }},
        "8":  { "textures": { "wall": "blocks/obsidian" }},
        "9":  { "textures": { "wall": "blocks/sandstone_normal" }},
        "10": { "textures": { "wall": "blocks/sandstone_carved" }},
        "11": { "textures": { "wall": "blocks/stone" }},
        "12": { "textures": { "wall": "blocks/stone_granite_smooth" }},
        "13": { "textures": { "wall": "blocks/stone_diorite_smooth" }},
        "14": { "textures": { "wall": "blocks/stone_andesite_smooth" }},
        "15": { "textures": { "wall": "blocks/end_stone" }}
      }
  }
}

Quote

October 25, 20168 yr

Author

I have the feeling people do not understand what the problem is i have!

My inventory works fine, my walls are working fine. Look at the pictures i posted.

This is my blockstate file again:

{
    "forge_marker": 1,
    
    "variants": {
        "up": {
            "true": {
                "submodel": {"wall_up": {"model": "wall_post"}}
            },
            "false": {}
        },
        "north": {
            "true": {
                "submodel": {"wall_north": {"model": "wall_side","uvlock": true}}
            },
            "false": {}
        },
        "east": {
            "true": {
                "submodel": {"wall_east": {"model": "wall_side","y": 90,"uvlock": true}}
            },
            "false": {}
        },
        "south": {
            "true": {
                "submodel": {"wall_south": {"model": "wall_side","y": 180,"uvlock": true}}
            },
            "false": {}
        },
        "west": {
            "true": {
                "submodel": {"wall_west": {"model": "wall_side","y": 270,"uvlock": true}}
            },
            "false": {}
        },
        
        "type": {
            "raw": {
                "textures": {
                    "wall": "tem:blocks/chalkstone"
                    
                    
                }
            },
            "smooth": {
                "textures": {
                    "wall": "tem:blocks/smooth_chalkstone"
                    
                }
            },
            "bricked": {
                "textures": {
                    "wall": "tem:blocks/bricked_chalkstone"
                    
                }
            }
        },
        "type=raw": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/chalkstone"
                
            }
        },
        "type=smooth": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/smooth_chalkstone"
                
            }
        
        },
        "type=bricked": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/bricked_chalkstone"
                
            }
        }
    }
}

I have a working item for my wall

I have a fully working wall

I have a small untextured particle issue. Just a few are untextured.

I can't find out why this happens.

I have still this error too:

[Client thread/ERROR] [FML]: MultiModel minecraft:builtin/missing is empty (no base model or parts were provided/resolved)

If i have to provide a base model in the default section, wich do i use? Is there even a base model for walls?

I tried these already:

-builtin/generated --> with this all the particles are untextured

-wall_inventory --> all placed walls looks like the inventory model

-wall_post --> all placed walls have a wallpost inside it

-wall_side --> all placed walls are equipped with a side piece

-cube_all --> yes i was so desperate i tried it.....but ofc black purple squares

I really don't know what to do anymore.

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

October 25, 20168 yr

You should be able to create an empty model like this to use as the default and then specify the

"particle"

texture in the blockstates file like this.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Quote

October 25, 20168 yr

Author

You should be able to create an empty model like this to use as the default and then specify the
"particle"
texture in the blockstates file like this.

Thank you so much, i already came up with the idea to make a custom empty model, but i had no json code inside it.

I tried your approach and yes that works fine now.

here is what i have now:

{
    "forge_marker": 1,
    "defaults": {
        "model": "tem:dummy",
        "textures": {
            "particle": "tem:blocks/bricked_chalkstone"
        }    
    },
    
    "variants": {
        "up": {
            "true": {
                "submodel": {"wall_up": {"model": "wall_post"}}
            },
            "false": {}
        },
        "north": {
            "true": {
                "submodel": {"wall_north": {"model": "wall_side","uvlock": true}}
            },
            "false": {}
        },
        "east": {
            "true": {
                "submodel": {"wall_east": {"model": "wall_side","y": 90,"uvlock": true}}
            },
            "false": {}
        },
        "south": {
            "true": {
                "submodel": {"wall_south": {"model": "wall_side","y": 180,"uvlock": true}}
            },
            "false": {}
        },
        "west": {
            "true": {
                "submodel": {"wall_west": {"model": "wall_side","y": 270,"uvlock": true}}
            },
            "false": {}
        },
        
        "type": {
            "raw": {
                "textures": {
                    "wall": "tem:blocks/chalkstone"
                    
                    
                }
            },
            "smooth": {
                "textures": {
                    "wall": "tem:blocks/smooth_chalkstone"
                    
                }
            },
            "bricked": {
                "textures": {
                    "wall": "tem:blocks/bricked_chalkstone"
                    
                }
            }
        },
        "type=raw": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/chalkstone"
                
            }
        },
        "type=smooth": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/smooth_chalkstone"
                
            }
        
        },
        "type=bricked": {
            "model": "wall_inventory",
            "textures": {
                "wall": "tem:blocks/bricked_chalkstone"
                
            }
        }
    }
}

The particle is now a defined texture, but can it be variable too or does this not matter?

The 3 stone types are almost the same so you won't notice a different color,but what if you have a wall in 16 colors?

Would the default particle for example white, be in every other block?

I don't know if it is working like this, just wondering.

Maybe i can use an empty texture for it?

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

October 25, 20168 yr

The particle is now a defined texture, but can it be variable too or does this not matter?

The 3 stone types are almost the same so you won't notice a different color,but what if you have a wall in 16 colors?

Would the default particle for example white, be in every other block?

I don't know if it is working like this, just wondering.

Maybe i can use an empty texture for it?

The

"particle"

texture can be a reference to another texture (like in my example) or defined separately for each value of the

type

property.

Setting it to

"#wall"

should use the

"wall"

texture for the particles.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Quote

October 25, 20168 yr

here is what i have now...

You have two sets of wall types at the bottom of the blockstates file. Are they doing the same thing? What's the difference between writing "raw" versus writing "type=raw"? Do both sets need to be there, or could they be consolidated?

It looks as if you might have solved the inventory texturing inside the blockstates file, but I'm unsure.

Quote

October 25, 20168 yr

Author

Yes i have 2 sets of types. 1 is for the block and the other is for the item (inventory).

I'm not sure what the best way is to do this, but for me this works fine.

the second set wich is called (type=raw) for example does not need to be the same as the first set.

It could be for example (myitem=rough). Those are only references to be used in the renderRegistry:

registerMetaRender(chalkstonewall,0,"type=raw");
	registerMetaRender(chalkstonewall,1,"type=smooth");
	registerMetaRender(chalkstonewall,2,"type=bricked");

the method is this:

private static void registerMetaRender(Block block, int meta, String variant){
	ModelLoader.setCustomModelResourceLocation(Item.getItemFromBlock(block), meta, new ModelResourceLocation(block.getRegistryName(),variant));	
}

Getting the inventory item was never a problem, i only had this untextured glitch in the blocks particle effect.

Try out my new Modpack for MC 1.15.2

https://www.curseforge.com/minecraft/modpacks/terran-civilization

Quote

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.

Reply to this topic...

https://forums.minecraftforge.net/topic/42631-mc-110-custom-wall-json-issue/

Followers

Go to topic listing

IPS spam blocked by CleanTalk.

Announcements

Orbital strike cannon fishing rod mod

was focused on school so didnt respond u think ur gonna get 1.21+ done by this week? @FoxyWoxy

By Astoxy · 3 hours ago3 hr
How to add my mob to another mod's biome in 1.20.1.

You can add mob spawns using Forge's Biome Modifiers feature. I won't go into details on how to use a data generator for them, but here's a simple example:
{ "type": "forge:add_spawns", // Required "biomes": "#namespace:biome_tag", // Accepts a biome id, [list of biome ids], or #namespace:biome_tag "spawners": { "type": "namespace:entity_type", // Type of mob to spawn "weight": 100, // int, spawn weighting "minCount": 1, // int, minimum pack size "maxCount": 4 // int, maximum pack size } }This JSON file would go somewhere like this: data/modid/forge/biome_modifier/your_biome_modifier.json

By Jonathing · 14 hours ago14 hr
How to change player renderer and transform model parts?

I have been trying for a while now to make a custom player renderer, and replace the vanilla player renderer with it. So far I've come up with a custom player renderer class that extends vanilla PlayerRenderer:
package com.FireDude123.BOTW.entity.renderer; import com.mojang.blaze3d.vertex.PoseStack; import net.minecraft.client.player.AbstractClientPlayer; import net.minecraft.client.renderer.MultiBufferSource; import net.minecraft.client.renderer.entity.player.PlayerRenderer; import net.minecraft.client.renderer.entity.EntityRendererProvider; import net.minecraftforge.client.event.RenderPlayerEvent; import net.minecraftforge.common.MinecraftForge; public class PoseablePlayerRenderer extends PlayerRenderer { public PoseablePlayerRenderer(EntityRendererProvider.Context ctx, boolean slim) { super(ctx, slim); System.out.println("here too"); } @Override public void render(AbstractClientPlayer p_117788_, float p_117789_, float p_117790_, PoseStack poseStack, MultiBufferSource p_117792_, int p_117793_) { System.out.println("didnt get here lol"); model.leftArm.xRot=(float)Math.toRadians(160); super.render(p_117788_, p_117789_, p_117790_, poseStack, p_117792_, p_117793_); } } As you can see, the intended purpose of this is to raise the player's left arm by 160 degrees. However, combined with this logic in ClientModEvents:
@Mod.EventBusSubscriber(modid = MODID, bus = Mod.EventBusSubscriber.Bus.MOD, value = Dist.CLIENT) public static class ClientModEvents { @SubscribeEvent public static void onClientSetup(FMLClientSetupEvent event) { EntityRenderers.register((EntityType<? extends AbstractClientPlayer>)(EntityType<?)EntityType.PLAYER, ctx -> new PoseablePlayerRenderer(ctx, true)); EntityRenderers.register(Entities.MAGNESIS_BLOCK.get(), com.FireDude123.BOTW.entity.renderer.BlockDisplayRenderer::new); EntityRenderers.register(Entities.REMOTE_BOMB.get(), ThrownItemRenderer::new); EntityRenderers.register(Entities.CRYONIS_ICE.get(), com.FireDude123.BOTW.entity.renderer.BlockDisplayRenderer::new); EntityRenderers.register(Entities.STASIS_BLOCK.get(), FallingBlockRenderer::new); } @SubscribeEvent public static void registerLayerDefinitions(EntityRenderersEvent.RegisterLayerDefinitions event) { event.registerLayerDefinition(new ModelLayerLocation(new ResourceLocation(BOTW.MODID, "paraglider"), "main"), ParagliderLayer::createBodyLayer); } }(I also have a paraglider layer here for something else, it's working perfectly fine, also I used the slim setting because the player is slim in 1.20.1 forge)
This logic isn't replacing the renderer, as far as I can tell. Can someone please advise as to why, and how to fix it?

By FireDude123 · Posted Yesterday at 12:07 AM1 day
How to add my mob to another mod's biome in 1.20.1.

I'm on 1.20.1 and was wondering if there was a way to add a mob I am going to make to a other mod's biome (Regions Unexplored in this case). I am trying to figure this out before I start coding the mod. Could someone point me to a good guide on this? I saw some things about biome modifier's but all the resources are either to short, unhelpful or for a different version. Thanks in advance. (i am a beginner but i have java and modding knowledge so this isn't like a "i am new and don't know anything about coding" problem btw)

By ilov3gam3z · Posted Wednesday at 04:08 PM1 day
Help with file conversion

Many Forge users seek help with file conversions. Similarly, managing your health can benefit from structured tools like the https://wellness-app.com/calculator/fasting-calculator/ and a free intermittent fasting calculator. These tools help you plan and personalize your fasting and eating windows based on your lifestyle and goals. By entering your preferred fasting duration and meal times, you receive a tailored schedule that makes intermittent fasting easier to follow. Just as mastering file conversions improves modding success, using a fasting calculator brings clarity and structure to your health routine, supporting better results over time.

By Brialeblanc · Wednesday at 10:34 AM2 days

Jimmy1166

Sign In

MC 1.10+ Custom wall JSON issue

Featured Replies

Join the conversation

Posts

Orbital strike cannon fishing rod mod

How to add my mob to another mod's biome in 1.20.1.

How to change player renderer and transform model parts?

How to add my mob to another mod's biome in 1.20.1.

Help with file conversion

Who's Online (See full list)

Important Information

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)