Dima Sever
- Cken
- JIRAUSER701612
- Europe/Moscow
- Yes
- No
Many blocks have broken since version 1.18.12+, most likely this is a geometry error since it is indicated in the logs as "contains 10 boxes outside the error bounds of (-0.01, -0.01, -0.01) to (1.01, 1.01, 1.01)" and yes, I use one model that goes beyond the geometry boundaries in order for the block collision to be higher, but I also use geometry that does not go beyond the geometry boundaries, but still the block is not displayed as it should. recently, the blocks functioned in 1.18.2.
Many blocks have broken since version 1.18.12+, most likely this is a geometry error since it is indicated in the logs as
"contains 10 boxes outside the error bounds of (-0.01, -0.01, -0.01) to (1.01, 1.01, 1.01)"
and yes, I use one model that goes beyond the geometry boundaries in order for the block collision to be higher, but I also use geometry that does not go beyond the geometry boundaries, but still the block is not displayed as it should. recently, the blocks functioned in 1.18.2.
Many blocks have broken since version 1.18.12+, most likely this is a geometry error since it is indicated in the logs as
"contains 10 boxes outside the error bounds of (-0.01, -0.01, -0.01) to (1.01, 1.01, 1.01)"
and yes, I use one model that goes beyond the geometry boundaries in order for the block collision to be higher, but I also use geometry that does not go beyond the geometry boundaries, but still the block is not displayed as it should. recently, the blocks functioned in 1.18.2.Many blocks have broken since version 1.18.12+, most likely this is a geometry error since it is indicated in the logs as
- "contains 10 boxes outside the error bounds of (-0.01, -0.01, -0.01) to (1.01, 1.01, 1.01)"
and yes, I use one model that goes beyond the geometry boundaries in order for the block collision to be higher, but I also use geometry that does not go beyond the geometry boundaries, but still the block is not displayed as it should. recently, the blocks functioned in 1.18.2.
Many blocks have broken since version 1.18.12+, most likely this is a geometry error since it is indicated in the logs as
- "contains 10 boxes outside the error bounds of (-0.01, -0.01, -0.01) to (1.01, 1.01, 1.01)"
and yes, I use one model that goes beyond the geometry boundaries in order for the block collision to be higher, but I also use geometry that does not go beyond the geometry boundaries, but still the block is not displayed as it should. recently, the blocks functioned in 1.18.2.
Many blocks have broken since version 1.18.12+, most likely this is a geometry error since it is indicated in the logs as
- "contains 10 boxes outside the error bounds of (-0.01, -0.01, -0.01) to (1.01, 1.01, 1.01)"
and yes, I use one model that goes beyond the geometry boundaries in order for the block collision to be higher, but I also use geometry that does not go beyond the geometry boundaries, but still the block is not displayed as it should. recently, the blocks functioned in 1.18.2.Many blocks have broken since version 1.18.12+, most likely this is a geometry error since it is indicated in the logs as
"contains 10 boxes outside the error bounds of (-0.01, -0.01, -0.01) to (1.01, 1.01, 1.01)"
and yes, I use one model that goes beyond the geometry boundaries in order for the block collision to be higher, but I also use geometry that does not go beyond the geometry boundaries, but still the block is not displayed as it should. recently, the blocks functioned in 1.18.2.
As I understand it, this error appears if the texture id is from block.json is sent to a block that already has a texture id and the geometry replaces it with another one with the same functions.
{ "format_version": "1.18.0", "minecraft:block": { "description": { "identifier": "scm_block:ston_kirpichi_a" }, "components": { "minecraft:creative_category": { "category": "construction" } } } }
As I understand it, this error appears if the texture id is from block.json is sent to a block that already has a texture id and the geometry replaces it with another one with the same functions.
{ "format_version": "1.18.0", "minecraft:block": { "description": { "identifier":"scm_block:ston_kirpichi_a"},"components":{"minecraft:creative_category": {"category": "construction" }} }}As I understand it, this error appears if the texture id is from block.json is sent to a block that already has a texture id and the geometry replaces it with another one with the same functions.
One Block
{ "format_version": "1.18.0", "minecraft:block": { "description": { "identifier": "scm_block:ston_kirpichi_a" }, "components": { "minecraft:creative_category": { "category": "construction" } } } }Two Block
{ "format_version": "1.18.0", "minecraft:block": { "description": { "identifier": "scm_block_zip:ston_kirpichi_a", "properties": { "decor:face": [ 0, 1, 2, 3 ] }, "is_experimental": true }, "components": { "minecraft:creative_category": { "category": "construction" }, "minecraft:material_instances": { "*": { "texture": "ston_kirpichi_a", "render_method": "alpha_test", "ambient_occlusion": false } }, "minecraft:geometry": "geometry.scm_zip_block", "minecraft:pick_collision": { "origin": [-8, 0, 7], "size": [16, 16, 1] }, "minecraft:entity_collision": { "origin": [-8, 0, 7], "size": [16, 16, 1] }, "minecraft:block_light_absorption": 2, "minecraft:on_player_placing": { "event": "decor:face" } }, "permutations": [ { "condition": "query.block_property('decor:face') == 0", "components": { "minecraft:rotation": [ 0, 180, 0 ] } }, { "condition": "query.block_property('decor:face') == 1", "components": { "minecraft:rotation": [ 0, 0, 0 ] } }, { "condition": "query.block_property('decor:face') == 2", "components": { "minecraft:rotation": [ 0, 270, 0 ] } }, { "condition": "query.block_property('decor:face') == 3", "components": { "minecraft:rotation": [ 0, 90, 0 ] } } ], "events": { "decor:face": { "set_block_property": { "decor:face": "query.cardinal_facing_2d-2" } } } } }Block.json
{ "ston_kirpichi_a": { "textures": "ston_kirpichi_a", "sound": "stone" } }
As I understand it, this error appears if the texture id is from block.json is sent to a block that already has a texture id and the geometry replaces it with another one with the same functions.
According to the idea, the first block (scm_block:ston_kirpichi_a) should be a block, the second (scm_block_zip:ston_kirpichi_a) should use geometry
One Block
{ "format_version": "1.18.0", "minecraft:block": { "description": { "identifier": "scm_block:ston_kirpichi_a" }, "components": { "minecraft:creative_category": { "category": "construction" } } } }Two Block
{ "format_version": "1.18.0", "minecraft:block": { "description": { "identifier": "scm_block_zip:ston_kirpichi_a", "properties": { "decor:face": [ 0, 1, 2, 3 ] }, "is_experimental": true }, "components": { "minecraft:creative_category": { "category": "construction" }, "minecraft:material_instances": { "*": { "texture": "ston_kirpichi_a", "render_method": "alpha_test", "ambient_occlusion": false } }, "minecraft:geometry": "geometry.scm_zip_block", "minecraft:pick_collision": { "origin": [-8, 0, 7], "size": [16, 16, 1] }, "minecraft:entity_collision": { "origin": [-8, 0, 7], "size": [16, 16, 1] }, "minecraft:block_light_absorption": 2, "minecraft:on_player_placing": { "event": "decor:face" } }, "permutations": [ { "condition": "query.block_property('decor:face') == 0", "components": { "minecraft:rotation": [ 0, 180, 0 ] } }, { "condition": "query.block_property('decor:face') == 1", "components": { "minecraft:rotation": [ 0, 0, 0 ] } }, { "condition": "query.block_property('decor:face') == 2", "components": { "minecraft:rotation": [ 0, 270, 0 ] } }, { "condition": "query.block_property('decor:face') == 3", "components": { "minecraft:rotation": [ 0, 90, 0 ] } } ], "events": { "decor:face": { "set_block_property": { "decor:face": "query.cardinal_facing_2d-2" } } } } }Block.json
{ "ston_kirpichi_a": { "textures": "ston_kirpichi_a", "sound": "stone" } }
npc compressedfontCompressed Font
Compressed Font NPC
For some reason, a font with ascreen resolutionof1600x900becomes blurry than with a square resolution, where it is clear. I noticed that this error most often appears in addons and may appear in vanilla, but rarely.
Font Russian1.If the screen resolution is 1600x900 and at the same time there is any Resource Pack, then the font of the NPC will be blurred.
2.
1.If the screen resolution is 1600x900 and
at the same time there is any Resource Pack, then the font of the NPC will be blurred.
2.1.If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%.
2.
1.If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%.
2.If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%, but if the screen resolution becomes square, then the font is fixed.
1. Enable Russian in the Minecraft Settings
2. Set the screen resolution to 1600x900
3. Enter the world (The font will break with a 50% probability)
If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%, but if the screen resolution becomes square, then the font is fixed.
1. Enable Russian in the Minecraft Settings
2. Set the screen resolution to 1600x900
3. Enter the world (The font will break with a 50% probability)Video: [#https://youtu.be/59E3XEeVprM]
If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%, but if the screen resolution becomes square, then the font is fixed.
1. Enable Russian in the Minecraft Settings
2. Set the screen resolution to 1600x900
3. Enter the world (The font will break with a 50% probability)If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%, but if the screen resolution becomes square, then the font is fixed.
1. Enable Russian in the Minecraft Settings
2. Set the screen resolution to 1600x900
3. Enter the world (The font will break with a 50% probability)
If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%, but if the screen resolution becomes square, then the font is fixed.
1. Enable Russian in the Minecraft Settings
2. Set the screen resolution to 1600x900
3. Enter the world (The font will break with a 50% probability)If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%, but if the screen resolution becomes square, then the font is fixed.
-The font becomes smooth, but not clear if it has a Russian font or an analog
-The font becomes clear if the screen resolution is higher than 1600x900 or it is square1. Enable Russian in the Minecraft Settings
2. Set the screen resolution to 1600x900
3. Enter the world (The font will break with a 50% probability)
If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%, but if the screen resolution becomes square, then the font is fixed.
-The font becomes smooth, but not clear if it has a Russian font or an analog
-The font becomes clear if the screen resolution is higher than 1600x900 or it is square1. Enable Russian in the Minecraft Settings
2. Set the screen resolution to 1600x900
3. Enter the world (The font will break with a 50% probability)If the screen resolution is 1600x900 and slightly lower, then the font of the NPC will be blurred with a probability of 50-50%, but if the screen resolution becomes square, then the font is fixed.
-The font becomes smooth, but not clear if it has a Russian font or an analog
-The font becomes clear if the screen resolution is higher than 1600x900 or it is square-This bug has been around since version 1.16+
1. Enable Russian in the Minecraft Settings
2. Set the screen resolution to 1600x900
3. Enter the world (The font will break with a 50% probability)
Yes, @a[c=1]
If you create a variable in an animation and then refer to it, a false error about an unknown variable is generated in the log.
Steps to Reproduce:
- Create an Animation Controller that uses a Molang variable.
- Create a second Animation Controller that references the created variable.
- Connect Animation Controllers to Players.
Observed Results:
When connecting to the world, an error appears in the logs (Error: unhandled request for an unknown variable ...). However, it's important to note that this error does not affect the functionality of the code, and it still works correctly.Expected Results:
The error should not appear since the variable exists.Example Code:
animation_controllers.json![]()











Yes, the problem is only in Bedrock Dedicated Server
The issue persists even after updating the animation_controller to the latest version, specifically concerning a false error indicating the non-existence of a variable. However, the problem arises only when variables are accessed before their creation.
For instance, with two animation_controllers: the first one checks a variable for equality to any value, and the second one creates a variable under a certain condition. If the condition in the second animation_controller is met, the variable is created, and the first animation_controller successfully detects its existence, returning true.
Nevertheless, despite this workaround, the error continues to manifest, likely due to peculiarities in the update process.
Thank you, the errors are really gone