In my old world there are Hardcoded spawn spots in the old chunks that recently appeared and are not supposed to be there.
They are however, supposed to generate in this same place in the 1.21 world generation of my world's seed.
There is both an outpost and an ocean monument that integrated themselves where they shouldn't be
I think this has potential to mess with people's builds,
This is a copy of my world that is a few months old but is similarly affected by this bug.
https://1drv.ms/u/c/4a66febb0439946d/EdH6DcxP2x9CmB4hqiFdl7kBHvluDkSSkAR6OOaQkL6ObQ
Seed: -656322617
Coordinates to HSA of a monument that appeared in a plains biome:
2317.41 66.60 621.42 [The corner NW spawn spot]
2317.58 64.00 674.49 [This spawn spot appeared in a river so its convenient for testing]
Coordinates to HSA of an outpost that appeared in a swamp:
1832, 80, 136 [Main spawn spot of the outpost]
Steps to reproduce:
Open copy of my world
Visit the respective coordinates of the outpost and ocean monument
Wait for pillagers to spawn in the swamp and guardians to spawn in the river
Expected result:
No guardians or pillagers appear
Observed result:
Guardians appear in the river and pillagers appear in the swamp
Edit:
Concerning the bug where biomes in old worlds changed to ocean. I waited and didnt update my game when that bug was around, when the hotfix dropped I updated and loaded my world. So I am quite sure my world wasnt affected by this bug, but its possible that it could be related to it in some way shape or form.
This is the bug I am talking about:
https://report.bugs.mojang.com/servicedesk/customer/portal/6/MCPE-186928
Linked issues
Comments 4
I know this bug that you linked. I specifically remember that I skipped updating back then until the hotfix dropped. So i am quite sure that my world wasnt loaded when this bug was present.
I am able to easily reproduce this all the time. In fact, i have even turned the outpost into a farm.
I could record a video of the guardians and pillagers spawning in their unnatural locations if that should help
Thank you for your report!
After consideration, the issue is being closed as Won't Fix.
Please note that this is not the same as Working as Intended, as this bug report correctly describes behavior in the game that might not be the intended or desirable behavior, but it will not be fixed right now. Sometimes, this is because the issue reported is minor and/or impossible to change without large architectural changes to the code base.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
It may be easier to reproduce the bug if you set the world simulation distance to 4 before loading it, and change to creative mode. Fly up directly above guardian spawn spot at about Y 90.
This is likely a side-effect of MCPE-186928, which is already fixed. Fixes to world generation usually can only apply to worlds or chunks where the bug has not yet occurred. So, the bug reported here may not be reproducible with worlds where it had not been triggered in 1.21.40, and it may not be fixable in worlds where it has been triggered.