Started by
thunderrock424242
on
Topic category: Feature requests and ideas for MCreator
Sometimes, you need to lock base files so you can manually change them. If something is wrong, let's say you know how to code very well, but you have to change some Gradle or some source code things the files will be overridden because that's what mcreaotr does. what you should do In workspace settings, you should add an option to have the files not be overridden, like a check box in advanced settings.
You can use user code blocks for this, basically if you put custom code into regions of custom code, this code will be kept across builds
I need to lock the code to solve an issue
so I'm having issues with this as well..
I'm trying to assign custom item properties to a blockitem.
heres my attempt at a workaround..
and it keeps re-writing the blocks in, so its giving an error, theyre "defined twice".
(the part I scribbled out, I wish wasnt regenerating)
I cant figure how to define custom item properties with this setup.. I agree with this post by thunderrock after a few hours of scratching my head, rolling around in depression, several more attempts, and still cant make it work with it re-writing it.
for clarity, heres how it should look.... but this setup is making it.. erm.. difficult?
I've also tried defining the item properties in a separate file, as a fluid does with a fluid bucket item, and mcreator deletes that file as well. Its doomed.