Flattened Sandstone and Red Sandstone blocks are no longer brighter due to brightness_gamma
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting.
The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json: Changed to 1.0 in 1.21.60.22 preview
However, this assigned brightness_gamma is not used in-game due to Fixed in 1.21.60.22 previewMCPE-167836.
Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.22 preview.
Linked Issues
is duplicated by2
Created Issue:
Flattened Sandstone and Red Sandstone blocks are no longer brighter due to brightness_gamma
When the sandstone and red_sandstone block IDs were flattened in 1.21.20, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:
However, this assigned brightness_gamma is not used in-game due to
MCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, since they do not respect their assigned brightness_gamma of 0.70.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described in
MCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
When the sandstone and red_sandstone block IDs were flattened in 1.21.20, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:
However, this assigned brightness_gamma is not used in-game due to
MCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, since they do not respect their assigned brightness_gamma of 0.70.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described in
MCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
When the sandstone and red_sandstone block IDs were flattened
in 1.21.20, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (seeMCPE-167836), the new IDs lost their special look.The following comparison screenshots were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:
However, this assigned brightness_gamma is not used in-game due to
MCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, since they do not respect their assigned brightness_gamma of 0.70.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described in
MCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
is caused by
relates to
is duplicated by
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:
However, this assigned brightness_gamma is not used in-game due to
MCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, since they do not respect their assigned brightness_gamma of 0.70.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described in
MCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:
However, this assigned brightness_gamma is not used in-game due to
MCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, since they do not respect their assigned brightness_gamma of 0.70.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described in
MCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
is duplicated by
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:
However, this assigned brightness_gamma is not used in-game due to
MCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, since they do not respect their assigned brightness_gamma of 0.70.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described in
MCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:
However, this assigned brightness_gamma is not used in-game due to
MCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, since they do not respect their assigned brightness_gamma of 0.70.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described in
MCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
-The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:
- Changed to 1.0 in 1.21.60.21 preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.21 previewMCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.21 preview.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described inFixed in 1.21.60.21 previewMCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
-The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:
- Changed to 1.0 in 1.21.60.21 preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.21 previewMCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.21 preview.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described inFixed in 1.21.60.21 previewMCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:Changed to 1.0 in 1.21.60.21 preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.21 previewMCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.21 preview.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described inFixed in 1.21.60.21 previewMCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting. This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (see
MCPE-167836), the new IDs lost their special look.The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:Changed to 1.0 in 1.21.60.21 preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.21 previewMCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.21 preview.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described inFixed in 1.21.60.21 previewMCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting.
This brightness is intended to be controlled by thebrightness_gamma property in blocks.json, but since this property is not respected in-game (seeMCPE-167836), the new IDs lost their special look.The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:Changed to 1.0 in 1.21.60.21 preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.21 previewMCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.21 preview.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described inFixed in 1.21.60.21 previewMCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting.
This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (seeMCPE-167836), the new IDs lost their special look.The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:Changed to 1.0 in 1.21.60.21 preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.21 previewMCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.21 preview.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described inFixed in 1.21.60.21 previewMCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting.
This brightness is intended to be controlled by the brightness_gamma property in blocks.json, but since this property is not respected in-game (seeMCPE-167836), the new IDs lost their special look.The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:Changed to 1.0 in 1.21.60.21 preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.21 previewMCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.21 preview.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described inFixed in 1.21.60.21 previewMCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting.
The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:Changed to 1.0 in 1.21.60.21 preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.21 previewMCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.21 preview.
To Fix
Minecraft does not follow the brightness_gamma property from blocks.json, as described inFixed in 1.21.60.21 previewMCPE-167836. This bug was briefly fixed in 1.20.60.22, but silently reverted, likely due to side effects described inMCPE-177356(which are easy to fix). If these side effects were fixed and brightness_gamma was re-enabled, flattened Sandstone and Red Sandstone blocks would keep their original appearance.
When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting.
The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:Changed to 1.0 in 1.21.60.21preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.2MCPE-167836.1previewExpected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.2
1preview.When the sandstone and red_sandstone block IDs were flattened, they lost their extra brightness applied to ambient lighting.
The following comparison screenshots (it's a GIF) were taken with an identical "Brightness" setting on both versions:
The intended brightness_gamma of 0.70 is still assigned in the 1.21.30 blocks.json:Changed to 1.0 in 1.21.60.22 preview
However, this assigned brightness_gamma is not used in-game due toFixed in 1.21.60.22 previewMCPE-167836.Expected Result
Sandstone and Red Sandstone blocks look the same before and after the Flattening.
Observed Result
Flattened Sandstone and Red Sandstone blocks look different than before, as their brightness_gamma values changed in 1.21.20, and have been intentionally set to 1.0 in 1.21.60.22 preview.
Duplicate of MCPE-184909
Thank you for your report!
We're tracking this issue in MCPE-184909, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-184909, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
UPDATE: in 1.21.50.28, the ambient_occlusion_exponent field was mistakenly removed from all vanilla resources. This is reported as MCPE-188216—until it is fixed, this bug report is blocked.
======================
In 1.21.50.25, many block IDs were given "ambient_occlusion_exponent" values (to fix MCPE-184909 and MCPE-177356).
However, a few blocks were given incorrect values, causing their shading to have an unintended look in-game.
Affected Block IDs
| Block ID | Intended Value | Current Value | Notes |
|---|---|---|---|
| cherry_leaves | 1.0 | 0.8 | Added post-Buzzy Bees - should match Java Edition brightness (1.0) |
| chiseled_nether_bricks | 1.0 | 0.8 | Added post-Buzzy Bees - should match Java Edition brightness (1.0) |
| cracked_nether_bricks | 1.0 | 0.8 | Added post-Buzzy Bees - should match Java Edition brightness (1.0) |
| mangrove_leaves | 1.0 | 0.8 | Added post-Buzzy Bees - should match Java Edition brightness (1.0) |
| nether_brick | 1.0 | 0.8 | Previously changed to use 1.0 brightness in 1.16 (Regression) - Applies to all nether bricks |
| nether_brick_double_slab | 1.0 | 0.8 | |
| nether_brick_fence | 1.0 | 0.8 | |
| nether_brick_slab | 1.0 | 0.8 | |
| nether_brick_stairs | 1.0 | 0.8 | |
| nether_brick_wall | 1.0 | 0.8 | |
| pale_oak_leaves | 1.0 | 0.8 | Added post-Buzzy Bees - should match Java Edition brightness (1.0) |
| red_nether_brick | 1.0 | 0.8 | |
| red_nether_brick_double_slab | 1.0 | 0.8 | |
| red_nether_brick_slab | 1.0 | 0.8 | |
| red_nether_brick_stairs | 1.0 | 0.8 | |
| red_nether_brick_wall | 1.0 | 0.8 | |
| sandstone_slab | 0.7 | 1.0 | Contrasts with all other sandstone blocks |
| snow | 1.0 | 0.45 | Contrasts with snowy grass side and powder snow (Regression of |
| snow_layer | 1.0 | 0.45 |
Sandstone Slab
Note: Red Sandstone Slab is already set correctly. Sandstone Double Slab is also set correctly. It is only the sandstone_slab ID which is incorrect.
Snow and Snow Layer
Note: The 0.45 values on snow and snow_layer are incorrect. Powder snow is correct. It is not possible to fix only the snowy grass block side without changing all grass block sides, so the snow must be changed instead.
Nether Bricks (Brighter than 1.16)
Expected Result
"ambient_occlusion_exponent" values are internally consistent. Blocks added post-Buzzy Bees should be consistent with Java Edition, unless they are part of an existing block set.
Observed Result
"ambient_occlusion_exponent" values are not consistent for specific block IDs. Some blocks added post-Buzzy Bees are not consistent with Java Edition.
A Note on Consistency
In the table in this bug report, consistency with other blocks was prioritized over parity with Java Edition. That is why the following blocks were not considered bugs:
- crying_obsidian: 2.0 matches obsidian
- respawn_anchor: 2.0 matches obsidian
- suspicious_sand: 0.55 matches sand
While the nether brick configuration of 0.8 is internally consistent, it also caused a regression back to the pre-1.16 Nether Bricks. This is why Nether Bricks were listed as a bug in the table, while Suspicious Sand was not.
The ambient_occlusion_exponent field in blocks.json has been completely removed from all vanilla resources in 1.21.50.28, and the broken brightness_gamma field has returned for some blocks, despite being removed in 1.21.50.25.
This causes many block sets to be inconsistent with each other, despite the previous changes from 1.21.50.25 fixing this issue. It also caused a regression of MCPE-177356 and MCPE-184909.
This is a regression which blocks MCPE-187777 (inconsistent AO values for certain block sets). The table below takes MCPE-187777 into account and provides consistent values for all block IDs.
List of Affected Files and Block IDs
| blocks.json File | Block IDs | Intended AO Value | Has Outdated brightness_gamma Field |
|---|---|---|---|
| vanilla | glowingobsidian leaves leaves2 nether_brick nether_brick_fence nether_brick_stairs obsidian red_nether_brick red_nether_brick_stairs red_sandstone sand sandstone snow snow_layer |
2.0 0.8 0.8 1.0 1.0 1.0 2.0 1.0 1.0 0.7 0.55 0.7 1.0 1.0 |
✅ ✅ ✅ ✅ ❌ ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ |
| vanilla_1.16 | crying_obsidian nether_brick nether_brick_fence nether_brick_stairs red_nether_brick red_nether_brick_stairs respawn_anchor |
2.0 1.0 1.0 1.0 1.0 1.0 2.0 |
✅ ✅ ❌ ❌ ✅ ✅ ❌ |
| vanilla_1.19.0 | mangrove_leaves | 1.0 | ✅ |
| vanilla_1.20.0 | cherry_leaves suspicious_sand |
1.0 0.55 |
❌ ❌ |
| vanilla_1.20.70 | acacia_leaves birch_leaves dark_oak_leaves jungle_leaves oak_leaves spruce_leaves |
0.8 0.8 0.8 0.8 0.8 0.8 |
✅ ✅ ✅ ✅ ✅ ✅ |
| vanilla_1.21.0 | nether_brick_slab sandstone_slab |
1.0 0.7 |
❌ ❌ |
| vanilla_1.21.10 | cut_sandstone_double_slab cut_sandstone_slab cut_red_sandstone_double_slab cut_red_sandstone_slab nether_brick_double_slab red_nether_brick_double_slab red_nether_brick_slab red_sandstone_double_slab red_sandstone_slab sandstone_double_slab smooth_sandstone_double_slab smooth_sandstone_slab smooth_red_sandstone_double_slab smooth_red_sandstone_slab |
0.7 0.7 0.7 0.7 1.0 1.0 1.0 0.7 0.7 0.7 0.7 0.7 0.7 0.7 |
❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ |
| vanilla_1.21.20 | chiseled_red_sandstone chiseled_sandstone cut_red_sandstone cut_sandstone red_sand red_sandstone sand sandstone smooth_red_sandstone smooth_sandstone |
0.7 0.7 0.7 0.7 0.55 0.7 0.55 0.7 0.7 0.7 |
✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ |
| vanilla_1.21.30 | nether_brick_wall red_nether_brick_wall red_sandstone_wall sandstone_wall |
1.0 1.0 0.7 0.7 |
❌ ❌ ❌ ❌ |
| vanilla_1.21.50 | pale_oak_leaves | 1.0 | ❌ |
Expected Result
ambient_occlusion_exponent remains present in all vanilla resources on the same blocks as 1.21.50.25. brightness_gamma is not present.
Observed Result
ambient_occlusion_exponent field has vanished from all the vanilla resources, and the broken brightness_gamma field has returned.
Also, the hard-coded brightness_gamma values are back, and ambient_occlusion_exponent in a resource pack cannot overwrite them (MCPE-188221).
It is worth noting that this bug affects three block IDs:
- sand
- red_sand
- suspicious_sand
Since MCPE-184909 was resolved Works As Intended, this bug is now more important, because sand and sandstone ambient occlusion are currently mismatched. This causes the sides of desert caves and mountains to look janky.











Here to just mention how sandstone on java isn't brighter, so it could be considered resolved for parity.
This being an intentional change is possible, but not likely, as the blocks.json from 1.21.30.21 still includes the brightness_gamma: 0.70 property. If the property was 1.0, I would believe this was intentional.
Mojang went back and manually replaced the broken brightness_gamma field with ambient_occlusion_exponent throughout all the default resources. This includes all varieties of sandstone. brightness_gamma is officially deprecated!
And so, this bug is fixed in 1.21.50.25.
This bug has returned in the 1.21.60.22 preview, as ambient_occlusion_exponent is now set to 1.0 for all sandstone variants.
This indicates that the shading change is intentional, so this report could be marked "Works As Intended" by Mojang. This change to darker shading matches Java, making this a successful parity change.
Since sandstone and red sandstone are now darker, the bug
MCPE-48366is no longer reproducible.