MCPE-167836Cannot change brightness_gamma setting in blocks.json
"sandstone" : { "brightness_gamma" : 0.70, "isotropic" : { "down" : true, "up" : true },
When changing properties in blocks.json for texture packs, the brightness_gamma setting doesn't actually change at all. Every other property can be changed except this one. There is no visual change in-game when this setting is updated and applied.
This has been a noted issue from 2+ years ago here
How to replicate:
- Change textures on a block that uses gamma_brightness by default (example sandstone) to be the same as a block that does not use gamma_brightness by default (example stone)
- Change gamma_brightness setting in blocks.json on sandstone
- See there is no change
Files attached:
Sample file that changes the textures of stone/sandstone to share a texture, and also the modified blocks.json file that should change gamma_brightness if it was working correctly.
Linked Issues
Created Issue:
Cannot change brightness_gamma setting in blocks.json
"sandstone" : { "brightness_gamma" : 0.70, "isotropic" : { "down" : true, "up" : true },When changing properties in blocks.json for texture packs, the brightness_gamma setting doesn't actually change at all. Every other property can be changed except this one. There is no visual change in-game when this setting is updated and applied.
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 11
- 1.19.63
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
"sandstone" : { "brightness_gamma" : 0.70, "isotropic" : { "down" : true, "up" : true },When changing properties in blocks.json for texture packs, the brightness_gamma setting doesn't actually change at all. Every other property can be changed except this one. There is no visual change in-game when this setting is updated and applied.
This has been a noted issue from 2+ years ago here[
How to replicate:
- Change textures on a block that uses gamma_brightness by default (example sandstone) to be the same as a block that does not use gamma_brightness by default (example stone)
- Change gamma_brightness setting in blocks.json on sandstone
- See there is no change
Files attached:
Sample file that changes the textures of stone/sandstone to share a texture, and also the modified blocks.json file that should change gamma_brightness if it was working correctly.
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
"sandstone" : { "brightness_gamma" : 0.70, "isotropic" : { "down" : true, "up" : true },When changing properties in blocks.json for texture packs, the brightness_gamma setting doesn't actually change at all. Every other property can be changed except this one. There is no visual change in-game when this setting is updated and applied.
This has been a noted issue from 2+ years ago here
[
How to replicate:
- Change textures on a block that uses gamma_brightness by default (example sandstone) to be the same as a block that does not use gamma_brightness by default (example stone)
- Change gamma_brightness setting in blocks.json on sandstone
- See there is no change
Files attached:
Sample file that changes the textures of stone/sandstone to share a texture, and also the modified blocks.json file that should change gamma_brightness if it was working correctly.
![[MCQA] Bartłomiej Słodkowski](../../../data/avatars/users/18941.svg){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
![[Mod] LateLag](../../../data/avatars/users/92884.png){kind=small}
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
is duplicated by
blocks
shouldn't a new report be made about the return of the issue?
![[Mod] EVGENSYPERPRO](../../../data/avatars/users/92853.png){kind=small}
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
MCPE-167836 was fixed in 1.20.60.22 Preview, which means brightness_gamma values can darken the block correctly.
However it can not affect the glowing blocks.
For example, we apply a resource pack, which includes the blocks.json and we edit the sand and glowstone in it, set a same brightness_gamma value.
Like this, set the value for 20.
{
"format_version": [
1,
1,
0
],
"glowstone": {
"brightness_gamma": 20
},
"sand": {
"brightness_gamma": 20
}
}
Activate the pack and load a world, place a sand and a glowstone.
Then we can see the sand side is dark while the glowstone is still light like before, see the attachment screenshot.
In vanilla bedrock resource pack, crying obsidian have a brightness_gamma value, which is 2.00 (default is 1). Because of the bug, it can not affect this block in game.
Although these oddities were always present, the fix for MCPE-167836 in 1.20.60.22 allows all of the brightness_gamma values in blocks.json to be changed, having a direct effect on the appearance of blocks in-game. This has both exposed new issues, and made older ones easier to fix. The fix for MCPE-167836 was correct and should not be reverted.
List of affected blocks:
- Sand, Red Sand -
Brighter, inconsistent with Suspicious Sand(Fixed in 1.21.50.25) - Sandstone, Red Sandstone and all of their variants - Updated: Single Sandstone Slab don't have the component "ambient_occlusion_exponent" : 0.70 set like the rest of the block set. Red Sandstone blocks are fully fixed in latest preview (Almost fixed in 1.21.50.25)
- Snow Block and Snow Layer - Brighter, regression of
MCPE-57022 - Nether Brick -
Slightly brighter, inconsistent with all of its variants(fixed in 1.21.50.25) - Red Nether Brick and Red Nether Brick Stairs -
Inconsistent with the slab and wall versions(fixed in 1.21.50.25) - Oak, Birch, Spruce, Jungle, Acacia, Dark Oak and Mangrove Leaves - Slightly brighter, probably intentional
- Obsidian - Slightly darker, probably intentional
- Crying Obsidian and Glowing Obsidian - No effect in-game due to
MCPE-177349
A simple fix for these would be to set these blocks' brightness_gamma component in blocks.json to the default value, which is 1. (Creator: You can also just delete the "ambient_occlusion_exponent" component from the block)
The fix for MCPE-167836 has enabled a previously unused component that's present in the default blocks.json file, making this issue reappear in Preview 1.20.60.22.
In 1.20.60.22 preview/beta, MCPE-167836 was fixed, allowing resource packs to modify the "brightness_gamma" property of any block. The issue reappeared in the following 1.20.60.23 preview.
As it was not listed in the changelog, this regression is likely unintentional. When MCPE-167836 is fixed once again, MCPE-177356 should also be fixed to maintain snow and nether brick visual cohesion.
These issues are no longer visible in-game because the fix for MCPE-167836 was incorrectly reverted, but they remain an issue today. Fortunately, it is a single line in the blocks.json file to fix each block.
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.
Pale Oak Leaves are lighter on Bedrock Edition than Java Edition due to a different, hard-coded brightness_gamma value. Having a brighter canopy detracts from the spookiness of the Pale Garden.
Comparison GIF:
This bug relates to MCPE-167836, which prevents blocks.json from overriding these hard-coded brightness_gamma values.
The Pale Oak Leaf brightness is most obvious when you replace the textures of Pale Oak Leaves and a normal block like Dirt with a plain, white texture (see the attached pale_oak_leaf_brightness_gamma sample pack).
There is more shading applied to the Dirt than the Pale Oak Leaves, despite using identical textures.
North-South
East-West
Bottom
Expected Result
Pale Oak Leaves are equally bright on Bedrock and Java Edition.
Observed Result
Pale Oak Leaves are brighter on Bedrock than Java, detracting from the gloomy atmosphere of the Pale Garden.
I can confirm this is still an issue in 1.21.50.22. However, at the moment, this bug is blocked by MCPE-167836.
Relates to MCPE-190244 and MCPE-190242.
In 1.21.50.24 preview, the field "ambient_occlusion_exponent" was introduced to blocks.json. This field is a replacement for the broken "brightness_gamma" field (see MCPE-167836).
However, this new field does not work properly with light sources. This means the "ambient_occlusion_exponent" values configured for crying obsidian and the respawn anchor in vanilla are not displayed in-game.
As an example, I have created a sample resource pack (attached below) which sets the following "ambient_occlusion_exponent" values:
- dirt: 1.0 (default)
- coarse_dirt: 100.0 (extremely dark)
- dirt_with_roots: 0.0 (no shading at all)
- sea_lantern: 1.0 (default)
- glowstone: 100.0 (extemely dark)
- shroomlight: 0.0 (no shading at all)
While the field is functional on dirt, it does not work on light sources:
Ambient Occlusion Exponent Resource Pack:
Vanilla:
This is definitely unintentional, as Crying Obsidian and Respawn Anchor have "ambient_occlusion_exponent" values of 2.0 configured. These do not apply in-game because of this bug.
Expected Result
Setting an "ambient_occlusion_exponent" value above 0 on any block, including light sources, in blocks.json will darken the block's face dimming and increase the amount of ambient occlusion.
Observed Result
Setting an "ambient_occlusion_exponent" value above 0 on light sources has no effect.
In 1.21.50.24 preview, the field "ambient_occlusion_exponent" was introduced to blocks.json. This field was a replacement for the broken "brightness_gamma" field (see MCPE-167836).
However, this field is also broken as of 1.21.50.28. The field briefly worked in 1.21.50.25-1.20.50.26. This regression is likely related to MCPE-188216.
To Reproduce
- Import the sample pack: ambient_occlusion_exponent_tester.mcpack
which sets the following "ambient_occlusion_exponent" values:
- dirt: 1.0 (default)
- coarse_dirt: 100.0 (extremely dark)
- dirt_with_roots: 0.0 (no shading at all)
- sea_lantern: 1.0 (default)
- glowstone: 100.0 (extremely dark)
- shroomlight: 0.0 (no shading at all)
- Load a world with the sample pack applied.
- Place down dirt, coarse dirt, and rooted dirt.
- Observe the default 1.0 shading on all three blocks.
- Place down sea lantern, glowstone, and shroomlight.
- Observe the default 0.0 shading on all three blocks.
Ambient Occlusion Exponent Resource Pack (No Effect):
Vanilla:
Expected Result
Setting an "ambient_occlusion_exponent" value on any block in blocks.json will configure the block's face dimming and ambient occlusion.
Observed Result
Setting an "ambient_occlusion_exponent" value in blocks.json has no effect on any block.
Other
This bug blocks MCPE-187536 and MCPE-187777 as they cannot be reproduced without a functional field.
Please provide a complete sample pack that can be used to reproduce the issue.
Effects 1.20.12
The issue has returned in 1.20.60.23 Preview.
Still effects 1.20.60.24 Preview
Interestingly, the fix for this bug was listed in the full 1.20.60 release changelog, despite not making it to the full update.
As of 1.21.50.25, brightness_gamma has been officially removed in favor of ambient_occlusion_exponent, which is now present throughout the default resources and makes all blocks the intended brightness.
This report can now be resolved as Fixed in 1.21.50.25.