mojira.dev

Aiden Kane

Assigned

No issues.

Reported

MC-158766 Duplication glitch (almost) Duplicate MC-158395 Lighting glitch on any slab or stair in popular servers. Invalid MC-158362 Mobs spawning more commonly when loading a chunk than in currently loaded chunks. Invalid

Comments

A popular youtuber made a similar comment. Antvenom's video about problematic mob spawning

You mean block NBT, the stuff that appears on f3 when you look at a block? Like "waterlogged: true"?

I think mobs should spawn upon rendering chunks, but it should be balanced so players don't notice the difference between mobs spawning when they stand still and mobs spawning while they explore the map. I don't think players should have to walk super far before they start seeing mobs. It makes your first few nights really hard when you need food, because you only start exploring after you've established your first base.

I guess you mean servers have plugins. I was right about that.

I would actually like the advancement to be bow-only. Keep this, Mojang.

I agree that this is most likely intentional, but if Mojang wanted to make the pillagers smarter, they could fix that.

I would keep the current pillager, though.

I have noticed this problem as well. Only one of my friends has ever pulled off a LAN world with me.

That should be a feature, because it doesn't make sense for the tool to disappear from inside the shulker box. Mojang should keep this.

I think they should decrease the amount of the iron golems, but not too much. I think a spawn limit of about 1 iron golem every 3 villagers will be a perfect balance. After all, iron golems are a village's only natural defense.

I think they should decrease the amount of the iron golems, but not too much. I think a spawn limit of about 1 iron golem every 3 villagers will be a perfect balance. After all, iron golems are a village's only natural defense.

You really seem to know your stuff.

I have reviewed this comment.

I haven't tried it myself yet, but I think what this person means is the naming system is bugged.

When a screen shot is created, the name is based on the time the screen shot was taken, down to the last second. When a screen shot is taken in the same second, it has the same name, and because the computer can't have two files with the same name, the first one is deleted to make room for the second one.

 You can easily fix this by adding in a system to add a "-1", "-2", "-3" to any screen shots taken in the same second.