Im not sure this should be in structure or gameplay. But I think it affects more about gameplay.
A lot of potential game changing ideas can come about and solve many current issues with minecraft if each block saved the UUID of the last player to place it. Default UUID of blocks generated can be NULL.
Here are the list of things that it can fix or features it can produce.
1. Control mob spawning, like in pillager spawning, pillagers currently spawn inside player made buildings. Simple control this by not allowing those mobs to spawn on blocks that have a UUID. This can also be applied for other hostile mob spawning and wandering merchants appearing inside player built structures.
2. This can also be used for pre generated structures like villages. If player takes a block of hay from a village it can agro an iron golem or give negative popularity.
3. Reduce griefing from other players, possibly implement a increased block breaking time for players who dont have the same UUID as the block.
3a . Friend multiplayer option, where friends can utilize UUID of members blocks and not have a breaking penalty.
3b. People might exploit by placing blocks around a player as a trap. This can be countered by other game changes that can also improve the game. Like no longer allowing heavy blocks to be stacked that would have a long break time, like cobblestone, stone etc. Building time would be increased for those like me who like to build large structures and carry like several stacks of stone. But that can be helped with a building profession for a villager. Which I can discuss in another thread.
Anyways this suggestion is just about adding a UUID for the blocks, so that developers have have more possibilities and flexibility for future features.
Please sign in to leave a comment.
-
Official comment
Comment actions
https://feedback.minecraft.net/hc/en-us/search?utf8=%E2%9C%93&query=uuid
Just helping out with related topics here. Also, it's more of a scripting issue (at least from first read), so we'll put it there.
2 Comments