I was building in my creative world, and I wanted to clone a large building. Usually, there's a limit to the number of blocks I can clone (32,678 or 2^15) but the number of blocks I cloned ended up being over 40,000, much higher than the block limit. I recorded a video of the bug as well as my settings.
Video link: https://youtu.be/HH27q7pOhYo
The issue might be due to a high memory usage on my computer (I have like 30 tabs open) but I can't see how that would affect Minecraft like this.
Attachments
Comments 10

Note: I'm not complaining about the limit not working for my world (I have large buildings that it would be inconvenient to clone otherwise) but it might be stressful on computer memory not to have a limit
Note: I'm not complaining about the limit not working for my world (I have large buildings that it would be inconvenient to clone otherwise) but it might be stressful on computer memory not to have a limit
It happened again in another world, this time with the number of blocks exceeding 2^18 and with the command taking about a minute to complete. (the tab in the top right corner is a YouTube video I had running in the background)
[media]It happened again in another world, this time with the number of blocks exceeding 2^18 and with the command taking about a minute to complete. (the tab in the top right corner is a YouTube video I had running in the background)
[media]I wanted to address some points regarding my bug report.
It appears that my initial understanding of the cloning limit being 2^15 was incorrect. (I believe this confusion arose because 2^15 is still the fill command limit). I could not find an external source confirming how long 655,360 has been the clone limit, nor could I find any other source for this new limit except Justin's new bug report (MCPE-183836) and my own testing in Minecraft 1.21.
However, my testing also shows that the stated new limit of 655,360 blocks does not always work consistently (see screenshot below). This inconsistency aligns with the title of my bug report, "/clone command Block Limit Not Working," implying that my bug report is still valid and should not be deleted.
Despite this, I am open to moving the discussion to Justin's bug report if the moderation team feels it is appropriate. (Plus, the new bug report is formatted better than mine.)
Best regards,
iSloth2437
Edit: forgot to add the screenshot
[media]
I wanted to address some points regarding my bug report.
It appears that my initial understanding of the cloning limit being 2^15 was incorrect. (I believe this confusion arose because 2^15 is still the fill command limit). I could not find an external source confirming how long 655,360 has been the clone limit, nor could I find any other source for this new limit except Justin's new bug report (MCPE-183836) and my own testing in Minecraft 1.21.
However, my testing also shows that the stated new limit of 655,360 blocks does not always work consistently (see screenshot below). This inconsistency aligns with the title of my bug report, "/clone command Block Limit Not Working," implying that my bug report is still valid and should not be deleted.
Despite this, I am open to moving the discussion to Justin's bug report if the moderation team feels it is appropriate. (Plus, the new bug report is formatted better than mine.)
Best regards,
iSloth2437
Edit: forgot to add the screenshot
[media]