Blockstates

Supported MCreator versions
2023.4
2024.1
2024.2
Tags / plugin type
Java plugin
Procedures
blockstates
Downloads:
7169
Upvotes: 74
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.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.zipUploaded on: 03/07/2024 - 08:42   File size: 60.45 KB
Blockstates v1.3.2 (MCreator 2024.1 ONLY) - blockstates_1.zipUploaded on: 04/25/2024 - 07:57   File size: 71.57 KB
Blockstates v1.4 (MCreator 2024.2 ONLY) - blockstates.zipUploaded on: 07/19/2024 - 15:43   File size: 48.04 KB

Comments

can you make transitions between states (if not will you consider adding it)?

there is no transparent element parameter in the model in the block state settings, are you planning to add it in the future?

I have problem with the 2024.2 version of the plugin (mc: 1.20.1 forge). The workspace was created in 2024.1 but the plugin got added to it the first time in the 2024.2

Everytime I change a blockstate with a procedure and try it out ingame I get a missing texture. In the F3 menu it shows the correct blockstate. Does anyone what i could be doing wrong and if/or how I can fix that problem?

If I could make a suggestion, it would be cool to have blockstate groups, similar to the loot table element.

On each group, you could then select whether it's a numeric state, one with a string name, or a boolean, as well as give the group a name. Similar to how observers have multiple states. I know it is possible to just use numeric IDs for everything, but it would still be useful for remembering specific states, organization, and full debug stick compatibility.

i heard you can make cake (block types) and stuff like that in this plugin, is that true?

Is there way to update all instances of a block in the world? For example, I am trying to change a texture from locked to unlocked (for every instance of that block in the world) after a player completes an advancement