1. Open a world that has already been extensively explored prior to 1.21.50
2. Go to a location well within the explored portion and run the command
   /locate biome pale_garden
3. Go to the indicated location

EXPECTED: There is a pale garden
ACTUAL: There is a dark forest

If I run the command again while standing in the indicated location, the command gives a new, usually nearby, location that is also not a pale garden. It seems most of the time the new location is 45 blocks away from my current location but sometimes the distance is a few hundred blocks. Doing this repeatedly seems to lead me around in circles within the same dark forest biome.

I thought that perhaps if I did this repeatedly, the game might "remember" which chunks are which biomes after I actually visit them in the new version of the game, but this doesn't seem to happen. I've found cases where the command leads me back to a location about 5 blocks away from a place I've already checked.

Ideally, the /locate command should provide a location that is actually a pale garden.

I've tried teleporting to a location far away from where I've ever visited (e.g. 50000, 100, 50000) in the same world and using the /locate command there, and it does successfully locate a pale garden. So it does work in completely unexplored areas. However, it seems that having already explored dark forests in a location where a pale garden would be if it weren't already explored causes the /locate command to produce incorrect results.