mojira.dev

Timer RP

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

No issues.

Reported

MCPE-227457 The folder "xal" is not generated even says fixed other ticket Unconfirmed MCPE-227456 The game settings are no longer on the external storage (minecraftpe folder it is generated but it remains empty) Unconfirmed MCPE-225990 Some files and folders are no longer generated within external storage and in system application storage Works As Intended MCPE-225986 External storage is no longer activated automatically Plausible MCPE-225542 Pillager spawning at fixed Outpost points is inhibited if there are few spawnable blocks exposed to the sky and many non-spawnable blocks exposed to the sky in the loaded chunks. Invalid MCPE-224151 Snowy Plains trees are not distributed with behavior packs Unconfirmed MCPE-223562 Villagers at the maximum height layer have default skin. Unconfirmed MC-299232 Villagers cannot be spawned by breeding at maximum height while in Bedrock Edition they can. Cannot Reproduce MCPE-223127 The firefly bush disappears when water is spilled and it contains snow in it the block. Community Consensus MCPE-179323 The bogged skeleton variant is inconsistent with its other variants in texture location Fixed MCPE-178910 "min_engine_version" causes vanilla resource pack of entities to not work correctly with entities that only have one file Fixed MCPE-178387 New d-pad touch control does not have option to choose the previous design, making gameplay difficult. Fixed MCPE-178355 The "xal" folder is in the wrong location when using application storage Duplicate MCPE-178354 The folder "xal" is not generated even though the changelog says it should generate within external storage Fixed MCPE-178317 Mangrove roots change color due to foliage Confirmed MCPE-178020 Gravel and sand suspicious block floating, falls after some random gametick which is different from Java Edition Confirmed MCPE-178015 Gravel, dirt and suspicious gravel generation is completely different in bedrock edition Confirmed MC-267689 Hanging signs can't be placed on feet (bedrock parity) Works As Intended MCPE-177552 Converting the world to a template causes the armadillo's experimental functions to not work correctly Won't Fix MCPE-177550 Can no longer convert old worlds to infinite with the new edit world UI Fixed

Comments

[media]

This is how it appears in Android 13-16, the correct thing would be that it also contains its files with the.

[media]

[media]

minecraft generates a folder called minecraftpe on Android 13-16 and it is empty, that folder should contain information

I wanted to provide some detailed context for this ticket, as this is not a new issue, but rather a consolidation of previous reports that have not been fully resolved.
The history of the issue is as follows:

  • MCPE-176675 was closed as 'resolved,' but the fix only applied to Android 11 and 12, leaving the rest of the devices unfixed.

  • MCPE-178354 focused on the XAL file not being generated, was also closed incorrectly, as the issue persisted.

  • MCPE-178355 reported that the XAL file was being moved to the wrong location. It was closed as a duplicate, despite being a separate issue from the lack of generation.

This ticket was created to merge all of these issues and ensure they are addressed comprehensively rather than piecemeal. We would appreciate a full review and a solution that works for all affected devices, not just a select group.
Thank you very much for your attention and support.

Ticket Status Summary:

  • MCPE-176675: This was the main ticket and was marked as resolved by Mojang. However, the fix only applied to Android versions 11 and 12.

  • MCPE-178354: Created as a follow-up, this ticket requested that the XAL file be generated on all Android devices. It was closed as "fixed," although the issue persists.

  • MCPE-178355: This ticket reported that the XAL file was being moved to the app storage. It was closed as a duplicate of a previous ticket, despite being a separate issue.

  • Consolidation: Following the previous issues, you decided to consolidate all your reports into a single ticket to address the storage issue more broadly, affecting both external and app storage.

still happens on 1.21.110.24

[media]

Poco x6 pro

Android 14

This appears to be the same bug as MCPE-178354 that was previously resolved as Fixed.

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

here is the world

[media]

Default generation

[media]

Behavior pack generation error

[media]

Expected generation (example)

[media]

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

duplicate of MCPE-178551

After thinking, I think this is an inconsistency because this has started happening since the implementation of the custom controls due to the red zone. So this is that when the custom controls were kept disabled the classic D-Pad touch controls remained lower and when the custom controls were activated it went up and then since the implementation of the new D-Pad it is no longer necessary to activate the custom.The touch controls they rise higher, which is inconsistent with the old D-Pad.

In conclusion the old and new D-Pad should be consistent in the default position which is lower down.

I've seen comments talking about the MCPE-178399 report stating "Button touching range is smaller than before in new D-Pad & tap to interact mode" that issue is fixed in future version.

It seems like you are experiencing ghost chunks (the report ghost chunks is MCPE-169059) which is probably because the world is old.

when he recently appeared in the nether, it can be seen that on the map the player's point is looking in the same direction as the overworld, which is incorrect, then when the problem goes away, he looks at the location he should be looking at, which is south (That this one looking south is also not entirely correct due to MCPE-177502). Which This is exactly what happens in MCPE-160998.

In conclusion it seems that the reporter is experiencing two issue MCPE-160998 and MCPE-169059

Patrick Play: describe your issue MCPE-160998 and MCPE-169059 from your point of view? You could export your affected world? What is the seed of your affected world? In what version your create the world affected ?

This seems partially fixed based on the current lines of code:

"minecraft:spawns_on_block_filter": [
          { "name": "minecraft:grass" },
          // Badland Terracotta Blocks
          { "name": "minecraft:brown_terracotta" },
          { "name": "minecraft:hardened_clay" },
          { "name": "minecraft:orange_terracotta" },
          { "name": "minecraft:light_gray_terracotta" },
          { "name": "minecraft:red_terracotta" },
          { "name": "minecraft:white_terracotta" },
          { "name": "minecraft:yellow_terracotta" },
          { "name": "minecraft:sand", "states": { "sand_type": "red" } },
          { "name": "minecraft:dirt", "states": { "dirt_type": "coarse" } }
        ],

Curiously, other variants of terracotta are not added, the truth is I don't know if it is intentional because java has a general tag of #minecraft:terracotta