Started by
MeepJJ
on
Topic category: Feature requests and ideas for MCreator
Hi! I've recently hit a roadblock because of MCreator's limited nbt functions. Here are some ideas that might be worth looking into:
- All nbt created/modified inside procedures is automatically put inside {ForgeData:{here}}. Although this prevents accidental overwriting vanilla block data, in some cases it may be necessary. An option to read/write nbt data outside of ForgeData would be appreciated. This could come in handy if you were making a mod where you can lock/unlock chests with keys, etc.
- String-type nbt would also be very helpful in cases like recording the name of the last player who opened a specific chest, maybe testing if an item's name changed, etc. This would open up many possibilities in retaining information.
Thanks for taking the time to read my suggestions. I am hopeful that these might be considered. :)
I will see what can be done.
The reason why this happens is that MCreator uses TileEntity#getTileData() that returns the ForgeData from the NBTTagCompound of the TileEntity. This is fine if you want to add your own data to an external TileEntity. If you want to override a vanilla tag, you could possibly force the TileEnttiy to read from a modified version of it own NBT.
I'm very new to Java. Do you know of any sources that might help me figure out how to do what you suggested?