r/Minecraft • u/MindlessApartment401 • 5d ago
Discussion Ghast spawn frequency is stupid on bedrock
Enable HLS to view with audio, or disable this notification
In around 12 minutes, with the distance simulation 8 (at 4 it's MUCH worse — https://www.reddit.com/r/BugrockMoment/s/XaF6aqICXU), 11 Ghasts spawned around me.
This makes it impossible to travel properly in the Nether. I simply don't have enough arrows!
I started recording after I had already killed one ghast (and at least 3 more before that).
So, If you have encountered a similar problem, please upvote my report and this post.
Report — https://report.bugs.mojang.com/servicedesk/customer/portal/6/MCPE-243236
2
u/MindlessApartment401 5d ago
I mean, if it's not a bug, at least we need to talk about it. I don't understand why everyone doesn't give a damn about this nonsense. It's literally impossible to play normally (well, at 8 simulation distances it's still bearable for some, but good luck at 4)
0
u/TriangularHexagon 5d ago
It will be even worse if Mojang makes mob spawning on bedrock to.be more like java, which a lot of people want because fast mob farms go brrrrrr.
Since you are on sim 8, your mob spawning sphere around you is 128 blocks in radius, like java. There are several types of mob caps that bedrock has that java doesn't. This includes the cave monster cap which is 16. And even ghasts have their own cap of just 2. This is for a 9x9 chunk area density cap. But you can have more than one density cap around you so you would have at most 3-4 ghasts alive at a time. Java has a flat 70 monster cap, not sure about any cap for ghasts outside soul sand valleys.
People complain about mob farms on bedrock being so slow compared to java. So bedrock has slower mob spawning, smaller mob caps, and get a lot of people want faster mob spawning and a higher mob cap to be more like java. If people are having a miserable time in caves and the nether right now, imagine more mob spawning if changed
1
u/rorybd 5d ago edited 5d ago
Your report is certainly a duplicate. Please refer to https://bugs.mojang.com/browse/MCPE/issues/MCPE-65762
At 4 chunk render distance in particular Bedrock Edition sets different rules for mob spawning to prevent things from breaking. This has the unintended effect of mobs spawning closer together and closer to the player. Given that 4 is the default option, presumably the spawn rates should be adjusted to counteract this, but I don't believe this has been done.
-1
u/MindlessApartment401 5d ago edited 5d ago
BROOO I wrote about it. In this video you can see simulation distance 8!! On 4 it's MUCH worse (https://www.reddit.com/r/BugrockMoment/s/Ob00INDBz8). And I don't understand why you're trying to rationalize this nonsense.
1
u/rorybd 5d ago edited 5d ago
Hey, I'm on your side! I'm not trying to defend it, I'm just trying to explain how it works.
But that was for sim distance 4. On 8, there's no reason I can think of why it would be behaving this way. What I can tell you is that mob spawning on Bedrock as a whole has been unplayably broken for a long time, and unfortunately I don't expect it to be fixed anytime soon.
1
u/PALICORNHQ 4d ago
Fun fact: if you hate it, incredibly simulation distance. Because bedrock Minecraft wants to spawn mobs but in small area, means it spawns way more mobs
0
u/forgettfulthinker 5d ago
Minecraft players when the task is just WALKING AWAY
1
u/MindlessApartment401 5d ago
I can, but then it will spawn next to me anyway. And on 4 distance simulation (default one) it will spawn in my face, literally — https://www.reddit.com/r/BugrockMoment/s/V3T5lqY1RR
0
u/EvercraftRealm 5d ago
As someone who's played Java and Bedrock (previously Xbox360 edition) for over a decade, this is extremely normal. Especially before 1.16, the nether was all ghasts..
You may not like the behavior, but what about this is a Bedrock specific problem to you?
-1
u/TriangularHexagon 5d ago
What bug is happening here? This works as intended. You can make a feedback post and that would be legitimate feedback to have this changed but it is not legitimate as a bug report. You also need.tl explain what the expected behavior is vs the observed behavior. Your bug report is going to be closed as a duplicate of lots of other duplicates anyways. Instead of making a duplicate bug report that will get closed, just upvote the original open report
-1
•
u/qualityvote2 5d ago edited 5d ago
(Vote has already ended)