mojira.dev

Matthias Verlinden

Assigned

No issues.

Reported

MC-164712 Clouds are rendered in front of chunk borders Fixed MC-164711 F3+G lines shown before blocks Duplicate

Comments

Wow Gnembon is a dev now. Good luck! 

I updated my drivers (to the newest version which is still 6 years old) and it worked so I'm lucky and have no problems anymore 🙂 , but similar things can't be simply ignored in the future, even more if a mod fixes a critical problem. It would make some people very dependent of mods, unnecessarily (if there a mod which tried to fix it) 

I experience this at 100%, it makes the game unplayble since 1.17. However, instead of saying we got bad computers you could try to fix it, or ask to OptiFine as OptiFine fixes it

I like it. I think it should stay

It simply doesn't render the 2 first gameticks on Java Edition I believe

I can confirm for 1.16.1. It happenned to me when I was testing and making an endermen farm

I notice this bug a lot when switching from 1.12 and versions above, the default settings changed actually. I always play in ZQSD, which became default in 1.13+. I don't remember seeing this in the change logs. In 1.12 going forward is W (the rest I don't remember but it doesn't matter) so I have to change it back every single time as well as the other settings 😞

This "bug" is simply useful. It's so cool, and I actually consider it as a feature. Would be a shame to "fix" it

If this stays, even less parity will be a thing in this world, and if Java do the same, even more people are going to cry 😞 (because already a lot of people are crying because of quarantine)

So 2 bee hives (or more) with the exact same NBT can stack together. I don't want this to change, it's cool

Can confirm too. Very annoying

Maybe it's intended. They want to make the Turtle Master potions the most valuable potion of them all

If you put bee nests in your enderchest, then you 're in the future (or maybe not)

Yeah I also saw this bug some days ago and took some screenshots

Haha you are so fast, after 3 minutes you already updated the bug report

I saw this bug too (in pre-release 4)

Please fix this bug before the full release of the 1.15