mojira.dev

r4isen1920

Assigned

No issues.

Reported

MCPE-153910 "minecraft:food" item component's property "saturation_modifier" is not working as intended Incomplete MCPE-152507 Structure files placed in sub-directories under BP/structures/... doesn't load or parse properly Cannot Reproduce MCPE-152291 NPC Dialogue buttons become unresponsive and do not trigger commands properly Fixed MCPE-120644 Unhandled request for hard-coded variables when using MoLang query.position Incomplete MCPE-110937 Marketplace text weird localization Duplicate MCPE-95633 Scrolling issue with right thumbstick on the Switch Cannot Reproduce MCPE-95627 Freezing issues in Nintendo Switch Duplicate MCPE-71284 Unable to import Behavior Packs-only add-on on Bedrock Realms Duplicate MCPE-63895 "Looping" minecraft:timer behavior component does not actually loop the timer in component groups Incomplete MCPE-56119 In-game "Player Puppet" does not function properly for an unknown reason Incomplete MCPE-56117 Custom player "Animation Controllers" does not work sometimes to run [/function] commands. Fixed MCPE-50978 Entity (Arrow) bug teleportation Cannot Reproduce MCPE-41634 Valid particles do not show using /particle Duplicate

Comments

Seems like the `@initiator` selector when used on NPC no longer works with the pack's `min_engine_version` set to `1.19.50`. It introduced the new execute commands, but somehow had affected `@initiator` selector.

To whom it may concern: this may be presumptuous to say, but have you guys not played the game and have at least messed with it's features - like Redstone mechanics? Of course it's still a bug and it still exists because you guys haven't fixed it! We do not need to spoon-feed everything for such a simple report in particular, but sure be my guest then.

Steps to Reproduce:

  1. Open a world

  2. Place a piston or a sticky piston

  3. Activate it with a lever or Redstone power

Observed Results:

It looks laggy and doesn't mimic the smoothness of the piston block movement similar to that of the Java Edition.

Expected Results:

Piston block movement should be smooth and is pleasing to look at, as gameplay overall more matches to that of the Java Edition.

Affected Versions: Bedrock Edition 1.17.x, 1.18.x, 1.19.x Preview and Beta

I have attached the file. Please take a look into it! Thank you.

Works on 1.19.0.20 Beta / 1.19.0.21 Preview. Hopefully will get it's way through stable versions ASAP. 🙏

I can't confirm. Structures in deeper directories are identified like so:

This couldn't have been more obvious. Though on my defense, that's still a quite confusing one. Having the very first sub-directory deep to be the namespace. I thought you can change namespace by referring it on the filename itself (e.g. `test:steve.mcstructure`). Nevertheless, thanks for pointing that out.

Edit: `:` is not even supported on filenames anyway. So yeah.

Added additional information

I have the same issue here. I'm on Android 11. This never happened before on my end, all of the sudden it just got stuck on the loading screen at 46%. Beta seems to load fine though, but not the current stable release. I hope they fix this ASAP.

My game is also stuck but at 46%. I promise you I have tried the following common/basic troubleshooting steps:

  • Restarted my device

  • Cleared the game's cache/data

  • Even reinstalled the game

And I can assure you that this never happened to me yesterday, or even the day before. Somehow, just all of the sudden, today the game no longer properly loads.

Additionally, the game loads just fine on any other versions – like the Beta for instance. I've tried installing the Beta and it was able to load the game just fine, not the stable version.

 

Platform: Android 11

Game version: 1.17.11 (stable release)

Recently checked the beta's changelog. Seems like it was fixed for the beta, but not for the current stable release.

You can disable "Content Log GUI" under the "Profiles" section from the in-game settings.

The issue seems to happen only when I join/open a world or server/realm, and then force closing the game.

 

I will keep on testing to provide more accurate report whenever possible.

This issue seems to have been fixed by itself. I just restarted the game. If the issue persists, I'll just send an update to this bug report.

 

Thank you!