mojira.dev

Bogdan Barbu

Assigned

No issues.

Reported

MC-268161 Calibrated sculk sensor appears in the wrong location Invalid MC-266377 Hotbar not saved between sessions Duplicate MC-189382 Soul sand, path blocks, and farmland push you Duplicate MC-189380 Rain can render through blocks Duplicate MC-186354 Ruined Portal Generation Bug Duplicate MC-183950 Pressing the Music & Sounds button plays the sound twice Duplicate MC-166067 Walking slowly on slime blocks Invalid MC-166054 Incorrect comparator output from locked chests Duplicate MC-165591 Items do not render in water Duplicate MC-165586 Creeper and lit TNT flashing is different than before Fixed MC-165585 Lit TNT is rendered incorrectly Duplicate MC-165584 Downwards bubble columns render incorrectly Duplicate MC-165170 Placing water with a bucket crashes the game Duplicate MC-164121 Entities in spawners are rendered too dark Fixed MC-164103 Bees don't gather pollen from tall flowers Duplicate MC-161855 Icons used for customizing superflat worlds are not displayed if no world has been opened before Fixed MC-160936 Cannot start game Invalid MC-145374 Farmland moisture Invalid MC-135475 All ocean ruin chests have identical contents Duplicate MC-135474 Glitch when jumping on boats Duplicate

Comments

This needs to be reopened, it was not fixed in 24w11a despite the changelog.

I cannot reproduce this either. No woodland mansion at that location.

PS: The bug report title does not match the description. The title basically means "I went to a dark oak forest and didn't find a woodland mansion there" rather than "woodland mansion generates in the wrong biome".

I agree that this should not be WAI. Even though the wolf collars were updated to better fit the wolf armor, the game should still try to keep its aesthetics consistent.

Fair enough, since the rest of the sculk blocks also appear in the natural blocks group, that explains it.

Why should it be the case that the hotbar slot is preserved? Other things, like orientation, aren't. If keepInventory is disabled then it's extra silly to preserve the slot.

I am pretty sure Jennifer's statement is wrong given everything in this thread and the fact that slicedlime suggested it was not actually fixed in his rc1 changes video.

In that bug report, rain was falling through blocks. This is different, as rain that is behind blocks is rendering through them (look at the size and density of the droplets). The rain isn't actually in the room and isn't even going all the way down. I insist that this bug report has a second look. Please do not mark it as resolved.

It might be that the person directing me here did so by accident because it does not look precisely the same to me.

https://imgur.com/VzRcGQt

Can a mod please unmark MC-189380 as being resolved? It really looks different to me and I've explained it there further.

The issue is not fixed. I am experiencing it in pre5 and the world has been created in pre3. I do not currently have access to the world.

Can a mod please reprove gaspoweredpick? I've seen him being toxic on numerous occasions and he is proving disruptive to this board's efforts with his constant hostile attitude towards reporters. Sorry for having to post it here.

This was not properly fixed. See here:

https://www.youtube.com/watch?v=PGJucW4j7t4

Actually, I just fired up 1.14.4 and it seems to be the case there as well. I am guessing this is expected behavior, in which case this ticket can be closed. Sorry.

I am confused about my report now. According to MC-47941, this is expected behavior. However, it's been marked as an important rendering bug.

The reason the bug behaves the way it does is that mobs can spawn at a radius of 128 blocks from players but if the render distance is less than 10, they can spawn in lazy chunks, where they will not despawn but still contribute to their respective mob caps. It should be less obvious with passive mobs because while they can spawn, they usually generate together with new chunks ignoring their mob cap (which is usually full for this reason).

I think a sensible option is to not even have the possibility to reduce the render distance to 9 or less. It has always been broken and no one has been counting on it for years.

Not entirely sure what the trigger is but a lot of the time I will start the game and the icons will show up without having opened a world. But the bug is definitely there (just happened again a few minutes ago), just not sure how to reproduce it consistently.

Reopen, it's not fixed in 19w39a. It's much worse now. Panning while breaking makes it even more obvious.

I generated about 15 worlds and all of them had floating chests with no torches around it, without a single exception. Still affects 19w37a.

I am experiencing this on Windows 10 as well. This ticket needs to be reopened.

Still an issue in 19w14a. Also, I'm not sure the seed helps because, as far as I've seen in the past, the bonus chest's location is not based on the seed. However, it shouldn't be too hard to replicate because I got this on 5 consecutive new worlds with random seeds. It's not that the chest generates above lakes in particular but it generates in floating in air without any torches around it (probably because there are no valid locations for them—however, they don't appear as entities on the ground either).

Yes, it's still an issue in both those versions. But it's marked as a duplicate, as you can see, so there's not much point in updating this ticket.