When creating custom blocks that use a custom geometry that contains a model larger than 16x16x16 pixels, aka one Minecraft block, the geometry causes errors and forces the block to appear as the "update" block.
Here is the error message:
[Blocks][error]-geometry.testblock contains 1 boxes outside the error bounds of (-0.01, -0.01, -0.01) to (1.01, 1.01, 1.01)
Additional info by @unknown
This problem did not exist in previous updates if a block was larger than 16x16x16 (unit cube) or had a bone that exceeded the 16x16x16 bounds by as little as 0.001 pixel; the geometry file would continue to load normally, but an error message would appear (which is preferred to this new way of handling larger geometry files)
This new method breaks MANY addons... it would be great if creators had the option (like in previous versions.) and weren't forced into making blocks use separate geos (if larger than 16x16x16).
It should also be noted that several vanilla blocks break the bounds, including (but not limited to) lecterns, spore blossom, walls/fences, and open shulkers boxes.
If intentional, it seems unfair that vanilla blocks are able to break these bounds while modded blocks cannot.
There was also no mention of the change in the changelog, or a reason as to why the change was made.The current warning bounds are also incorrect (reports -0.1,-0.1,-0.1 to 1.1,1.1,1.1, when in practice this extra space is not included; actual bounds are (0,0,0) to 1.1,1.1,1.1. (1,1,1). Prior to this update, the warning was (-0.5,-0.5,-0.5) to (1.5,1.5,1.5), which makes much more sense. (Given the fact that vanilla some blocks break the 1, 1, 1 format by half a block at most)
As a final note, custom block geometries on Java Edition can be as large as 3x3x3 (blocks, not pixels). This was how bedrock was before this update...
Linked issues
is duplicated by 10
MCPE-152256
Data driven blocks' geometries reaching outside 16x16x16 are broken
Resolved
MCPE-152267
Custom blocks that taller than 16x16x16 are not rendering
Resolved
MCPE-152330
Blocks With Custom Models using custom block states do not work
Resolved
MCPE-152605
Addons don't work.
Resolved
MCPE-152643
Addons blocks
Resolved
Attachments
Comments 39
Example of an addon that is broken by this change: https://mcpedl.com/fauna-and-flora/
Direct download link: https://www.mediafire.com/file/8aoupx5ogvkwtj2/Fauna_And_Flora_Addon.mcaddon/file
I'm receiving the same error. I made a statue of a cat that is outside the 16 X 16 X 16 bounds. It worked yesterday and now says the texture needs to be updated and that it is outside the bounds.
I am also having this error since my game updated to 1.18.10 yesterday, models that worked just fine before are now wrecked. I dearly hope this was caused by a programming oversight and is neither intentional nor permanent.
Edit: I have now added example screenshots.
This needs to be fixed ASAP this has crippled my realm, My ATM, Slot Machines, Custom Crafting Tables, My giant custom block map all broken now
[media]
Changes made in 1.20.40 seem to have exacerbated this problem and has reduced the amount of block scaling freedom to an even further degree. Mojang at this point seems to be actively looking for ways to limit mod creators and players from having fun. Oldest son quit the game when the initial changes were made and now my youngest son's world has been damaged by arbitrary block geometry ""fixes"" as well. Absurd how a game that encourages so much freedom can simultaneously deny any of it to people who want to use custom addons.
seriously, what is the point of making addons when your limited on what you can do, just remove the limit and make it so it warns you about lag.
Thank you for your report!
However, this issue is Working as Intended.
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
Full Version History -- Snapshot Version History -- Feature Requests and Suggestions
Quick Links:
📓 Bug Tracker Guidelines -- 💬 Community Support -- 📧 Mojang Support (Technical Issues) -- 📧 Microsoft Support (Account Issues) -- 📓 Project Summary -- ✍️ Feedback and Suggestions -- 📖 Game Wiki
This problem did not exist in previous updates if a block was larger than 16x16x16 (unit cube) or had a bone that exceeded the 16x16x16 bounds by as little as 0.001 pixel; the geometry file would continue to load normally, but an error message would appear (which is preferred to this new way of handling larger geometry files)
This new method breaks MANY addons... it would be great if creators had the option (like in previous versions.) and weren't forced into making blocks use separate geos (if larger than 16x16x16).
It should also be noted that several vanilla blocks break the bounds, including (but not limited to) lecterns, spore blossom, walls/fences, and open shulkers boxes.
If intentional, it seems unfair that vanilla blocks are able to break these bounds while modded blocks cannot.
There was also no mention of the change in the changelog, or a reason as to why the change was made.
The current warning bounds are also incorrect (reports -0.1,-0.1,-0.1 to 1.1,1.1,1.1, when in practice this extra space is not included; actual bounds are (0,0,0) to 1.1,1.1,1.1. (1,1,1). Prior to this update, the warning was (-0.5,-0.5,-0.5) to (1.5,1.5,1.5), which makes much more sense. (Given the fact that vanilla some blocks break the 1, 1, 1 format by half a block at most)
As a final note, custom block geometries on Java Edition can be as large as 3x3x3 (blocks, not pixels). This was how bedrock was before this update...