mojira.dev

Gamepro5

Assigned

No issues.

Reported

MC-219290 Calcite is too quiet compared to other blocks Fixed MC-218982 Bobbing camera velocity interpolation when colliding with terrain Duplicate MC-218976 Inventory craft options lack sprite Duplicate MC-218698 Infested deepslate makes the old "stone" sounds Fixed MC-215966 Large sun-occluding structures cause massive lag spikes when chunks are loaded, but only on servers. Cannot Reproduce MC-186380 Old Computer Suffers Even Lower FPS Now Duplicate MC-171923 Beacons don't tolerate inaccessible blocks encased by bedrock Confirmed MC-170668 Weighted pressure plates still use wooden step sounds despite them being made of gold/iron. Duplicate MC-168231 Bees cannot boost crop growth if there is no bee hive or nest nearby Invalid MC-167630 Stackoverflow Error for default Minecraft Servers Invalid MC-157867 Game Stutters when trying to break a block with a sword or trident while walking or sprinting Duplicate MC-157741 Shields Visual Glitch Duplicate MC-146180 Water doesn't flow after using a bucket Duplicate MC-146151 Structures don't seem to generate in certain chunks Duplicate MC-145982 Multishot doesn't deal more damage when more than one arrow hit a mob at once Works As Intended MC-145600 Chests had repeating loot in specific areas Duplicate MC-145599 Lead completely glitched out when strapping a mob to a pole Duplicate MC-133631 Doors cannot be waterlogged and have ugly water texture in front Duplicate MC-133626 Sponges remove water from waterlogged blocks, but the water logged blocks don't refill. Invalid MC-133548 Game ignores lang.json files in resource packs unless the very last definition is present Cannot Reproduce

Comments

Confirmed in 21w11a.

I know this is a bug, but I really hope it stays. Having less brightness contrast when you open the inventory makes it so you don't get flashbanged by the GUI when it opens.

I think this bug should be re-opened. I'm on a multiplayer server and it actually happens even when the wolf does have direct access to sunlight, sometimes. I'm in 1.16.5.

 

[media][media]

 

I don't have this issue at all. Are you using any resource packs?

Can confirm.

When did you buy Minecraft? Because you may need to sign in with your Microsoft account if it was created after 2020. Perhaps you are signed in with another account of a relative? Including pictures would be helpful! 🙂

As of 1.17 snapshot 21w10a and the introduction of a better rendering engine, this issue appears to be fixed.

An inconsistent workaround to destroy the netherrack is to summon the wither right next to it, but that is also very RNG based. Annoying to deal with on any cheatless run of the game.

Servers like this use 1.8.9. They allow newer versions to play on the server too, because it is heavily modded with plugins, but those plugins aren't perfect, resulting in stuff like this. For the best experience, use 1.8.9 🙂

No, I had just spawned it in.

Just tried it and it works. Let this issue become resolved as invalid. Although it doesn't make much sense that a hive needs to be nearby if it's still dripping the pollen over the crops.

I found the issue, it was because Java automatically gave me the 32-bit java. Downloading 64 bit fixed the issue. How do I close this issue?

I tried this in 1.14.4 and it failed as well. I'm starting to wonder if its something with my computer or something.

I just tested it in 1.15.1 and it still has the same issue.

 I did some more testing, this time installing starting a server entirely from scratch. I let the server generate the world, and then It was playable, but then it started to get progressively laggier until I was met with a stack overflow error, which means there is a memory leak somewhere. I re-launched it only to find my world file deleted, but my playerdata still intact. I started to play and the same thing happened. This screenshot isn't very helpful but it was taken the second time it happened.

[media]
[media]

 

[media]

Has been added by request. I had to stop the debugger early because it didn't seem to create a file if it ended up crashing, which it did. The debug session didn't last long cause it was going to crash.

[media]

Can confirm for 1.14 Pre-release 5. (see my screenshot)

Confirmed for 19w13b

I am in 1.13.2 and I still experience this bug, or a similar one.

I know, sorry, I tried to search for it but unless I used the same exact way of describing the bugIi wouldn't be able to find it.