mojira.dev

AgentMindStorm2

Assigned

No issues.

Reported

View all
MCPE-234722 /reload all doesn't reload resource packs in "resource_packs" folder, but exiting and re-entering a world manually does Unconfirmed MCPE-226626 Resource packs which previously defined "warped_forest" music no longer work in 1.21.110.24 Unconfirmed MCPE-226568 Mangrove swamp client biome file is missing water identifier for Vibrant Visuals Confirmed MCPE-226247 Smooth lighting on partial blocks is broken after 1.21.100 Duplicate MCPE-223225 Manifest labels in resource packs no longer load correctly in the subpack selector screen Works As Intended MCPE-223048 Server authoritative movement: Creative mode flight sometimes desyncronizes when switching quickly in singleplayer Unconfirmed MCPE-223046 Pauses between background songs are about 3 times longer than intended in-game Plausible MCPE-222490 query.is_carrying_block cannot be used on the off-hand, unlike other held item queries Plausible MCPE-218551 Cobwebs in corners sometimes have incorrect shading/ambient occlusion Confirmed MC-297537 Extra "entity.wolf_whine.whine" sound event exists in sounds.json Fixed MC-296624 Old Brown Mooshroom texture is missing from Programmer Art Fixed MCPE-191247 New cow and mooshroom models have incorrect front leg pivot points Unconfirmed MCPE-191246 New cow models are misaligned compared to old cow models and mooshroom model Unconfirmed MCPE-191245 Main menu background and splash text movement change does not match the purpose of Screen Animations setting Works As Intended MCPE-191242 /reload all command crashes the game with 100% consistency Fixed MCPE-190812 Mooshroom back mushrooms float above the model Duplicate MCPE-190811 Mooshroom back mushrooms are no longer double-sided Confirmed MCPE-190810 Outdated Enchanting Table name still used in Achievements Unconfirmed MCPE-190809 Sheep texture does not match Java Edition Works As Intended MCPE-190808 New spawn egg texture names and locations do not match Java Edition Won't Fix

Comments

[media]

I am unable to reproduce this issue in 26.0.27 using Timeless Adventures from the Marketplace as my test world.

This bug is still an issue in the 26.0.27 preview.

It’s worth noting that the packs sometimes apply after closing and reopening the game, but it does not always work as expected.

You’re hearing idle and step sounds, which work as intended because they aren’t played through animations. This issue affects stand up, sit down, and sniffing sounds, which are played as sound_effects in an animation.

This also affects the Camel Husk as of 1.21.130.

This is most likely related to MC-304769

Can confirm. The issue is most visible at the transition point from “spear held straight” to “spear held sideways” in first person. There is just no rotation transition at all in RC1, while the rotation transition works perfectly in pre2.

I can also confirm in 1.21.120.

Can confirm in 1.21.130.25.

Counterpoint: This is the intended way the cursor works on Java Edition, so this could be considered a parity fix. The previous report may have been marked “Won’t Fix” due to a limitation of the UWP system, but switching to GDK has fixed the issue.

This should be marked “Works As Intended”, as it fixes a longstanding parity issue.

[media]
[media]
[media]

In 1.21.110.24, Mojang added the biome_music definition to all Nether biomes and the normal roofed forest. This has not resolved the issue because all the following biome groups are still missing the component:

  • Swampland (all)

  • Peaks (all)

  • Meadow

  • Grove

  • Snowy Slopes

  • Cherry Grove

  • Birch Forest (all)

  • Roofed Forest Mutated

  • Forest

  • Flower Forest

  • Mega Taiga (all)

  • Redwood Taiga (all)

  • Mesa (all)

  • Desert (all)

  • Lush Caves

  • Dripstone Caves

  • Deep Dark

For this issue to be resolved, all these biomes need the correct biome_music configuration. I have tested and confirmed personally that adding the component with the right definition to these biome files fixes the music issue.

[media]
[media]
[media]

I also encountered this issue and did some investigating to figure out why it’s happening. Here is a more thorough description of the issue:

Title: Smooth lighting on partial blocks is broken after 1.21.100

Description:

Smooth lighting has completely broken for partial blocks as of 1.21.100. This was not an issue in 1.21.94. This change from the 1.21.100 changelog has most likely caused the issue:

  • Fixed faces of non-full blocks (eg. Cakes or Trapdoors) having an unnatural ambient occlusion applied to them in some neighboring blocks configurations

This has actually made lighting significantly worse for all non-full blocks. It is most noticeable on snow layers and village paths, since they are light in color and often surrounded by full blocks.

List of confirmed affected blocks:

  • All slabs

  • Snow layer

  • Dirt Path

To Reproduce

  1. In the main menu, navigate to Settings → Video → Graphics Mode, and select Fancy.

  2. Enable Smooth Lighting.

  3. Enter a world in Creative Mode with Cheats enabled.

  4. Type the following command:

    1. /locate biome minecraft:snowy_slopes
      /locate biome minecraft:snowy_slopes

  5. Teleport to the Snowy Slopes biome.

  6. Observe a sloping hill with snow layers.

  7. Observe the unnatural lighting on the snow layers.

Expected Result

Lighting is smooth on partial blocks when next to full blocks.

Observed Result

Lighting on partial blocks looks unnatural next to full blocks, with a harsh dividing line at the edge of the partial block.

[media]
[media]
[media]
[media]

Can confirm in 1.21.93.

The environmental fog from Java Edition is nothing like Vibrant Visuals' volumetric fog. The Pale Garden fog, for example, is handled differently, being extremely thick on Bedrock while basically unnoticeable on Java.

Vibrant Visuals is not a good reason for Fancy Graphics parity breaks in general. Do the new cloud changes from Java Edition intend to match Vibrant Visuals? Not really; in fact, Bedrock clouds are still as limited as old Java clouds in Fancy. I don’t see why the fog would be different.

Can confirm.

This may be caused by https://report.bugs.mojang.com/servicedesk/customer/portal/6/MCPE-219051

This is not a bug. Sound events choose a random song from their list, and there is nothing in place to prevent the same song from being randomly chosen multiple times.

Humans are bad at perceiving true randomness: https://www.howtogeek.com/847793/why-spotify-shuffle-is-not-truly-random/

This is more of a feature suggestion than a bug report.

Can confirm.

Load more comments