#my custom geometry block's texture is broken for some reason

1 messages · Page 1 of 1 (latest)

tame path
#

when i put the block in minecraft, it's textures are completely broken meanwhile in blockbench everything seems fine. no idea what went wrong, can someone tell me? It's in box-UV btw.

#

and now for no reason blockbench opens it as an bedrock entity even though i made it as a block in the first place :/

jolly hatch
jolly hatch
#

The Problem (simple)

Your block had holes in-game because:

Minecraft Bedrock did not accept your UVs
Some cube faces were not clearly defined

Result:

  • Blockbench → looks fine
  • In-game → some faces are invisible ❌

Why did it still work in Blockbench?

Blockbench is forgiving:

  • It shows faces even if UVs are wrong
  • It guesses the texture

Minecraft Bedrock is strict:

  • No proper UV = no face
  • Not explicitly defined = invisible

The main mistake

You were using:

"uv": [0, 0]

This means:

“Minecraft, figure out the texture placement by yourself”

Bad idea in Bedrock
Some faces end up with no texture at all


The solution (very simple)

Per-Face UV

Instead of one UV for the whole cube:

  • 1 UV per face
  • north, south, east, west, up, down

Example:

"north": { "uv": [8, 8], "uv_size": [4, 5] }

This clearly tells Minecraft:

  • which face
  • where to start in the texture
  • how big the texture area is

Minecraft loves this ✔


What to remember

Before

1 cube
→ 1 global UV
→ Minecraft gets confused
→ holes

After

1 cube
→ 6 faces
→ 6 explicit UVs
→ no holes

Golden rule for Bedrock

If it works in Blockbench but not in-game → UV problem

Always use Per-Face UV for custom models


In one sentence

Every face must explicitly know which part of the texture it uses, otherwise Minecraft removes it.

#

If you need anything else, let me know ^^

tame path
#

holy ai

jolly hatch
#

What, how’s that? I just asked the AI to explain it to you because me and English makes two

jolly hatch
# tame path holy ai

So now, especially for your blocks that have elaborate models, do it on the UV side. It will avoid this kind of problem. I never had it, but I knew it came from the geo file