Blockstates

Supported MCreator versions
2023.4
2024.1
2024.2
2024.3
Tags / plugin type
Java plugin
Procedures
blockstates
Downloads:
8919
Upvotes: 92
About the plugin

Blockstates is a plugin which allows you to define multiple states in which your blocks change textures, models, bounding boxes and light levels. It introduces the blockstates mod element and multiple procedure blocks with which you can control the current blockstate your block uses.

 

This is a java plugin and requires java plugins to be enabled.

 


Changelog

v1.5.1
-Fixed the latest 2024.3 patch breaking the UI

v1.5
-Ported to 2024.3 and neoforge 1.21.1

v1.4
-Ported to 2024.2 and neoforge 1.20.6

v1.3.2
-Updated the block template to include a bugfix from 2024.1 patch 2

v1.3.1
-Updated to work with MCreator 2024.1.15821

v1.3
-Support for MCreator 2024.1
-Support for neoforge 1.20.4

v1.2.2
-Fixed blocks having build errors in 1.19.4

v1.2.1
-Fixed blockstate textures not working in 1.19.2
-Fixed crashing when using bounding box offset with blockstates

v1.2
-Blockstates can now have different bounding boxes
-Blockstates can now have different luminance (light level)
-Added the cross and crop base models to blockstates

v1.1
-Fixed template errors when multiple blocks and blockstates were present
License
MIT License

Plugin downloads
Blockstates v1.2.2 (MCreator 2023.4 ONLY) - blockstates.zip Uploaded on: 03/07/2024 - 08:42   File size: 60.45 KB
Blockstates v1.3.2 (MCreator 2024.1 ONLY) - blockstates_1.zip Uploaded on: 04/25/2024 - 07:57   File size: 71.57 KB
Blockstates v1.4 (MCreator 2024.2 ONLY) - blockstates.zip Uploaded on: 07/19/2024 - 15:43   File size: 48.04 KB
Blockstates v1.5.1 (MCreator 2024.3 ONLY) - blockstates_0.zip Uploaded on: 10/31/2024 - 07:45   File size: 48.96 KB

Comments

are the plugins being worked on for 2024.1 patch 3? My intention is not to rush you, but to find out.

One Question:
I'm using the Forge 1.19.2 Generator Plugin and I use Blockstates for changing Textures. But for some odd reasons I get missing Textures on the Block.

Do you know the reason why?

Also I'm using 2024.1.

Hi! I found the issue and its an easy fix! What worked for me is that I copied "blocks" folder and pasted it in the same place with a folder name "block", it is in workspace folder: src/main/resources/assets/modname/textures. Maybe you will have "block" folder first then do the same but rename copied folder "blocks" (what worked the best for me, is that same textures were in both folders even if they were dupicates, what happends is that 1.19.2 has just diffrent folder name from 1.19.4 and above and plugin works in the newer one "blocks" if you change minecraft version, the folder will delete, so keep in mind to just copy and paste all textures in a renamed folder each time you switch to 1.19.2) hope I helped :)

Hi, so there seems to be a problem where when a procedure tries to get the block state of a block it appears to return the wrong blockstate leading to unexpected behavior.

There is a problem where blockstates resets or keep NBT data for themself instead for the entire block
Can you make it soo that blockstate does not affect NBT?

EDIT: Nevermind...
Fixed that issue although problem is partially on Blockstate side too but can bypass it

Explanation: I had machine that stores energy and that works fine
However I have set it to set stored energy value to 0 whenever it places and when blockstate changes to Default, It treat it as the block was placed again somehow

Quick Question
Is Blockstate 0 the default one or I need to make new blockstate to have for example Furnace off?

Can I change the textures of items instead of blocks? (For example fishing rod - changes texture when cast)

Could you add perhaps an advanced feature of adding Boolean and string Properties and also multiple blockstates?

Can i make a chest with an animation just like the vanilla?