Ninja Dankinate
- ninjadankinate
- JIRAUSER636145
- America/Los_Angeles
- Yes
- No
Deleted Comment:
MCPE-104826is open. It has an ADO number. If shulkers are the feature, then they were added well before 1.14/1.15. If shulker reproduction itself is the feature, then it is not present in both Java and Bedrock. Per the rules, It should not be an open ticket, and yet it has an ADO, which implies dev approval.Why was this ticket closed and marked as invalid, but shulker reproduction, which violates the same rules, allowed to stay open?
Since admins and devs have endorsed opening tickets like this by leaving
MCPE-104826open and giving it an ADO number, please reopen this ticket, or would you prefer I open a new one?
This happened to me today in my realm. I'm at ~y17, with many layers of rock and an ocean above my villager trading hall.
This happened to a villager potato farm I had; all villagers just disappeared when I left the area and came back. Luckily, realm was reset, so I was able to get them back, but it's not something I can ask my realm owner for easily if it happens again.
Our realm is having regular crashes with the aforementioned symptoms as well, i.e. players unable to interact with anything for a short time, mobs freezing, and then a sudden crash kicking all players from our realm.
It's made our realm nigh unplayable, save for those with a high tolerance for sudden rollbacks.
Just a reminder/report that trident killers aren't the only affected entity.
I made an ender pearl metastasis chamber (at about y=65). I did a quick fly away and back. during that time, the ender pearl phased through the ground down to y = 14. I know this because as soon as I was close enough to reload the area on my way back, the ender pearl began interacting with blocks again, and I was teleported from way up in the sky down into solid blocks at y = 14.
Unlike tridents, there is no simple "stick it in a chest when done" for this case.
FWIW, I'm having the opposite problem at my drowned conversion farm – zombie spawners just randomly seem to stop producing zombies, even though the wiki says that spawners should ignore mob caps, and even after the drowned are all cleared via trident killer, the spawners still won't produce zombies. If I leave the area and comback, the spawner works again. Maybe I should file a ticket for this...
Reply from [Mod] GoldenHelmet: that issue is tracked at
MCPE-142285.This is happening in my realm with double zombie spawners. Spawners are located at border of 1.16 and 1.17 generated chunks.
Seed = -1337710146
Coords: 1459, 22 ,1835 and 1448, 17, 1834 (Y coords are approximate)
I afk here within 16 blocks of both spawners, and eventually, all zombies stop generating from both spawners.
This happened to our realm as well, but even after we turned off the "require resource packs to join" option, the issue persists. We still cannot locally load our own resource packs when playing in our realm.
@Roman Ferrier, I've done that multiple times, and it still won't work for us.
I'd argue that comparative performance metrics between linux and windows in the latest version (similar to what has already been attached to this ticket for previous versions) should be submitted before deciding to close this ticket. It should not be closed just because a few subjective comments were left that things seemed to have improved.
After all, we wouldn't open a ticket if someone only claimed "performance sucks on Linux". The same should go for closing.
Even with the workaround, hoglins will path back onto my rail track from the trapdoors, and only inconsistently fall into my pit. Pit is 3x3 with trap doors along one side (1x3). Trap doors are lined perpendicular to the track, and all three are triggered with the observer string adjacent to the track.
All other mobs fall into the pit as expected.
Thanks @Auldrick for the update! The new workaround fixed my issue, and consistently drops all ground-based nether mobs in my 3x3 pit!
At the risk of having this comment removed, I'd like to emphasize that this ticket really does represent a bug, or rather, new features that further create disparity between the two versions ought to be classified as bugs – especially features with such huge impact to in-game quality of life. Obviously, this ticket is open, so Jira admins likely agree with this sentiment, but it'd be nice to know officially if that sentiment is shared with admins and devs. Should we be filing more tickets like this?
Reply from [Mod] GoldenHelmet:
There is no need for emphasis. This ticket is not only open, it is confirmed and has an ADO number, which means that Mojang is tracking it internally. It also has a "vanillla-parity" label, which means it is considered a valid parity issue for the bug tracker based on the current parity issue policy, which is posted here: https://feedback.minecraft.net/hc/en-us/community/posts/360062341891--May-2020-Bug-reports-about-vanilla-parity-issues-on-the-bug-tracker-
You can find all of this information in the Bug Tracker Guidelines .
Thanks for the links!
I think where I was confused, and where I'm still asking for clarity, is that I'm viewing shulker reproduction as the feature, as opposed to shulkers themselves. That is, shulker reproduction as a feature does not exist in both versions, and fails to meet the following requirement.
I guess it's safe to say that shulkers in and of themselves are the feature here, and the bug is the difference in behavior across versions, right?
Reply from [Mod] GoldenHelmet:
Should the fix/version be changed back to "None"?
I should also add that I've completely uninstalled and reinstalled (Bedrock Win10), and still I cannot use my locally enabled resource packs in the realm I'm a member of.
You could be right, but that still leaves one things unaccounted for – we have "require players to accept resource packs" turned off, but players are being prompted as if it were still on when joining the realm. Strange things are afoot.
Update on my end. Removing and reapplying existing packs, and toggling the "require players to accept resource packs" on and off multiple times seems to have fixed the issue with our realm. YMMV
Created a Ghast blaster farm, and my ghast got loose from the cart on relog. It didn't happen every time though. It stayed in the cart more often than it got loose from it, FWIW.
@Sierra, it has an ADO number, and is marked as confirmed, so it is definitely a bug, but maybe just one that isn't as noticeable on beefier machines.
MCPE-120605(which is closed due to being tracked here) mentions lag induced by entities being redirected by slime blocks.I'm seeing the slime block redirection aspect of this bug with a small (three ghasts) ghast blaster on my M1 iPad Pro.
The farm feeding my ghast blaster is a massive redstone contraption, but without the ghasts, there's essentially no lag. In fact, with two ghasts, the lag is barely noticeable, but as soon as I add a third or fourth ghast, the lag is horrendous.
Edit: Since I'm on iOS, the lag may be exacerbated by MCPE-66740, but overall, the lag is almost certainly due to the issue described in this ticket.
In 1.18.12, if the bees are in a 1x1 column (height doesn't matter), the bees sometimes get stuck on each other, and are unable to path back to the hive.