[Feature Request] Per-Blockstate Model & Texture UI – Similar to Entity Model Layers

Post:

Hi MCreator devs!

I’d love to suggest a feature that improves how we assign visuals to blockstates, using a UI similar to what currently exists for entity model layers (see attached screenshot for reference).

🧩 Idea: Per-Blockstate Model & Texture Assignment UI

When creating or editing blocks with multiple states (e.g., stairs, fences, or complex custom blocks), we often deal with many blockstates like:

• inner_left
• outer_right
• top
• bottom
• torches
• powered
• redstone
• rails
• etc
• custom_end_portal_frame_colors
• boats
• chests
   

Right now, assigning different models/textures for each state requires editing blockstate JSON files manually. This could be made much easier with a built-in UI, like how entity model layers work.

🛠 Proposed Feature Flow:

1. When selecting a base model like stairs, MCreator recognizes its typical blockstates.

2. For each detected blockstate (like inner_right, top, etc.), it asks:

   "Do you want to use the default model or a custom model/texture for this state?"

3. If "custom" is selected:
   • A new tab opens, similar to the Model Layers tab for entities.
   • It allows the user to set:
     • Model file
     • Texture file
     • Optional: glow, overlays, or display conditions

🎯 Why This Matters:

This makes complex blocks way more approachable in MCreator, letting creators:

• Assign unique visuals to blockstates visually, without JSON edits.
• Quickly create advanced multi-state blocks (stairs, fences, custom variants).
• Reuse existing systems in MCreator (like entity visuals) to improve block UX.

📎 Visual Example:

Here’s what inspired this suggestion — the current Model Layers UI for entities:

Thanks for considering this! It would make a massive difference for custom block design in MCreator.

_____________________________

I know you already are working on blockstates in your update but still is a bit confusing to understand or how to use, this would be very helpful. 

Why This Is Better Than the Current or Upcoming System:

Currently, MCreator generates blockstate .json files, but it doesn’t provide a visual way to link specific models or textures to individual blockstates directly in the UI. Even in the upcoming update, while improvements are being made, the setup still appears confusing or limited for users who want more control or clarity over visual states.

This suggestion offers:

✅ Pros:

• A visual, user-friendly UI for managing blockstate visuals (no JSON editing required).
• Reuses existing logic from entity model layers, reducing development overhead.
• Makes it more intuitive for creators to understand which state links to which model/texture.
• Reduces user error and time spent debugging missing or mismatched states.

⚠️ Possible Cons:

• Requires UI adjustments and logic linking to blockstate identifiers.
• May slightly increase the complexity of the block editor (though it's optional and behind a toggle).

By making this part of the block editor itself (rather than relying only on file generation), it aligns better with MCreator’s goal of being powerful but accessible—especially for creators who want to push visual customization without diving deep into JSON structures.

Thanks again for considering this!