Ori1666
Assigned
Reported
Comments
Circling back to this, I believe this can be closed. I believe shooting a projectile near a sculk sensor, from any distance, is designed to alert nearby shriekers. Apologies as I was unaware of this behavior being by design when this case was opened. Sincere thanks for the help and follow up.
PS - I was testing with a bow with the Flame enchantment, so firing once would trigger all 4 warnings because the arrow was still lit. Being as it was fired by the player, and still lit, it would cause all 4 warnings to be triggered.
I am also seeing this behavior after the latest Bedrock update was released. I can't shoot arrows, breaking blocks is incredibly slow, mobs don't die in my mob farm, other mobs/villagers don't move or move very slowly, and other game activity just lags to a point where the game is unplayable. However, I'm playing on the PS4 version of Bedrock and not BDS online.
I know this is a confirmed issue, but for player's seeing mobs in Ancient Cities not in/near the lush or dripstone caves biomes remember mobs can come from above the cities in any biome. I see this when they come down waterfalls or spawn on ledges on the walls and then fall. Torches and boxing off the water can help in those cases. I kind of like the challenge of mobs in ACs, should be a game setting toggle players can choose in Options. Just a heads up for players who weren't aware.
This bug affects the Bedrock version of the game, this specific bug report (MCPE-154121) tracks issue reports for Playstation, but this issue affects multiple platforms. See MCPE-55010 - confirmed on multiple platforms. Same issue. MCPE-55010
I realize this may not be a priority given how specific this is, but some more info anyway. You can repro this by placing a sculk sensor and then a shrieker within range. If you shoot the sensor with a Bow with the Flame 1 enchantment, from any distance, it will trigger the shrieker 4 times. I realize a shrieker placed like this can't spawn a Warden (can_summon = false), but the rest of the mechanics should be the same. I suspect the sensor is detecting persistent noise/vibration generated from the player.
My expectation would be this is a bug or clarification of, or an amendment to, game mechanics is needed. Thanks again.
Added to report notes as well, here are the coords:
Seed: -4664117889184820337
Projectile Position (Player Area): -9806,-32,-2919
Sculk Location (Target Area): -9825,-55,-2929
Thank you
It is believed to be a bug, which is why it was reported. I can't find any documentation (change logs, wiki, etc.) that states this is by design, so I was referring to undocumented behavior. I will share the seed and test location.
To raise awareness on this, my understanding was this was a Bedrock code based issue affecting multiple platforms not just consoles. Refer to MCPE-55010 for details as I believe there are reports on Windows as well. The commonality among reports is that the impacted World size has become "too large", usually over 500MB. This affected my world starting when it became 900GB in size. Given how long this issue has been open with no attention or movement, I'm not sure this can or will be fixed unfortunately.
Is there a method to delete 1 of the level DB files for Playstation 4 world? Export world to USB and modify on computer or something similar? Been locked out for almost 2 months and really want to play 1.19
Issue remains in 1.19 release...
@Meg / All - My understanding was there was a master bug report being tracked (MCPE-55010) for this as it a Bedrock code base bug affecting all Bedrock platforms. Please vote/watch this incident as, so many are open, I believe it isn't accurately reflecting how many users are truly affected:
I believe this issue is a duplicate and should be linked to the master bug tracker ID MCPE-55010. There are a lot of linked/duplicate reports on this issue which has watered down the true scope of exactly how many players are impacted by this. Thank you.
I have been experiencing this exact issue (Bedrock v 1.18.31 on PS4) but was able to work around it until yesterday. My world reached 1 GB in size and now I can't play anymore - "There was a problem loading this world". I've tried everything - downloaded previous saves from cloud and USB, reinstalled Minecraft, etc. etc. I can't believe years of work is just...gone? I'm not starting over, if this is truly lost then how do we know this won't happen again? I was really championing and looking forward to the 1.19 update as well. Whether it is an issue of complexity or priority, this has been unresolved for so long I'm losing faith this can or will be fixed? Hundreds of hours...just....catastrophic disappointment.
I am experiencing this issue on Bedrock 1.20.60 and the latest 1.20.62 versions on ps5 (ps4 edition). For me, this issue started on 1.20.40 intermittently and became completely unplayable starting on 1.20.51. No worlds will load now and all are over 1GB in size. If helpful or relevant, I've encountered very similar issues during the last 2 major game update cycles between major versions (1.18>1.19 and 1.19>1.20) and each of the prior 2 cycles it didn't work until the last Bedrock update prior to the next major release. However, this issue has no workarounds that I've found where uninstalling/reinstalling and/or Realms would previously work on some occasions.