Uhh yusufulus, no the amethyst blocks not the buds
@MMK21
The IP address is a Public IP address but the server is not public, though I had no idea it showed the IP in the text document.
Well I'm new at this and it turns out upon reloading the world the chunk does reset, and likely the hotbar thing will become corrupted as well.
After over 150 iterations of chest inception, I can conclusively say that the corrupted data does not occur in a Singleplayer world, but the game does start to get laggy. And the deletion of the chests in my inventory takes longer and longer to delete due to the increased recursive NBT data.
I've added a file of the entire setblock command of how many iterations I did for just the chests; Word says that it's about 129,082 characters long.
I can take a look but to be frank, even if I can do it, I really would like that feature to stay since I use it a lot for storing all of my command block between worlds using the hotbar saving feature. What I would suggest is stopping people from overloading the NBT by putting a restriction on an item with an NBT tag amount of just before the corruption, and this would stop that item from being able to be put into chests and saved on the hotbar.
I want to point out whoever coded the create issue dialog should consider removing the Category element from the index page's "create form dialog" since I just easily edited the Category Element with F12 (Inspect) and then clicked Update and it accepted my code.