Started by
OMGitsMiniMe
on
Topic category: Feature requests and ideas for MCreator
It would be super nice to have the option to add custom models for the block base types, such as custom models for fences and slabs instead of using the default models with a different texture. (edit I see now after reading through the code for the fences and stairs and glass panes how much mojang has changed the way those blocks work since I first started modding, and also that it would be a nightmare to be able to set custom bounding boxes for custom modeled base blocks)
Edited by OMGitsMiniMe on Sat, 05/28/2022 - 04:14
MCreator already has the defaults. Add a new block, name it, add texture, look at Block base (click the drop down menu), select the type, change additional values/triggers/conditions/particles, save and test. For custom models use Blockbench, use your imagination, and practice until you get it right. One step at a time.
Try to follow this tutorial, then create your own custom blocks. https://www.youtube.com/watch?v=B62Rt6KlAbI
Have fun.
That's the thing if I select that I want to make a slab it only lets me select a single texture and not a custom model. For instance say I want my slab to have a hole in the center of it for whatever reason, you can't do that at this current time. I would instead have to code my own triggers to make a janky version of a slab when instead if mCreator allowed a custom model to be used with block bases then it would be so much easier. of course for custom fences it would require 5-6 different models but it would be easier then having to follow this video and do it the hard and very unnecessary way. https://www.youtube.com/watch?v=fXX0BEpcfr4
I know how to make models and custom blocks. but it would be nice to be able to have custom modeled Base Blocks instead of using the default models with a simple retexture.
https://www.youtube.com/watch?v=6CuKFPOpX3I Here is what I mean by custom modeled Base Blocks
and here is an example of what a model for a custom modeled base slab would be.
https://drive.google.com/file/d/128t6UU1q8CW7-Wo_yNdUjohXaF8SYEKA/view?…
Ive found a work around that requires a lot of extra work but ill release a video soon and post it here to show the work around as well as an easy way fro them to implement this as a feature
The developers have provided some default blocks and models (entities) to help us with a starting point, in order to have better models we must use our creativity (and a 3d modeling software of course). They have been doing their best for thousands of hours (over 10 years) simplifying the coding, adding the default blocks, adding some default models (entities), providing procedure blocks, allowing plugins to be added, and releasing an up-to-date modding tool for everyone ... absolutely free!
And yes ... it does require a lot of work.
Yes I understand that in order to have custom modeled blocks we have to make them ourselves I've been modding and making games for 10 years I understand that stuff and I have made plenty of mods with custom models. Im saying that the default base block types (stair, fence, slab, pane, end rod, ect.) don't allow the use of custom models and only use the default model, so I created this feature request post to request the feature of custom models for block types. such as making a stair block using the Block Base provided in MCreator but instead of using the default model that has 2 steps I could use a custom model I made to have it instead have 3 or 4 or even 8 steps rather than the default two. Last night I edited the json files for the slab Block base and was able to make a slab that looks like the image I posted above of the round log slab by changing the blockstate model files. For a feature like this all that's required to make the custom model is to add a selector for how ever many block models the Block base requires( in the slabs case its 3, Bottom half, top half, and full block) then alow the user to select their custom models that they made or downloaded. the biggest issue with this is the bounding boxes would be a bit more difficult to implement for each custom model.
There is however a work around that requires you to create multiple different blocks and use very complex triggers to detect neighboring blocks and set them to the right model and I made this feature request to suggest a way to save people from having to do that.