Topic category: Feature requests and ideas for MCreator
I'd like a crop element to be added to simplify the process of making actually growable crops that are compatible with mods.
Reason being, this is one of the only vanilla functions remaining that is extremely difficult to replicate without breaking directly into coding it manually. The current tutorial for crops is not only outdated, but it is incompatible with mods that affect crops. We basically have to mimic the process with procedures and hope it works, which is a lengthy process to do for any mods with several crops in it, and it makes it harder for our mods to be compatible.
My hope is that a Crop Element would simplify this process like it has done for Saplings & Features, where you can just input the various settings you need, the textures of each growth stage, and make it so that anyone can make a mod with crops in it.
All we would need for settings is:
Time it takes to grow (Age)
Textures for each growthstage (Blockstate)
Blocks it can grow on (Block)
Item used to plant (Item/Food)
Item retrieved on break (Item/Loot Table)
My reason for needing this is I have 2 mod ideas that are ready to be built, textures wise, but I cannot get them off the ground without crops, and unfortunately I've not managed to figure out how to program these crops myself.
Hopefully this can be added officially (or as a Plugin)
In fact, just like godot, MCreator also has its own design aesthetics - elementization For your needs, you only need to create multiple Block elements of different ages and place them one by one in the Procedure
don't do that, all you need for a crop is one block element with blockstate "age" (which you can select using the "already existing blockstates") and then just add all the crop logic using procedures (which means one that just increases crop age, which can be done using the [set/get integer property "age"] on tick, and another one that makes sure bonemeal works properly), and then you're gonna have to edit the files for blockstates to work (this is explained here).
Both of these solutions still ignore the problem that making crops is TIME CONSUMING currently, which doesn't match how the rest of the program handles basic vanilla features.
Not to mention mod incompatibility that comes with the procedures method, and the problem of MCreator just not allowing you to change the textures of the blockstate json within the program itself.
An actual crop element would make it simple to add new crops, which is what the program currently does not do.
The biggest reason it needs an element is that there is no compatibility when using procedures for any part of it.
Sure you can mimic it, but you aren't making a crop, you're making a block that looks like a crop. Which makes the many mods affecting crops, not work at all with your mod.
i agree when you say that we need a crop element (because it's actually quite easy to make one, the whole logic is almost just changing the Block type to CropBlock type), but how is making one block time consuming? the hardest thing you'd need is changing blockstates, nothing else.
Well by, time consuming, I mean relative to everything else in the program. Especially should I decide to add crops in bulk. It's just much less time spent on things in general when I can just duplicate the element I had before and know it'll work immediately.
Whereas within the code has a few more steps & is a bit more involved. It's not much time, but it adds up when you're working on many crops. And the program isn't going to regenerate this code when you update versions, meaning you may have to just redo it.
I would love to see crop elements in the future! That is, if it gets implement on Mcaddon! (I'm still clinging onto hope :D )