Closed VolticFroogo closed 3 years ago
I am making the assumption that the claim block material will be exclusively used for claim blocks (i.e. not used for anything else). Is this an okay assumption, or should I use NBT data to differentiate claim blocks from other regular blocks?
The preferred option would be to use NBT data to differentiate claim blocks from other regular blocks ONLY IF we are still able to use the custom textures we've already made for the configurable claim blocks.
From what I recall, as I will be using custom NBT data with no collisions with regular Minecraft, it should not break custom textures. I will change material differentiation to NBT data in the next update.
This has been implemented; the blocks are using server-side only metadata, so no collisions should be possible. Items are using 1.16's PersistentDataContainer, yet again, with no collisions possible.
Currently, the customisable attributes on the block are: its material (not exclusive), name, and lore. Are there any more customisable attributes you would need?
Not to my knowledge, no! Unless @NotARobotII has any other ideas.
Frankly, I'm not sure how we denote in a resource pack that a custom textures belongs to a custom NBT thing rather than a standard Minecraft block. But I won't be the one implementing the custom textures anyways, so perhaps there is no need for me to understand that!
Thanks for keeping me in the loop, @VolticFroogo!
Okay, sounds good!
If any other attributes should be added just reopen this issue.
Add blocks, which upon placement, will claim an area as a home or outpost chunk.
These blocks should be configurable in the generic config file.