Tokes

Probably should edit the title to include "Infinite XP glitch".

Reset as in "no longer force loaded" or reset as in "chunk gets erased and generated again from scratch"?

I realized it's fixed now but that doesn't help people who are playing on earlier versions. Do we need to avoid recommending any versions from 1.17.x thru 1.20.1 when someone is asking about a mod that isn't updated to the latest version for example?

Confirmed "fixed" via massive downgrade in 1.19. Now dimensions with seeds are impossible, removing one of the reasons for custom dimensions in the first place.

Mojang, please bring this feature back! We didn't want it removed, just made optional.

Also if it was intended it would be affecting multiplayer-only, not singleplayer-only.

Note that while it claims to be fixed in 22w17a, the patch notes for 22w17a claim it is ONLY fixed in cases where the player lit the tnt (so no redstone cases or fire charge shot out of a dispenser cases). This bug report is for all cases, so should be reopened since it hasn't been fully fixed.

Surprised they released a B snapshot this time around. They didn't a month back when the furnace was broken. We just had to wait until the next week.

In what way is a 14 pixel high boat chest supposed to be identical to a 15 pixel high regular chest? It's not a problem with the lock, it's you having a preference for the missing pixel of height to be on the bottom instead of on the top.

Pretty sure the old behavior was intended (since a block there would be in the way of the path the particles travel in). SOME of the particles appear from the top surface of the bookshelves and travel in a curved path to the top surface of the enchanting table. If a block is diagonally up from the bookshelf it's in the way of the particle flow.

Granted SOME of the particles come out the side of the bookshelves, but even those ones need to travel to the top surface of the enchanting table, so a full block above the air between the bookshelves and the table would block those particles too.

Or should we open a new bug report stating that the particles have always travelled wrong and it should be a straight line from the side of the bookshelf to the side of the enchanting table? That would mean enchanting tables have ALWAYS had the wrong particle path and it's been a bug since 2011.

Pretty sure this bug has always been there. It's a side effect of world generation not causing block updates. Same reason caves that cut too close to rivers or oceans can sometimes expose the side of a water block without causing it to flow.

This issue has always been there with abandoned mineshafts. The rails (and the ground they were on) were placed, and then a later section of the mineshaft was placed and the ground under the rails was removed without the rails being removed.

Worldgen doesn't cause block updates (which is what would be needed for these rails to notice the ground under them is now missing). The world would generate far too slowly if it did. This is also why caves that cut too close to rivers and oceans sometimes expose the sides of water blocks without causing them to start flowing. And it's also why you sometimes find the top halves of trees floating above ponds. I wouldn't be surprised if this is never fixed.

Has mojang considered just not spawning the water? It's not actually needed for farmland, the crops just grow a lot slower without it (and dry farmland without anything planted in it reverts back to dirt pretty fast, but not faster than villagers replant). Maybe replace the water with more farmland+crops so it doesn't make a 1 block deep hole that villagers keep jumping in and out of (the jump out can trample crops last I checked).

Only drawback I can think of is if the villagers don't have enough to replant every space they'll start losing spaces.

About phantoms: they'll only spawn if there's open sky directly above you (so that you don't come back from a mining trip and find masses of them above you), and I was under the impression that they start appearing on the 4th night (as in: you need to avoid sleeping for 3 FULL nights before you're marked as able to cause phantoms to spawn).

I just checked the wiki to be sure, and 1 minecraft hour (55 real seconds) after sunrise on day 4 is when you qualify. That's when you would've woken up from bed if you had slept on night 3. Of course they can't spawn in daylight, so they have to wait until night 4.

Btw over a long enough time period those baby villagers would grow up and then be targetable by the raiders.

From r/minecraft on 1.18pre6 and 1.18pre7 (someone else's comment not my own):

"Performance in 1.18 prereleases is still abysmal because the renderer has not been improved to compensate the change in worlds, neither for the shift to GL 3.1, nor for the rather simplistic approach to vertex storage and draw calls. The renderer "worked" for for pre-GL 3 because device drivers for old GL versions are optimized around assumptions that held for compatibility contexts, but those optimizations are not present anymore because more responsibility to be efficient with GPU object usage and draw calls is shifted to the application in GL 3. No matter what you do, today's Minecraft JE rendering is severely limited by single core performance and GPU bandwidth because of the excessive draw calls and buffer property rebinding, and even high end CPUs can't provide enough headroom for that."

Note that the list of what animals spawn in what biomes has been tweaked slightly. Make sure you're not looking for cows in biomes they don't spawn in at all for example. But this shouldn't affect any tests that just look for passive animals regardless of species.

And animals are less likely to spawn in:

• Dark Forests because the animals require a light level of 8 or higher to spawn.

• Jungles because they also require grass_block as the surface they spawn on, which Jungles block with lots of underbrush. Animals used to get around that by spawning INSIDE leaves, but that was declared a bug and eventually got fixed. Not sure what the Ocelots are doing to get around the problem.

Btw the default lava level (on 1.18 snapshot worlds that don't have their height changed)  is -54 not -64. Can you confirm which of those two you're experiencing?

Report it to the texture pack's maker. It's nothing to do with minecraft itself, that's 3rd party content.

"All data is treated according to GDPR and CCPA best practices"

Which require an opt out.

REOPEN THIS ISSUE.

Btw ore distribution changes DID appear in the changelog, just not the one you guys were looking at.

Ore distribution of ALL ORES was changed when the height was increased in the snapshots (new height range was negative 64 to positive 320). Then in week 15 Mojang decided to revert all height changes and save that for 1.18. Apparently their reversion of ore distribution had a mistake in it. But the changelog for the release version of 1.17 isn't going to list changes that were made 4 months back and then undone 2 months back.

Also there's nothing anyone can do to get your stuff back. Only you can do that (by enabling cheats and using /give commands to give yourself the items). Yes I realize this will make it so you can't get achievements on that world (such a stupid bedrock-only feature).